...
| Change | Description | Comments |
|---|---|---|
| New | Completely new entity. | |
| 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. |
| 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. |
LOC implements Activity Stream and has types.
- URI belongs to a scheme when active (e.g. subject scheme). This is identified by a triple. The scheme triple is removed when it is deprecated.
- Sometimes a term may move from one authority (e.g. subject) to another (e.g. genre). Adds a triple identifying the new term (e.g. use_instead predicate). Complicated when the change is a split. Which term's URI should be used for use_instead?
Activity Stream is under development and is likely going to be a change management feed using JSON-LD. Currently, LOC is using an Atom Feed to provide some basic change management info.
Are the following handled differently when managing change?
...