Add a scientificNameID property to NameUsage

17787
Reporter: mdoering
Type: NewFeature
Summary: Add a scientificNameID property to NameUsage
Priority: Major
Status: Open
Created: 2015-09-03 15:11:36.786
Updated: 2015-12-14 18:51:22.427
        
Description: There is no place in the NameUsage class and ChecklistBank db schema to hold a scientificNameID. We should add a new property to NameUsage and add it to the name_usage table (so they can be different for different datasets). Ultimately we can then store a nomenclator name identifier in backbone taxa.

A preferred but far more invasive solution would be to add the property to the name table. As all names are normalized now and there is a unique constraint on the name string, we cannot represent checklist in their original way. To do so remove the unique constraint and create a name record per dataset, thus duplicating the same name in the table.

The same is true for the citation table btw]]>