Set-Up & Configuration
      Back to home
      1. Preserve Knowledge Base
      2. Set-Up & Configuration

      Bulk Meta Best Practices

      Best practices for using Bulk Meta to help technicians search and find documents.

      Bulk Meta will help technicians search and find documents with ease. Here are our top 9 best practices for Bulk Meta:

      1. Clarity and Descriptiveness
        1. Use Descriptive Names: File names should clearly describe the content and purpose of the document. This helps users quickly identify what the document is about without having to open it.
        2. Example: Q1-Financial-Report.pdf instead of Report1.pdf.
      2. Consistency
        1. Adopt a Naming Convention: Establish a standard naming convention and ensure everyone adheres to it.
      3. Simplicity
        1. Avoid Special Characters: Use simple characters and avoid spaces, special characters, or punctuation marks that could cause issues in different systems.
        2. Example: Use underscores (_) or hyphens (-) instead of spaces: project_update_2024_08_02.docx.
      4. Length and Readability
        1. Keep Names Manageable: File names should be long enough to be descriptive but not excessively lengthy. Aim for a balance that provides enough detail without being cumbersome.
        2. Example: Q2_Marketing_Plan_Summary.pdf is preferable to Summary_of_the_Marketing_Plan_for_Second_Quarter_2024.pdf.
      5. Version Control
        1. Include Version Information: Clearly indicate the version of the document if multiple versions are likely to exist.
        2. Example: ProjectProposal_v2.3.docx.
      6. Relevance and Context
        1. Include Relevant Context: If a document is part of a larger project or category, include that information in the file name.
        2. Example: ClientA-Contract-2024-Signed.pdf.
      7. Avoid Redundancy
        1. Eliminate Redundant Information: Avoid unnecessary repetition of information that is already captured elsewhere in the metadata or folder structure.
        2. Example: If the document is already in a folder named Contracts, you don’t need to include Contract in the file name.
      8. Scalability
        1. Consider Future Needs: Ensure the naming convention can scale with the growing number of documents without becoming unwieldy.
        2. Example: Plan for potential subcategories or phases of projects.
      9. User Training and Documentation
        1. Educate Users: Provide training and documentation to ensure all users understand and follow the naming conventions.