Software implements logic for migrating legacy designations on-the-fly. Here is how it is done:
Look if terms already exists. If it exists, do nothing.
Create first designation of type “expression” based on legacy term
Fill in first designation’s normativeStatus from classification
Create additional designations based on legacy synonyms
The problem now is that there is terms that does not seem to include legacy synonyms. Software sees terms and does nothing, but terms does not include legacy synonyms, so synonyms never get migrated.
I am going to change the migration logic to look at “synonyms”, and if “synonyms” is present then perform a smaller migration to only deal with synonyms
In https://github.com/geolexica/isotc211-glossary/commit/26a947ca80fdf6883e1f9bec3d1db1909dccf79c, this databases now has list
terms
instead of oneterm
, but they are missing synonyms.Software implements logic for migrating legacy designations on-the-fly. Here is how it is done:
terms
already exists. If it exists, do nothing.term
normativeStatus
fromclassification
synonyms
The problem now is that there is
terms
that does not seem to include legacy synonyms. Software seesterms
and does nothing, butterms
does not include legacy synonyms, so synonyms never get migrated.