Provenance. describes the source of the Content Information, who has had custody of it since its origination, and its history (including processing history). Context describes how the Content Information relates to other information outside the Information Package. For example, it would describe why the Content Information was produced, and it may include a description of how it relates to another Content Information object that is available. Reference provides one or more identifiers, or systems of identifiers, by which the Content Information may be uniquely identified. Examples include an ISBN number for a book, or a set of attributes that distinguish one instance of Content Information from another. Fixity provides a wrapper, or protective shield, that protects the Content Information from undocumented alteration. For example, it may involve a checksum over the Content Information of a digital Information Package. Much of the PDI content is included in national and international metadata standards. If it is already available for the data set, it can be referenced rather than being included in every SIP. Similarly, the Representation Information may be available separately and can also be referenced rather than included in every SIP. Figure 6.1-2. Obtaining Information from Data in an OAIS Archival Information Packages and Dissemination Information Packages An Archival Information Package (AIP) consists of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS. Dissemination Information Packages are received by the Consumer in response to a request to the Archive. In response to a request, the OAIS provides all or a part of an AIP, or potentially multiple AIPs, to a Consumer in the form of a Dissemination Information Package (DIP). The DIP may also include collections of AIPs, and it may or may not have complete PDI. The Packaging Information will necessarily be present in some form so that the Consumer can clearly distinguish the information that was requested. Figure 6.1-3. OAIS Information Package Concepts and Relationships PAIMAS BACKGROUND The second document, the Producer-Archive Interface Methodology Abstract Standard (PAIMAS), describes four phases of the process that the Data Producers and the Archive will follow. These phases describe the relationship, interactions, and negotiation between the Producer and the Archive that result in both a final SA and a successful transfer of data. The PAIMAS phases are: The Preliminary Phase, also known as a pre-ingest or pre-accessioning phase, includes the initial contacts between the Producer and the Archive and any resulting feasibility studies, preliminary definition of the scope of the project, a draft of the SIP definition and finally a draft Submission Agreement. The Formal Definition Phase includes completing the SIP design with precise definitions of the digital objects to be delivered, completing the Submission Agreement with precise contractual transfer conditions such as restrictions on access and establishing the delivery schedule. The Transfer Phase performs the actual transfer of the SIP from the Producer to the Archive and the preliminary processing of the SIP by the Archive, as it is defined in the agreement. The Validation Phase includes the validation processing of the SIPs by the Archive and any necessary follow-up action with the Producer. Different systematic or in-depth levels of validation may be defined. Validations may be performed after each delivery, or later, depending on the validation constraints. The SA, when finalized, represents the completion of the Formal Definition Phase. The Transfer and Validation phases will be subsequent steps and are documented in the Guidelines for the Producer-Archive Interface document. Note that there will, in many cases, be some needed changes to the Producer and/or the Archive software to accommodate specific functionality defined in this SA. This may necessitate a time delay between the formal definition phase and the beginning of the transfer phase so that these modifications can be developed, integrated, and tested. While the PAIMAS describes a SA as the final outcome, or deliverable, the Archive recognizes that the information contained in the PAIMAS version of the SA may be included in other documents. These additional documents could include an Interface Control Document (ICD), a Memorandum of Understanding (MOU), a Memorandum of Agreement (MOA), a Service Level Agreement (SLA), an Operations Agreement (OA), or other similar documents, and may be any combination of this set of documents. The Archive does not dictate which of these documents must be used, only that the necessary information be appropriately documented. However, for simplicity in this document, the term SA is used and is intended to be inclusive of all necessary information whether in the SA itself and/or in additional documents. TERMINOLOGY This section is a glossary which defines the common terminology as it is used in this document.
Appears in 1 contract
Samples: And Conditions of Agreement
Provenance. describes the source of the Content Information, who has had custody of it since its origination, and its history (including processing history). Context describes how the Content Information relates to other information outside the Information Package. For example, it would describe why the Content Information was produced, and it may include a description of how it relates to another Content Information object that is available. Reference provides one or more identifiers, or systems of identifiers, by which the Content Information may be uniquely identified. Examples include an ISBN number for a book, or a set of attributes that distinguish one instance of Content Information from another. Fixity provides a wrapper, or protective shield, that protects the Content Information from undocumented alteration. For example, it may involve a checksum over the Content Information of a digital Information Package. Much of the PDI content is included in national and international metadata standards. If it is already available for the data set, it can be referenced rather than being included in every SIP. Similarly, the Representation Information may be available separately and can also be referenced rather than included in every SIP. Figure 6.1-2. Obtaining Information from Data in an OAIS Archival Information Packages and Dissemination Information Packages An Archival Information Package (AIP) consists of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS. Dissemination Information Packages are received by the Consumer in response to a request to the Archive. In response to a request, the OAIS provides all or a part of an AIP, or potentially multiple AIPs, to a Consumer in the form of a Dissemination Information Package (DIP). The DIP may also include collections of AIPs, and it may or may not have complete PDI. The Packaging Information will necessarily be present in some form so that the Consumer can clearly distinguish the information that was requested. Figure 6.1-3. OAIS Information Package Concepts and Relationships PAIMAS BACKGROUND The second document, the Producer-Archive Interface Methodology Abstract Standard (PAIMAS), describes four phases of the process that the Data Producers and the Archive will follow. These phases describe the relationship, interactions, and negotiation between the Producer and the Archive that result in both a final SA and a successful transfer of data. The PAIMAS phases are: The Preliminary Phase, also known as a pre-ingest or pre-accessioning phase, includes the initial contacts between the Producer and the Archive and any resulting feasibility studies, preliminary definition of the scope of the project, a draft of the SIP definition and finally a draft Submission Agreement. The Formal Definition Phase includes completing the SIP design with precise definitions of the digital objects to be delivered, completing the Submission Agreement with precise contractual transfer conditions such as restrictions on access and establishing the delivery schedule. The Transfer Phase performs the actual transfer of the SIP from the Producer to the Archive and the preliminary processing of the SIP by the Archive, as it is defined in the agreement. The Validation Phase includes the validation processing of the SIPs by the Archive and any necessary follow-up action with the Producer. Different systematic or in-depth levels of validation may be defined. Validations may be performed after each delivery, or later, depending on the validation constraints. The SA, when finalized, represents the completion of the Formal Definition Phase. The Transfer and Validation phases will be subsequent steps and are documented in the Guidelines for the Producer-Archive Interface document. Note that there will, in many cases, be some needed changes to the Producer and/or the Archive software to accommodate specific functionality defined in this SA. This may necessitate a time delay between the formal definition phase and the beginning of the transfer phase so that these modifications can be developed, integrated, and tested. While the PAIMAS describes a SA as the final outcome, or deliverable, the Archive recognizes that the information contained in the PAIMAS version of the SA may be included in other documents. These additional documents could include an Interface Control Document (ICD), a Memorandum of Understanding (MOU), a Memorandum of Agreement (MOA), a Service Level Agreement (SLA), an Operations Agreement (OA), or other similar documents, and may be any combination of this set of documents. The Archive does not dictate which of these documents must be used, only that the necessary information be appropriately documented. However, for simplicity in this document, the term SA is used and is intended to be inclusive of all necessary information whether in the SA itself and/or in additional documents. TERMINOLOGY This section is a glossary which defines the common terminology as it is used in this document.
Appears in 1 contract
Samples: And Conditions of Agreement
Provenance. describes the source of the Content Information, who has had custody of it since its origination, and its history (including processing history). Context describes how the Content Information relates to other information outside the Information Package. For example, it would describe why the Content Information was produced, and it may include a description of how it relates to another Content Information object that is available. Reference provides one or more identifiers, or systems of identifiers, by which the Content Information may be uniquely identified. Examples include an ISBN number for a book, or a set of attributes that distinguish one instance of Content Information from another. Fixity provides a wrapper, or protective shield, that protects the Content Information from undocumented alteration. For example, it may involve a checksum over the Content Information of a digital Information Package. Much of the PDI content is may be included in national and and/or international metadata standardsstandard metadata. If it is these metadata are already available for the data set, it can be referenced rather than being included in every SIP. Similarly, the Representation Information may be available separately and can also be referenced rather than included in every SIP. Figure 6.1-25. Obtaining Information from Data in an OAIS Archival Information Packages and Dissemination Information Packages An Archival Information Package (AIP) consists of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS. Dissemination Information Packages are received by the Consumer in response to a request to the Archive. In response to a request, the OAIS provides all or a part of an AIP, or potentially multiple AIPs, to a Consumer in the form of a Dissemination Information Package (DIP). The DIP may also include collections of AIPs, and it may or may not have complete PDI. The Packaging Information will necessarily be present in some form so that the Consumer can clearly distinguish the information that was requested. Figure 6.1-36. OAIS Information Package Concepts and Relationships PAIMAS BACKGROUND The second document, the Producer-Archive Interface Methodology Abstract Standard (PAIMAS), describes four phases of the process that the Data Producers and the Archive will follow. These phases describe the relationship, interactions, and negotiation between the Producer and the Archive that result in both a final SA and a successful transfer of data. The PAIMAS phases are: The Preliminary Phase, also known as a pre-ingest or pre-accessioning phase, includes the initial contacts between the Producer and the Archive and any resulting feasibility studies, preliminary definition of the scope of the project, a draft of the SIP definition and finally a draft Submission Agreement. The Formal Definition Phase includes completing the SIP design with precise definitions of the digital objects to be delivered, completing the Submission Agreement with precise contractual transfer conditions such as restrictions on access and establishing the delivery schedule. The Transfer Phase performs the actual transfer of the SIP from the Producer to the Archive and the preliminary processing of the SIP by the Archive, as it is defined in the agreement. The Validation Phase includes the validation processing of the SIPs by the Archive and any necessary follow-up action with the Producer. Different systematic or in-depth levels of validation may be defined. Validations may be performed after each delivery, or later, depending on the validation constraints. The SA, when finalized, represents the completion of the Formal Definition Phase. The Transfer and Validation phases will be subsequent steps and are documented in the Guidelines for the Producer-Archive Interface document. Note that there will, in many cases, be some needed changes to the Producer and/or the Archive software to accommodate specific functionality defined in this SA. This may necessitate a time delay between the formal definition phase and the beginning of the transfer phase so that these modifications can be developed, integrated, and tested. While the PAIMAS describes a SA as the final outcome, or deliverable, the Archive recognizes that the information contained in the PAIMAS version of the SA may be included in other documents. These additional documents could include an Interface Control Document (ICD), a Memorandum of Understanding (MOU), a Memorandum of Agreement (MOA), a Service Level Agreement (SLA), an Operations Agreement (OA), or other similar documents, and may be any combination of this set of documents. The Archive does not dictate which of these documents must be used, only that the necessary information be appropriately documented. However, for simplicity in this document, the term SA is used and is intended to be inclusive of all necessary information whether in the SA itself and/or in additional documents. TERMINOLOGY DOCUMENT REVIEW RECORD DOCUMENT REVIEW SCHEDULE This section document is expected to undergo a glossary which defines periodic review of content for completeness, correctness and overall currency. All reviews should be documented in the common terminology as it Document Review Record, D.2, even though a document review may not warrant a document change. The review schedule is used in this document.defined below. Next Review Date Subsequent Review Frequency DOCUMENT REVIEW RECORD The Review Record table tracks the reviews of the document based on its review schedule. Review Record
Appears in 1 contract
Samples: And Conditions of Agreement
Provenance. describes the source of the Content Information, who has had custody of it since its origination, and its history (including processing history). Context describes how the Content Information relates to other information outside the Information Package. For example, it would describe why the Content Information was produced, and it may include a description of how it relates to another Content Information object that is available. Reference provides one or more identifiers, or systems of identifiers, by which the Content Information may be uniquely identified. Examples include an ISBN number for a book, or a set of attributes that distinguish one instance of Content Information from another. Fixity provides a wrapper, or protective shield, that protects the Content Information from undocumented alteration. For example, it may involve a checksum over the Content Information of a digital Information Package. Much of the PDI content is may be included in national and and/or international metadata standardsstandard metadata. If it is these metadata are already available for the data set, it can be referenced rather than being included in every SIP. Similarly, the Representation Information may be available separately and can also be referenced rather than included in every SIP. Figure 6.1-25. Obtaining Information from Data in an OAIS Archival Information Packages and Dissemination Information Packages An Archival Information Package (AIP) consists of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS. Dissemination Information Packages are received by the Consumer in response to a request to the Archive. In response to a request, the OAIS provides all or a part of an AIP, or potentially multiple AIPs, to a Consumer in the form of a Dissemination Information Package (DIP). The DIP may also include collections of AIPs, and it may or may not have complete PDI. The Packaging Information will necessarily be present in some form so that the Consumer can clearly distinguish the information that was requested. Figure 6.1-3. OAIS Information Package Concepts and Relationships PAIMAS BACKGROUND The second document, the Producer-Archive Interface Methodology Abstract Standard (PAIMAS), describes four phases of the process that the Data Producers and the Archive will follow. These phases describe the relationship, interactions, and negotiation between the Producer and the Archive that result in both a final SA and a successful transfer of data. The PAIMAS phases are: The Preliminary Phase, also known as a pre-ingest or pre-accessioning phase, includes the initial contacts between the Producer and the Archive and any resulting feasibility studies, preliminary definition of the scope of the project, a draft of the SIP definition and finally a draft Submission Agreement. The Formal Definition Phase includes completing the SIP design with precise definitions of the digital objects to be delivered, completing the Submission Agreement with precise contractual transfer conditions such as restrictions on access and establishing the delivery schedule. The Transfer Phase performs the actual transfer of the SIP from the Producer to the Archive and the preliminary processing of the SIP by the Archive, as it is defined in the agreement. The Validation Phase includes the validation processing of the SIPs by the Archive and any necessary follow-up action with the Producer. Different systematic or in-depth levels of validation may be defined. Validations may be performed after each delivery, or later, depending on the validation constraints. The SA, when finalized, represents the completion of the Formal Definition Phase. The Transfer and Validation phases will be subsequent steps and are documented in the Guidelines for the Producer-Archive Interface document. Note that there will, in many cases, be some needed changes to the Producer and/or the Archive software to accommodate specific functionality defined in this SA. This may necessitate a time delay between the formal definition phase and the beginning of the transfer phase so that these modifications can be developed, integrated, and tested. While the PAIMAS describes a SA as the final outcome, or deliverable, the Archive recognizes that the information contained in the PAIMAS version of the SA may be included in other documents. These additional documents could include an Interface Control Document (ICD), a Memorandum of Understanding (MOU), a Memorandum of Agreement (MOA), a Service Level Agreement (SLA), an Operations Agreement (OA), or other similar documents, and may be any combination of this set of documents. The Archive does not dictate which of these documents must be used, only that the necessary information be appropriately documented. However, for simplicity in this document, the term SA is used and is intended to be inclusive of all necessary information whether in the SA itself and/or in additional documents. TERMINOLOGY This section is a glossary which defines the common terminology as it is used in this document.
Appears in 1 contract
Samples: And Conditions of Agreement
