Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Checklistbank
-
Labels:None
Description
The intermediate neo dbs for the nub and indexed checklists contain a single neo4j node for a pro parte synonym that has multiple accepted parents. In the postgres db model these get expanded into individual name_usage records and need to have their own primary key.
For indexed checklists thats no problem as the ids get assigned during inserts from the regular pg sequence.
For nub usages the ids should all exist in advance to preserve stable ids over time. A single neo4j pro parte synonym must therefore have multiple ids assigned. Use the additional PROPARTE_SYNONYM relationship to store the usageKey to be read during imports!
https://github.com/gbif/checklistbank/commit/008fe6d6fae1ccf1421235a85c1ebd72ec7ce13a