Add versioned glossary YAML import and export
This commit is contained in:
@@ -143,6 +143,27 @@ The database defaults to `data/database/glossary.sqlite3`. It is created and
|
||||
bootstrapped automatically and can be moved with `MKA_GLOSSARY_DATABASE`.
|
||||
Glossary integration does not rewrite raw or diarized transcript artifacts.
|
||||
|
||||
Use **Export glossary** to download the complete SQLite-backed glossary as
|
||||
UTF-8 YAML, and **Import glossary** to replace it from a previously exported
|
||||
file. Imports are fully validated before a single SQLite transaction replaces
|
||||
the current glossary, so malformed or conflicting files leave existing data
|
||||
unchanged. Schema version 1 is:
|
||||
|
||||
```yaml
|
||||
version: 1
|
||||
glossary:
|
||||
- id: 1
|
||||
canonical_term: Secugrid HS
|
||||
aliases:
|
||||
- Sikirgut
|
||||
category: product
|
||||
description: Canonical product spelling
|
||||
active: true
|
||||
```
|
||||
|
||||
`id` is the stable SQLite glossary-entry identifier. Categories are `product`,
|
||||
`material`, `organization`, `technical_term`, `acronym`, or `other`.
|
||||
|
||||
## Input configuration import and export
|
||||
|
||||
Use **Export inputs** to save the current Meeting Assistant run-input form as a
|
||||
|
||||
Reference in New Issue
Block a user