...
There are times, however, when a document should be presented in a manner that is consistent within the context of the referring page, usually be creating a copy of the document's text, images, etc. within the technology platform used to present the referring page (e.g., WordPress for http://www.incommon.org). This also may be desired when there revisions are expected in the future, and there are multiple references to the document. When this is done, the content "owner" of the referring page should:
- Preface the copy with a statement clarifying that it is not the authoritative copy, and providing a link to the authoritative copy in the repository. For example,
- This document is curated under the Internet2 Trust and Identity Document Stewardship program. Download the official text from the Internet2 Trust and Identity Document Repository at http://doi.org/10.26869/TI.34.1.
- Do not change the text or otherwise change the intellectual content integrity of the document. If you find you need to do this, you should probably be creating a new document with (perhaps extensive) quoting from the authoritative copy.
- Keep the formatting as close to the authoritative content as practical.
- Ask the librarian to add a note to the metadata page to indicate that a non-authoritative copy exists, its URL, and who (by name or position) should be informed if the document is superseded or deprecated. For example,
- A non-authoritative copy of this document is presented by Internet2 at https://www.incommon.org/federation/baseline-expectations-for-trust-in-federation/. Please inform the InCommon Service Manager if this document is ever superseded or deprecated so that the non-authoritative copy can be corrected or removed.
...