...
Approach:
Example Data Stream:
...
Canceled
Description:
MeSH uses the terminology that a heading is canceled. They generally include use_instead to identify the alternative. This may be the same as Deprecated.
...
Split
Description:
This type provides information on an entity that was split into two or more separate entities.
...
Example Data Stream:
...
Merge
Description:
This type provides information on two or more entities that were merged into a single entity.
...
Example Data Stream:
...
Changed
Description:
This type provides information on an existing entity with changed data.
...
Example Data Stream:
...
Label Change Only
Description:
This type provides information on an existing entity with changed label data.
...
- Null to actual value.
- How to distinguish between a missing subject vs. a typo?
- Notification of missed value to a specific user. This would likely be outside the change management stream.
- Notification of submitted entities that were accepted and those that were not accepted.
- Ex. Cataloger adds record to OCLC, but it is not immediately available. Get notification when it is available or rejected.
Would the types of changes be different for different types of entities (e.g. MeSH Subjects vs. Names)?
- The goal is to have the types be flexible enough to use the same basic data for each type for all authorities and all types of entities.