CLOCKSS: Mandatory Responsibilities - Revision history

Ntay: restoring post-2016 edits

2019-08-14T22:16:37Z

restoring post-2016 edits

Dshr: Initial version

2013-09-27T01:41:29Z

Initial version

New page

= CLOCKSS: Mandatory Responsibilities =

== OAIS Mandatory Responsibilities ==

Section 3.1 of the OAIS standard describes the mandatory responsibilities thus:
<blockquote>The OAIS shall:
* Negotiate for and accept appropriate information from information Producers.
* Obtain sufficient control of the information provided to the level needed to ensure Long Term Preservation.
* Determine, either by itself or in conjunction with other parties, which communities should become the Designated Community and, therefore, should be able to understand the information provided, thereby defining its Knowledge Base.
* Ensure that the information to be preserved is Independently Understandable to the Designated Community. In particular, the Designated Community should be able to understand the information without needing special resources such as the assistance of the experts who produced the information.
* Follow documented policies and procedures which ensure that the information is preserved against all reasonable contingencies, including the demise of the Archive, ensuring that it is never deleted unless allowed as part of an approved strategy. There should be no ad-hoc deletions.
* Make the preserved information available to the Designated Community and enable the information to be disseminated as copies of, or as traceable to, the original submitted Data Objects with evidence supporting its Authenticity.
</blockquote>

== CLOCKSS Mandatory Responsibilities ==

The CLOCKSS archive is a dark archive, which affects its Mandatory Responsibilities:
* Negotiate for and accept appropriate information from information Producers.
** The process for doing so is described in [[CLOCKSS: Ingest Pipeline]].
* Obtain sufficient control of the information provided to the level needed to ensure Long Term Preservation.
** The process for doing so is described in [[Definition of SIP]] and [[Definition of AIP]].
* Determine, either by itself or in conjunction with other parties, which communities should become the Designated Community and, therefore, should be able to understand the information provided, thereby defining its Knowledge Base.
** The CLOCKSS archive has done so. The Designated Community and other Interested Parties are defined in [[CLOCKSS: Designated Community]].
** The Knowledge Base implied by this definition and the necessary Representation Information are described in [[Definition of AIP#CLOCKSS Representation Information|Definition of AIP]].
* Ensure that the information to be preserved is Independently Understandable to the Designated Community. In particular, the Designated Community should be able to understand the information without needing special resources such as the assistance of the experts who produced the information.
** It is the publisher's responsibility, not that of the CLOCKSS archive, to ensure that the journal articles and e-books they submit for preservation are understandable without the assistance of the authors.
** If content from the CLOCKSS archive is ever triggered, the process for delivering it to the readers in the [[CLOCKSS: Designated Community]] is described in [[CLOCKSS: Extracting Triggered Content]]. It may involve the processes described in [[LOCKSS: Format Migration]].
* Follow documented policies and procedures which ensure that the information is preserved against all reasonable contingencies, including the demise of the Archive, ensuring that it is never deleted unless allowed as part of an approved strategy. There should be no ad-hoc deletions.
** Content in the CLOCKSS archive is replicated to a worldwide network of currently 12 CLOCKSS boxes.
** The CLOCKSS boxes communicate via the [[LOCKSS: Polling and Repair Protocol]] to detect and repair any corruption or loss.
** The threat model upon which the CLOCKSS archive's technology is based, and the mitigation implemented for each threat, is described in [[CLOCKSS: Threats and Mitigations]].
** The LOCKSS technology, as described in [[CLOCKSS: Threats and Mitigations]] takes care not to implement any code that can delete content.
** See [[CLOCKSS: Succession Plan]].
* Make the preserved information available to the Designated Community and enable the information to be disseminated as copies of, or as traceable to, the original submitted Data Objects with evidence supporting its Authenticity.
** If content from the CLOCKSS archive is ever triggered, the process for delivering it to the readers in the [[CLOCKSS: Designated Community]] is described in [[CLOCKSS: Extracting Triggered Content]].

== Change Process ==

Changes to this document require:
* Review by LOCKSS Engineering Staff
* Approval by LOCKSS Chief Scientist

== Relevant Documents ==
# OAIS (2012) CCSDS 650.0-M-2: Reference Model for an Open Archival Information System (OAIS). Magenta Book. Issue 1. June 2012 (ISO 14721:2003) http://public.ccsds.org/publications/archive/650x0m2.pdf accessed 2013.08.31
# [[Definition of SIP]]
# [[Definition of AIP]]
# [[CLOCKSS: Extracting Triggered Content]]
# [[CLOCKSS: Ingest Pipeline]]
# [[CLOCKSS: Designated Community]]
# [[LOCKSS: Format Migration]]
# [[CLOCKSS: Threats and Mitigations]]

@@ Line 15: / Line 15: @@
 == CLOCKSS Mandatory Responsibilities ==
-The CLOCKSS archive is a dark archive, which affects its Mandatory Responsibilities:
+The CLOCKSS Archive is a dark archive, which affects its Mandatory Responsibilities:
 * Negotiate for and accept appropriate information from information Producers.
 ** The process for doing so is described in [[CLOCKSS: Ingest Pipeline]].
@@ Line 21: / Line 21: @@
 ** The process for doing so is described in [[Definition of SIP]] and [[Definition of AIP]].
 * Determine, either by itself or in conjunction with other parties, which communities should become the Designated Community and, therefore, should be able to understand the information provided, thereby defining its Knowledge Base.
-** The CLOCKSS archive has done so. The Designated Community and other Interested Parties are defined in [[CLOCKSS: Designated Community]].
+** The CLOCKSS Archive has done so. The Designated Community and other Interested Parties are defined in [[CLOCKSS: Designated Community]].
 ** The Knowledge Base implied by this definition and the necessary Representation Information are described in [[Definition of AIP#CLOCKSS Representation Information|Definition of AIP]].
 * Ensure that the information to be preserved is Independently Understandable to the Designated Community. In particular, the Designated Community should be able to understand the information without needing special resources such as the assistance of the experts who produced the information.
-** It is the publisher's responsibility, not that of the CLOCKSS archive, to ensure that the journal articles and e-books they submit for preservation are understandable without the assistance of the authors.
+** It is the publisher's responsibility, not that of the CLOCKSS Archive, to ensure that the journal articles and e-books they submit for preservation are understandable without the assistance of the authors.
-** If content from the CLOCKSS archive is ever triggered, the process for delivering it to the readers in the [[CLOCKSS: Designated Community]] is described in [[CLOCKSS: Extracting Triggered Content]]. It may involve  the processes described in [[LOCKSS: Format Migration]].
+** If content from the CLOCKSS Archive is ever triggered, the process for delivering it to the readers in the [[CLOCKSS: Designated Community]] is described in [[CLOCKSS: Extracting Triggered Content]]. It may involve  the processes described in [[LOCKSS: Format Migration]].
 * Follow documented policies and procedures which ensure that the information is preserved against all reasonable contingencies, including the demise of the Archive, ensuring that it is never deleted unless allowed as part of an approved strategy. There should be no ad-hoc deletions.
-** Content in the CLOCKSS archive is replicated to a worldwide network of currently 12 CLOCKSS boxes.
+** Content in the CLOCKSS Archive is replicated to a worldwide network of currently 12 CLOCKSS boxes.
 ** The CLOCKSS boxes communicate via the [[LOCKSS: Polling and Repair Protocol]] to detect and repair any corruption or loss.
-** The threat model upon which the CLOCKSS archive's technology is based, and the mitigation implemented for each threat, is described in [[CLOCKSS: Threats and Mitigations]].
+** The threat model upon which the CLOCKSS Archive's technology is based, and the mitigation implemented for each threat, is described in [[CLOCKSS: Threats and Mitigations]].
 ** The LOCKSS technology, as described in [[CLOCKSS: Threats and Mitigations]] takes care not to implement any code that can delete content.
 ** See [[CLOCKSS: Succession Plan]].
 * Make the preserved information available to the Designated Community and enable the information to be disseminated as copies of, or as traceable to, the original submitted Data Objects with evidence supporting its Authenticity.
-** If content from the CLOCKSS archive is ever triggered, the process for delivering it to the readers in the [[CLOCKSS: Designated Community]] is described in [[CLOCKSS: Extracting Triggered Content]].
+** If content from the CLOCKSS Archive is ever triggered, the process for delivering it to the readers in the [[CLOCKSS: Designated Community]] is described in [[CLOCKSS: Extracting Triggered Content]].
 == Change Process ==
@@ Line 39: / Line 39: @@
 Changes to this document require:
 * Review by LOCKSS Engineering Staff
-* Approval by LOCKSS Chief Scientist
+* Approval by LOCKSS Program Manager
 == Relevant Documents ==