...
- The Repository ID of the original document will be listed as a "superseded document" on the superseding document's repository metadata page.
- The "Deprecated" field of original document's repository metadata page will be "yes."
- When the superseding document is an update to the superseded document, its Repository ID will typically be the Repository ID of the original document after adding 1 to the version number. For example, an update to TI.22.3 would have TI.22.4 for its Repository ID. There are, however, exceptions to this numbering convention. For example, the superseding document may be completely new, not an update, or there may simply be historical reasons why this was not done,
- There are additional details for the Doc Repostiory Librarian at https://spaces.at.internet2.edu/x/Y5iTBg
- Note that a revisable version of the older document may be available in the Development Location field of its repository metadata page, as well as other material that may help you.
Here is an example of a document that is an update to an earlier document in the repository: http://doi.org/10.26869/TI.105.2
The "Deprecated" field of a document's repository metadata page will be set to "yes" when its content should no longer be trusted to reflect current practice or thinking on its topic. As noted above, this occurs when a document is superseded by another, but it can also occur without a superseding document
Here is an example of a document that is an update to an earlier document in the repository. (Note the change log at the end of the document, which is a helpful feature to add to any such document.) http://doi.org/10.26869/TI.105.2
When it's time to deprecate a document
...