Updates Use Cases

Updates to Name records

1. Additional/removal information for a provider record

   1. name needs rematching to check if it still matches the current consensus name

      1. if the name matches a different record, the provider record is re-attached.  If any other provider records were relying on this provider name to provide relationships, then the other provider names/consensus names need to be reattached to the appropriate node according to those prrovider records

2. Accidental reuse of provider record ID for a different name

1. this is an issue, so should be detected on import and reported back to the provider

1. driven by distance function that determines whether this name is now significantly different to the name originally provided with this ID (based on name part, ie not including authors)

3. Removal of record (no deprecation)

   1. this is an issue, so should be detected on import and reported back to the provider

   2. At integration 2 scenarios - the consensus record is supported by another provider record AND this is the only provider record for the consensus name

      1. we need to be testing consensus against consensus names to detect names with no provider records and names that should match now but are still separated

4. Deprecation of record

Updates to Name Based Concepts

1. Update to provider record

1. does this

2. Deprecation of provider record

   1. Need to deprecate the consensus record, BUT can't really determine the replacement ID

      1. So Name Based Concepts are versioned by the accordingto and date fields - ie, a "snapshot" of a dataset at a particular point in time.  Then when the dataset is updated

 Updates to Concept Records

1. Additional information provided

2.