Assign stable ids to nub usages

17682
Reporter: mdoering
Assignee: mdoering
Type: NewFeature
Summary: Assign stable ids to nub usages
Priority: Critical
Resolution: Fixed
Status: Resolved
Created: 2015-07-13 17:40:51.711
Updated: 2015-08-14 15:25:19.047
Resolved: 2015-08-14 15:25:19.004
        
Description: During the nub build stable ids must be assigned for nub usages. A new backbone must reuse existing usage keys. Deleted nub usages must remain only logically deleted so we can resurrect such a deleted usageKey in case we include the name again in the backbone.

This task includes dealing with logical nub usage deletions.
Consider using an internal nub lookup over the http service one similar to the NubDB find method. We need to include authorship in the matching (NubDB does that).

Decide on what properties mark a stable usage key. Consider:
 - canonical name
 - kingdom
 - authorship in case of synonyms
]]>
    

Author: mdoering@gbif.org
Comment: The new IdLookup package is responsible for this and does compare canonical name, rank, kingdom & leniently authorship using a dedicated authorship comparator: https://github.com/gbif/checklistbank/tree/master/checklistbank-cli/src/main/java/org/gbif/checklistbank/nub/lookup
Created: 2015-08-11 13:16:15.617
Updated: 2015-08-11 13:16:15.617

Author: mdoering@gbif.org
Comment: Added stable id test: https://github.com/gbif/checklistbank/commit/4471493150a83e2c8cf12effe55ef3983bbeccb5
Created: 2015-08-14 15:25:19.045
Updated: 2015-08-14 15:25:19.045