Lumi Docs
  • About Lumi AI
  • Setting Up
    • Quick Start
    • 1. Connect
    • 2. Configure
      • Configuration Tips
      • Add Tables & Fields
      • Add Business Context
      • Advanced Configuration
    • 3. Distribute
  • Using Lumi
    • Getting Started
    • Lumi Use Cases
      • Data Exploration
      • Business Metrics
      • Anomaly Detection
      • Trend Analysis
      • Root Cause Analysis
      • Data Quality
    • Best Practices
      • Prompting Best Practices
      • Boards Best Practices
      • Versioning Best Practices
    • Chat Limitations
    • Knowledge Base Utility
      • Curated Prompts
      • Leveraging Memories
    • Network Configuration
  • Product Features
    • Chat
    • Boards
    • Knowledge Base
      • Overview
      • Connection
      • Tables
        • Custom Fields
      • Model
      • Business Context
      • Memories
      • Users
      • Restoration
    • Organization Settings
      • Organization Profile
      • Tool Integrations
      • Gateway Management
      • Members
    • User Profile
    • Notifications
    • Data Gateway
      • Deployment
      • Configuring for Boot
    • Source System Integrations
      • PostgreSQL
      • Microsoft SQL Server
      • MySQL
      • Databricks
      • BigQuery
      • Snowflake
      • SAP HANA
      • Oracle
    • Secondary Interfaces
      • Slack
      • Microsoft Teams
    • Release Notes
Powered by GitBook
On this page

Was this helpful?

  1. Using Lumi
  2. Best Practices

Versioning Best Practices

PreviousBoards Best PracticesNextChat Limitations

Last updated 1 month ago

Was this helpful?

​Effective management of knowledge base (KB) versions is essential to ensure the accuracy and reliability of knowledge bases. The following guidelines provide best practices for implementing version control strategies.

Versioning Best Practices

Consider the following strategies to maintain and implement robust version control:

  • Single Editor Policy: Allow only one individual to edit a KB at any given time to prevent saving conflicts and lost progress.​

  • Incremental Changes: Make small, manageable updates to facilitate easier tracking and reduce the risk of errors.​ Implement change-check-test, development process. See for more information.

  • Frequent Saves: Regularly save changes to minimize data loss and maintain an up-to-date record of modifications.​

  • Regular Testing: Consistently test the KB after updates to verify functionality and accuracy.​

  • A/B Testing: Implement A/B testing methodologies to evaluate the effectiveness of different KB versions and identify the most user-friendly formats.

  • Consistent Naming Conventions: Adopt a standardized naming system for KB versions to streamline organization and retrieval. For example, use the format: <Knowledge_Base_Name>_<Version_Number>.​ For example "Demo Procurement KB V2.1"

configuration tips