Skip to content

Glossary import/export #3103

@ZuzanaOdstrcilova

Description

@ZuzanaOdstrcilova

1. Problem

What is the core problem we are trying to solve? Why does this matter?

Problem: Users have glossaries elsewhere (Confluence, internal tools) and need import/export/or some integration capabilities.
Why it matters: For big customers with existing glossaries in other tools and teams managing them, easy import/export/integration is essential. Without it, our glossary feature becomes painful for bigger clients who need to connect their existing workflow.
Why we should do it now: We had it in previous cycle. Now developer is still in the topic, fast continuation.


2. Appetite

How much time do we want to spend on this?

3 weeks - as simple as possible


3. Solution

How do we imagine solving this problem?

Import

  • New glossaries: Import option available immediately after creating a new glossary
  • Existing glossaries: Import option in glossary view (action button)

Import conflict handling:

  • Dialog Import file + checkbox to "Overwrite existing terms"
  • Import new languages not yet in glossary (projects) (implementation options on the meeting)

Export

  • Export option in glossary view
  • Export to CSV format

File Formats

  • CSV support: Requires analysis of structure and organization
  • Follow standards (analyze other tools)
  • Docs - CSV guidelines
  • Column structure: term, description, non-translatable, case-sensitive, abbreviation, forbidden term, languages

4. Basic Drawings

What rough sketches or wireframes illustrate the concept?

Image
Image
Image
Image


5. Rabbit Holes

What are the potential complexities, unknowns, or risky areas?

Potential problems: Import new languages not yet in glossary (projects)


6. No-Goes

What explicitly falls outside the scope of this pitch?

  • File formats: No other formats then CSV
  • CSV requirements: user must follow CSV format rules (analysis needed), we will not try to implement special cases (Incorrect separators)
  • No handling of simultaneous edit conflicts
  • No partial imports (bulk op) or exports - full glossary only

7. Success Criteria

How will we measure success?

  • Usage tracking: Measure how many people use glossaries and percentage who use import/export features
  • Enterprise adoption: Track glossary feature adoption among big customers (we can have some UX calls with customers in the future)
  • Workflow integration: If we will not implement it now, we can monitor reduction in customer support requests about glossary management

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestpitchThe pitch according to the Shape-up approachpitch-donePitch prepared for betting

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions