Reference we can use as a starting point: Change Management NOTES from LODLAM 2020
Types of Changes
| Change | Description | Comments |
|---|---|---|
| New | Completely new entity. | Two possible approaches:
|
| Deleted | Completely removed. | |
| Deprecated | Still in the authority but marked as deleted. | Allows for the URI to still resolve, but the data is marked as deprecated indicating it should no longer be used. Usually has link to the replacement entity with a predicate like use_instead. |
| Changed | Any changed. | Need more details and examples of changes. |
| Label Changed | A label of an entity changes. | May include additional changes beyond label. Would it make more sense to have a DELETE_LABEL + ADD_LABEL for changing label. When primary label, need a replacement label. For variant label, maybe delete/add is ok. What happens for primary label if there is a delete but no add? Probably not a problem because primary label is likely to be minimal required data for a valid record. ISNI number is primary label. Wikidata has multiple primary labels for different languages and some may be missing for some languages. In some cases, variants may represent different languages. In some authorities, the primary label is critical and in others it may be optional or used for convenience. LOC is looking at using a feed that provides information on authoritative labels. This is mostly for name changes (e.g. person died and the death date is added to the label). |
| URI | ||
| New Label | Does this include preferred label, variant label, etc.? What is the difference between a new label vs. a change in label? (e.g. "milk"@en) What if this is a URI to the label, possibly passing through a blank node? | |
| Predicate | Identifies which label it is? | |
| NEW LABEL | This is a new asserted triple. | |
| REPLACES LABEL | This replaces a literal label. | |
| Replaced Label | If REPLACES LABEL is specified, then also have to include the literal label being replaced. | |
| Split | One term is split into two or more terms. | May be a sub-class of deleted since the original term is no longer available under its URI. |
| Merged | Two or more terms are merged into one. | May be a sub-class of deleted since the original terms are no longer available under their original URIs. Ex. In MeSH, a common name is merged into the scientific name. Also, two works can merge into one. WikiData can get redundant entities for the same person that are then merged into one entity. |
Are the following handled differently when managing change?
- High velocity changes vs. Low velocity changes
- labels typically change less frequently
- High impact changes vs. Low impact changes
- Importance of change
Notification when an initial search fails to match and later a match becomes available. Same for partial match.
- Null to actual value.
- How to distinguish between a missing subject vs. a typo?
- Notification missed value to a specific user. This would likely be outside the change management stream.
- Ex. Cataloger adds record to OCLC, but it is not immediately available.
