3. Migrating existing data
Convert your existing terms into Glossarist format. Intended for registry managers with some technical knowledge.
If you don’t have any concepts to migrate, you can skip this step.
The complexity of this stage depends on how many pre-existing terms and concepts you have.
Below is a diagram that gives a general overview of data migration steps. For blocks in blue, further explanation is given below.
If your existing terminology data is already stored in a structured machine-readable format, it can be possible to write a software utility (an import adapter) to convert that data to Glossarist’s supported import format.
Viable source formats for conversion include, for example, Excel spreadsheets and CSV files.
Depending on how you keep track of your concepts, it may be possible to preserve revision history and change requests.
Existing terminology migration scripts
You can take a look at ISO/TC 211 termbase migration utility, written in Ruby.
|Since the latest update of that script, Glossarist data format has somewhat evolved, but it can give you a general idea.|
Getting help with your import adapter
If you can make your original terminology database public, you can file a ticket against the Migration adapters repository on GitHub.
Glossarist import format specification
We are bringing import specification details here.
Getting in touch with Ribose
Glossarist is a project developed and maintained by Ribose Open. If your original terminology database cannot be made public, you’re welcome to reach out privately and we’ll do our best to help.
If it’s not possible to convert your existing terminology data automatically, or there’s not that many concepts to migrate, the alternative is to simply use Glossarist Desktop app to enter concept & term data by hand.
You and/or concept system change submitters might want to read Getting started with the desktop app