Specification for Submission Information Packages

Preface

I. Aim of the Specification

This document is one of several related specifications which aim to provide a common set of usage descriptions of international standards for packaging digital information for archiving purposes. These specifications are based on common, international standards for transmitting, describing and preserving digital data. They also utilise the Reference Model for an Open Archival Information System (OAIS), which has Information Packages as its foundation. Familiarity with the core functional entities of OAIS is a prerequisite for understanding the specifications.

The specifications are designed to help data creators, software developers, and digital archives to tackle the challenge of short-, medium- and long-term data management and reuse in a sustainable, authentic, cost-efficient, manageable and interoperable way. A visualisation of the current specification network can be seen here:

Figure I: Diagram showing E-ARK specification dependency hierarchy. Note that the image only shows a selection of the published CITS and isn’t an exhaustive list.

Overview of the E-ARK Specifications

Common Specification for Information Packages (E-ARK CSIP)

This document introduces the concept of a Common Specification for Information Packages (CSIP). The main purposes of CSIP are to:

• Establish a common understanding of the requirements which need to be met to achieve interoperability of Information Packages.
• Establish a common base for the development of more specific Information Package definitions and tools within the digital preservation community.
• Propose the details of an XML-based implementation of the requirements using, to the largest possible extent, standards which are widely used in international digital preservation.

Ultimately the goal of the Common Specification is to reach a level of interoperability between all Information Packages so that tools implementing the Common Specification can be adopted by institutions without the need for further modifications or adaptations.

Specification for Submission Information Packages (E-ARK SIP)

The main aims of this specification are to:

• Define a general structure for a Submission Information Package format suitable for a wide variety of archival scenarios, such as document and image collections, databases or geospatial data.
• Enhance interoperability between Producers and Archives.
• Recommend best practices regarding the structure, content and metadata of Submission Information Packages.

Specification for Archival Information Packages (E-ARK AIP)

The main aims of this specification are to:

• Define a generic structure of the AIP format suitable for a wide variety of data types, such as document and image collections, archival records, databases or geospatial data.
• Recommend a set of metadata related to the structural and the preservation aspects of the AIP as implemented by the eArchiving Reference Implementation (earkweb).
• Ensure the format is suitable to store large quantities of data.

Specification for Dissemination Information Packages (E-ARK DIP)

The main aims of this specification are to:

• Define a generic structure of the DIP format suitable for a wide variety of archival records, such as document and image collections, databases or geographical data.
• Recommend a set of metadata related to the structural and access aspects of the DIP.

Content Information Type Specifications (E-ARK CITS)

The main aim of a Content Information Type Specification (CITS) is to:

• Define, in technical terms, how data and metadata must be formatted and placed within a CSIP Information Package to achieve interoperability in exchanging specific Content Information.

The number of possible Content Information Type Specifications is unlimited. For a list of existing Content Information Type Specifications see the DILCIS Board webpage (DILCIS Board, http://dilcis.eu/).

II. Organisational Support

This specification is maintained by the Digital Information LifeCycle Interoperability Standards Board (DILCIS Board, http://dilcis.eu/). The role of the DILCIS Board is to enhance and maintain the draft specifications developed in the European Archival Records and Knowledge Preservation Project (E-ARK project, http://eark-project.com/), which concluded in January 2017. The Board consists of eight members, but no restriction is placed on the number of participants taking part in the work. All Board documents and specifications are stored in GitHub (https://github.com/DILCISBoard/), while published versions are made available on the Board webpage. The DILCIS Board have been responsible for providing the core specifications to the Connecting Europe Facility eArchiving Building Block https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eArchiving/.

III. Authors & Revision History

A full list of contributors to this specification, as well as the revision history, can be found in the Postface material.

E-ARK SIP

Specification for Submission Information Packages

Version: 2.1.0

Date: 2021-10-25

1. Introduction
1.1. Scope and purpose
1.2. Target audience
1.3. Definition of SIP
2. Structure
3. METS
3.1. Extended use of the METS root element (element mets)
3.2. Extended use of the METS header (element metsHdr)
3.3. Extended use of the METS descriptive metadata section (element dmdSec)
3.4. Extended use of METS administrative metadata section (element amdSec)
3.5. Extended use of the METS file section (element fileSec)
3.6. Extended use of the METS structural map (element structMap)
4. Content Information Type Specifications
4.1. Submission Agreement
5. Appendices
5.1. Appendix A: Submission Agreement semantic elements
5.1.1. Project information
5.1.2. Change management
5.1.3. Producer, Archive and Designated Community
5.1.4. Submission Information Package (SIP)
5.1.5. Submission Session Information
5.1.6. Ingest
5.1.7. Submission risks
5.2. Appendix B: E-ARK Information Package METS example
5.3. Appendix C: External Schema
5.3.1. E-ARK SIP METS Extension
5.3.2. E-ARK CSIP METS Extension
5.4. Appendix D: External Vocabularies
5.4.1. Package status
5.4.2. Alternative record ID’s
5.4.3. Note type
5.4.4. OAIS Package type
5.5. Appendix E: A Full List of E-ARK SIP Requirements
6. Glossary

1. Introduction

According to the Open Archival Information System Reference Model (OAIS) every submission of information to an archive occurs as one or more discrete transmissions of Submission Information Packages (SIP). Unfortunately, the OAIS itself does not specify how these information packages should look like.

The EU funded E-ARK project (2014-2017) first acknowledged this problem and started to develop a solution in the form of a package specification. This specification is now part of a set of specifications currently managed by an independent body named the Digital Information LifeCycle Interoperability Standards Board (DILCIS Board).

1.1. Scope and purpose

This document describes how to produce and parse E-ARK Submission Information Packages (SIP). The main objectives of this specification are to:

• Define the general structure for a Submission Information Package format in a way that it is suitable for a wide variety of archival scenarios, e.g. document and image collections, databases or geographical data;
• Enhance interoperability between Producers and Archives;
• Recommend best practices regarding metadata, content and structure of Submission Information Packages.

1.2. Target audience

The target audience for this specification is records creators, archival institutions and software providers that are responsible with preparing, packaging, delivering and receiving packages of information to be archived in an OAIS, i.e. pre-ingest and ingest functional units.

1.3. Definition of SIP

The OAIS reference model defines a Submission Information Package (SIP) as:

An Information Package that is delivered by the Producer to the OAIS for use in the construction or update of one or more AIPs and/or the associated Descriptive Information.

The E-ARK SIP follows this definition and builds on the E-ARK Common Specification for Information Packages by extending it to support specific requirements related to the process of selecting, packaging, transmitting, receiving, validating and ingesting information originally maintained by a Producer.

In summary, the SIP constitutes a package of information that is ready to be sent by a Producer to an Archive in order to be ingested by the OAIS.

2. Structure

The SIP specification follows a structure that is common to all Information Packages in the E-ARK set of specifications. The common structure is fully described in the Common Specification for Information Packages (see Section 4. CSIP structure).

In its simplest form, an SIP consists of metadata and zero or more representations, also composed of data and metadata, as seen in Figure 2. A package with zero representations means that it only includes metadata. This is a special type of Information Package that enables Producers to deliver updates to the metadata to previously ingested packages.

Figure 2: Simplified view of a package structure.

According to PREMIS Version 3.0:

A representation is a set of files, including structural metadata, needed for a complete and reasonable rendition of an Intellectual Entity. For example, a journal article may be complete in one PDF file. This single file constitutes the representation. Another journal article may consist of one SGML file and two image files. These three files constitute the representation. A third article may be represented by one TIFF image for each of 12 pages plus an XML file of structural metadata showing the order of the pages. These 13 files constitute the representation.

As one SIP can contain more than one representation of the same intellectual entity, representations MUST be placed within distinct folders (i.e., rep-001, rep-002, rep-n under the representations folder). In contrast, metadata may exist within each representation folder or at the root level (next to the representations folder). Metadata can serve multiple purposes, the most common one being the support for discoverability of resources within the OAIS (i.e. descriptive metadata).

If metadata is stored at the root level of the package, then there is generally no need to include a metadata folder at the representation level. In such cases, the metadata folder under representations is considered optional. The SIP also accounts for the following additional folders that can exist both at the root level or under the representations folder (Figure 3):

• documentation – for including additional documentation about the data included in the package (e.g. a data dictionary for a SIARD file);
• schemas – for storing schemas of XML files included in the data or metadata.

Figure 3: Example of the full use of the SIP structure

The details of the internal structure of an SIP including its data and metadata folders can be further specified by Submission Agreements. These can exist for a particular submission, a special collection or a specific Producer.

3. METS

The Metadata Encoding and Transmission Standard (METS) is a standard for encoding descriptive, administrative, and structural metadata expressed using the XML Schema Language.

The METS Schema for an E-ARK SIP is the same as for an E-ARK AIP or an E-ARK DIP. The actual requirements of the METS used in the E-ARK SIP are defined in the CSIP on section “5.3 Use of METS”. However, there are some small differences between a METS instance of an E-ARK SIP and an E-ARK CSIP. Most of the differences consist of setting values of particular attributes, defining controlled vocabularies or making optional elements mandatory.

These differences are manifested by means of a METS profile. The SIP METS profile extends the CSIP METS profile. As stated before, in this document only the differences between the SIP METS and the CSIP METS are highlighted. In order to fully understand how to create or interpret the METS file included within an SIP, it is necessary to read the CSIP.

3.1. Extended use of the METS root element (element mets)

The root of a METS document can contain a number of optional attributes, namespaces (xmlns:), locations for external schemas (xsi:) and a number of other elements.

The following table describes the differences in the mets element between the E-ARK SIP and the CSIP.

Example: METS root element example with values from E-ARK-SIP as well as CS IP.

<mets:mets xmlns:mets="http://www.loc.gov/METS/" xmlns:csip="https://DILCIS.eu/XML/METS/CSIPExtensionMETS" xmlns:sip="https://DILCIS.eu/XML/METS/SIPExtensionMETS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" OBJID="uuid-4422c185-5407-4918-83b1-7abfa77de182" LABEL="Accounting records of 2017" TYPE="OTHER" csip:OTHERTYPE="Accounting" PROFILE="https://earksip.dilcis.eu/profile/E-ARK-SIP.xml" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/mets.xsd http://www.w3.org/1999/xlink http://www.loc.gov/standards/mets/xlink.xsd https://DILCIS.eu/XML/METS/CSIPExtensionMETS https://earkcsip.dilcis.eu/schema/DILCISExtensionMETS.xsd https://DILCIS.eu/XML/METS/SIPExtensionMETS https://earksip.dilcis.eu/schema/DILCISExtensionSIPMETS.xsd">
</mets:mets>

Example: METS example of altrecordID’s, and SIP agents following the SIP profile as well as CS IP.

<mets:metsHdr CREATEDATE="2018-04-24T14:37:49.602+01:00" LASTMODDATE="2018-04-24T14:37:49.602+01:00" RECORDSTATUS="NEW" csip:OAISPACKAGETYPE="SIP">
  <mets:agent ROLE="ARCHIVIST" TYPE="ORGANIZATION">
    <mets:name>The Swedish health agency</mets:name>
    <mets:note csip:NOTETYPE="IDENTIFICATIONCODE">VAT:SE201345098701</mets:note>
  </mets:agent>
  <mets:agent ROLE="CREATOR" TYPE="ORGANIZATION">
    <mets:name>The agency, Personnel</mets:name>
    <mets:note csip:NOTETYPE="IDENTIFICATIONCODE">VAT:SE2098109810-AF87</mets:note>
  </mets:agent>
  <mets:agent ROLE="CREATOR" TYPE="INDIVIDUAL">
    <mets:name>Sven Svensson</mets:name>
    <mets:note>Phone: 08-123456, Email: sven.svensson@mail.mail</mets:note>
  </mets:agent>
  <mets:agent ROLE="PRESERVATION" TYPE="ORGANIZATION">
    <mets:name>The archives</mets:name>
    <mets:note csip:NOTETYPE="IDENTIFICATIONCODE">ID:1234567</mets:note>
  </mets:agent>
  <mets:altRecordID TYPE="SUBMISSIONAGREEMENT">http://submissionagreement.kb.se/dnr331-1144-2011/20120711/</mets:altRecordID>
  <mets:altRecordID TYPE="PREVIOUSSUBMISSIONAGREEMENT">FM 12-2387/12726, 2007-09-19</mets:altRecordID>
  <mets:altRecordID TYPE="REFERENCECODE">SE/RA/123456/24/P</mets:altRecordID>
  <mets:altRecordID TYPE="PREVIOUSREFERENCECODE">SE/FM/123/123.1/123.1.3</mets:altRecordID>
</mets:metsHdr>

3.2. Extended use of the METS header (element metsHdr)

The METS header element <metsHdr> includes information about the creator of the submission package, the original creator of the data, contact information of the person delivering the SIP, among other actors. These entities are typically called “agents” (see element metsHdr/agent).

The metsHdr is also used to indicate the type of behaviour to be expected from the OAIS when processing a particular SIP. For example, one might indicate that an SIP should be used to “replace” a particular AIP in the repository or that an SIP is meant for “testing” purposes and therefore it should not create an AIP at the end of the ingest process (see attribute metsHdr/@RECORDSTATUS).

It is also in the metsHdr that the Submission Agreement to which a particular SIP conforms can be identified (see metsHdr/altrecordID/@TYPE=”SUBMISSIONAGREEMENT).

The following table describes the differences in the metsHdr between an E-ARK SIP and the CSIP.

Example: METS example of the archival creator agent described in SIP9 - SIP14

<mets:agent ROLE="ARCHIVIST" TYPE="ORGANIZATION">
  <mets:name>The Swedish health agency</mets:name>
  <mets:note csip:NOTETYPE="IDENTIFICATIONCODE">VAT:SE201345098701</mets:note>
</mets:agent>

Example: METS example of the submitting agent described in SIP15 - SIP20

<mets:agent ROLE="CREATOR" TYPE="ORGANIZATION">
  <mets:name>The agency, Personnel</mets:name>
  <mets:note csip:NOTETYPE="IDENTIFICATIONCODE">VAT:SE2098109810-AF87</mets:note>
</mets:agent>

Example: METS example of the contact person agent described in SIP21 - SIP25

<mets:agent ROLE="CREATOR" TYPE="INDIVIDUAL">
  <mets:name>Sven Svensson</mets:name>
  <mets:note>Phone: 08-123456, Email: sven.svensson@mail.mail</mets:note>
</mets:agent>

Example: METS example of the preservation agent described in SIP26 - SIP31

<mets:agent ROLE="PRESERVATION" TYPE="ORGANIZATION">
  <mets:name>The archives</mets:name>
  <mets:note csip:NOTETYPE="IDENTIFICATIONCODE">ID:1234567</mets:note>
</mets:agent>

3.3. Extended use of the METS descriptive metadata section (element dmdSec)

The METS descriptive metadata section <dmdSec> is responsible for recording descriptive metadata for all the data items included in the package.

The SIP specification itself does not prescribe of any particular metadata format. It is a role of the OAIS together with the Producer to set the rules in terms of descriptive metadata. These rules should be set and agreed on in the Submission Agreement.

In this regard, the SIP specification does not change or extend any of the requirements already defined by the Common Specification for Information Packages (for more information see section 5.3.3 of the CSIP).

3.4. Extended use of METS administrative metadata section (element amdSec)

The METS administrative metadata section <amdSec> is used to include or reference technical and preservation metadata.

Although seldom used, preservation metadata can be included in an SIP. The guide on Using PREMIS with METS provides recommendations on how to use the <amdSec> element to reference PREMIS metadata. Preservation metadata is typically used to record the history of preservation events that influence the state of the information package. Normally, these take place after the package has been ingested into a digital repository, however an example of preservation event that can occur prior to the ingest process is the digitization of analogue material. This event takes place before the information is ingested and can be included in an SIP.

The SIP specification does not change or extend any of the requirements already defined by the Common Specification for Information Packages (for more information see section 5.3.4. of the CSIP).

3.5. Extended use of the METS file section (element fileSec)

The METS file section element <fileSec> is used to describe all the components included in the information package which have not been already included in the amdSec and dmdSec elements.

The main purpose of the METS file section is to serve as a “table of contents” or “manifest” for all the files included in the package, thus allowing the OAIS to validate the integrity and completeness of the files included in the package. This means that for all the files included in the package, their location and checksum need to be available and described in the fileSec element. That includes files in the data, schemas and in the documentation folders.

The following table describes the differences in the fileSec between an E-ARK SIP and the CSIP.

Example: METS example of an SIP with file information together with the info from CS IP.

<mets:file ID="docx-file" MIMETYPE="application/vnd.openxmlformats-officedocument.wordprocessingml.document" SIZE="2554366" CREATED="2012-08-15T12:08:15.432+01:00" CHECKSUM="91B7A2C0A1614AA8F3DAF11DB4A1C981F14BAA25E6A0336F715B7C513E7A1557" CHECKSUMTYPE="SHA-256" sip:FILEFORMATNAME="Microsoft Word for Windows" sip:FILEFORMATVERSION="2007 onwards" sip:FORMATREGISTRY="PRONOM" sip:FORMATREGISTRYKEY="fmt/412">
  <mets:FLocat LOCTYPE="URL" xlink:type="simple" xlink:href="documentation/File.docx">
  </mets:FLocat>
</mets:file>

3.6. Extended use of the METS structural map (element structMap)

The mandatory METS structural map element <structMap> is intended to provide an overview of the components included in the package. It can also link elements of that structure to associated content files and metadata. In the CSIP the structMap describes the higher-level structure of all the content in the root and may link to existing representations.

The SIP specification does not change or extend any of the requirements already defined by the Common Specification for Information Packages (for more information see section 5.3.6 of the CSIP)

4. Content Information Type Specifications

The concept of a Content Information Type Specification is essentially an extension method which allows for widening the interoperability scope of the E-ARK IPs into a content specific level.

A Content Information Type can be understood as a category of Content Information, for example, relational databases, scientific data or digitised maps. A Content Information Type Specification defines in technical terms how data and metadata (mainly in regard to the Information Object) should be formatted and placed within an Information Package in order to achieve interoperability in exchanging specific Content Information.

The SIP presents no extensions or exceptions to the concept of Content Information Type as it is formalised in the Common Specification for Information Packages. More information on this subject can be found in sections 1.2, 1.3 and 6.1 of the CSIP.

4.1. Submission Agreement

Interactions between Producers and the OAIS are often guided by a Submission Agreement, which establishes specific details about how these interactions should take place, e.g. the type of information expected to be exchanged, the metadata the Producer is expected to deliver, the logistics of the actual transfer, statements regarding access restrictions on the submitted material, etc.

Given the importance of the Submission Agreement, the E-ARK SIP specification provides a way of referring to it regardless of its form. A submission agreement can be delivered in digital (e.g. PDF or XML file) or in analogue forms (i.e. paper document). More information about how to reference the Submission Agreement within the SIP can be found in the section dedicated to the metsHdr element.

According to the PAIMAS, 2004 standard a Submission Agreement should include a complete and precise definition of:

• Information to be transferred (e.g. SIP contents, SIP packaging, data models, identification of the designated community, legal and contractual aspects);
• Transfer definition (e.g. specification of the OAIS Data Submission Sessions);
• Validation definition;
• Change management (e.g. conditions for modification of the agreement, for breaking the agreement);
• Schedule (submission timetable).

This specification includes a list of semantic elements that should be present in a standard Submission Agreement (see Appendix A). The E-ARK SIP specification does not require the use of any of these semantic elements or in any way forbids the use of any other Submission Agreement formats. The list of semantic elements provided simply serves as a baseline recommendation.

The recommended list of semantic elements is inspired by the PAIMAS requirements and the Submission Agreement template provided by the National Oceanic and Atmospheric Administration (NOAA).

5. Appendices

This section includes supplementary information that may help the reader to better understand this specification.

5.1. Appendix A: Submission Agreement semantic elements

The following list of semantic elements provide a starting point for anyone willing to prepare a Submission Agreement. This list is not prescriptive, or by any means complete. It merely serves the purpose of outlining the most relevant semantic elements that should be present in a Submission Agreement.

5.1.1. Project information

• Project - Elements of a transfer project.
  • Project Name - Name of the transfer project (e.g. Transfer I, 2016).
  • Project ID - Identification code of the transfer project (e.g. 201601122044).

5.1.2. Change management

• Version/Revision - Elements for tracking the changes in versions of the submission agreement.
  • Release date - The date of the version.
  • Change authority - The information about the person who changed the submission agreement (e.g. John Smith (The National Archives of Estonia)).
  • Change description - A short textual description of the change.
  • Section(s) affected - This element is meant for recording more detailed information about changes.

5.1.3. Producer, Archive and Designated Community

• Producer Organization - Elements describing the Producer.
  • Organization name - Elements describing the organisation
  • Main Contact - Elements describing the main contact of the transfer project.
    • Address - The address of the main contact.
    • Telephone - The telephone number of the main contact.
    • E-mail - The e-mail of the main contact.
    • Additional Information - Meant for recording any additional information needed to describe the contact.
  • Individual Contacts - Elements describing other individual contacts of the organisation.
    • Name - The full name of the contact person.
    • Role - The role of the contact person.
    • Telephone - The telephone number of the contact person.
    • E-mail - The e-mail of the contact person.
    • Additional Information - Meant for recording any additional information needed to describe the contact.
• Archive Organization - Elements describing the Archive.
  • Organization name - The official name of the organisation.
  • Main Contact - Elements describing the main contact of the transfer project.
    • Address - The address of the main contact.
    • Telephone - The telephone number of the main contact.
    • E-mail - The e-mail of the main contact.
    • Additional Information - Meant for recording any additional information needed to describe the contact.
  • Individual Contacts - Elements describing other individual contacts of the organisation.
    • Name - The full name of the contact person.
    • Role - The role of the contact person.
    • Telephone - The telephone number of the contact person.
    • E-mail - The e-mail of the contact person.
    • Additional Information - Element for recording any additional information needed to describe the contact.
• Designated Community - Elements describing the Designated Community.
  • Description - The textual description of the skills and knowledge base of the designated community.
  • Individual Contacts - Elements describing the individual contacts of the designated community.
    • Name - The full name of the contact person.
    • Role - The role of the contact person.
    • Telephone - The telephone number of the contact person.
    • E-mail - The e-mail of the contact person.
    • Additional Information - Meant for recording any additional information needed to describe the contact.

5.1.4. Submission Information Package (SIP)

• Content and metadata - Elements describing the content and metadata of the submission information package.
  • Description - A description of data origination, content and coverage.
  • Platform Information - A short description of the source system.
  • Representation Information - A description of the means to represent the data content (e.g. referencing to data dictionaries, decoding software, etc.).
  • Preservation Descriptive Information - A description for keeping data independently understandable (e.g. processing history, platform documentation, algorithm information, technical reports, user manuals, etc.).
  • Supplemental Information - Meant for recording any additional information needed to describe the content or metadata of the SIP.
  • Access Constraints - A description of access restrictions and other legal or contractual access aspects.
• Data Model - Elements describing the agreements for the SIP data model.
  • Content Type - A short description of the content type (e.g. ERMS content).
  • Reference - A reference to the full agreed data model description.
  • Additional Information - A description of any other additional information (e.g. description of the physical folder structure of the SIP) related to the data model.

5.1.5. Submission Session Information

• Submission Session - Elements describing the agreements for the submission session.
  • Submission Method - The description of the submission method (e.g. through a digital interface, a physical transfer).
  • Delivery Schedule - A description of a delivery schedule (a submission session may have a routine or a complex schedule).
  • Data Submission Inventory - A description of the complete inventory of data objects (and other items) in the submission session.

5.1.6. Ingest

• Submission Reception - Elements describing the agreements for the ingest.
  • Validation - A description of procedures for the quality assurance.
  • Error Handling - A description of procedures for the error handling.
  • Receipt Confirmation - A description of the receipt confirmation.

5.1.7. Submission risks

• Risks - Elements describing the risks and mitigation options of the submission.
  • Risk Factor - Meant for listing all risk factors (e.g. the designated community is not properly defined) of the submission.
  • Mitigation Option - Meant for listing all mitigation options (e.g. define the designated community together with producers) for the risks.

5.2. Appendix B: E-ARK Information Package METS example

Example 1: Example of a whole METS document describing an submission information package with no representations.

<mets:mets xmlns:mets="http://www.loc.gov/METS/" xmlns:csip="https://DILCIS.eu/XML/METS/CSIPExtensionMETS" xmlns:sip="https://DILCIS.eu/XML/METS/SIPExtensionMETS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" OBJID="uuid-4422c185-5407-4918-83b1-7abfa77de182" LABEL="Accounting records of 2017" TYPE="OTHER" csip:OTHERTYPE="Accounting" PROFILE="https://earksip.dilcis.eu/profile/E-ARK-SIP.xml" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/mets.xsd http://www.w3.org/1999/xlink http://www.loc.gov/standards/mets/xlink.xsd https://DILCIS.eu/XML/METS/CSIPExtensionMETS https://earkcsip.dilcis.eu/schema/DILCISExtensionMETS.xsd https://DILCIS.eu/XML/METS/SIPExtensionMETS https://earksip.dilcis.eu/schema/DILCISExtensionSIPMETS.xsd">
  <mets:metsHdr CREATEDATE="2018-04-24T14:37:49.602+01:00" LASTMODDATE="2018-04-24T14:37:49.602+01:00" RECORDSTATUS="NEW" csip:OAISPACKAGETYPE="SIP">
    <mets:agent ROLE="CREATOR" TYPE="OTHER" OTHERTYPE="SOFTWARE">
      <mets:name>RODA-in</mets:name>
      <mets:note csip:NOTETYPE="SOFTWARE VERSION">2.1.0-beta.7</mets:note>
    </mets:agent>
    <mets:agent ROLE="ARCHIVIST" TYPE="ORGANIZATION">
      <mets:name>The Swedish health agency</mets:name>
      <mets:note csip:NOTETYPE="IDENTIFICATIONCODE">VAT:SE201345098701</mets:note>
    </mets:agent>
    <mets:agent ROLE="CREATOR" TYPE="ORGANIZATION">
      <mets:name>The agency, Personnel</mets:name>
      <mets:note csip:NOTETYPE="IDENTIFICATIONCODE">VAT:SE2098109810-AF87</mets:note>
    </mets:agent>
    <mets:agent ROLE="CREATOR" TYPE="INDIVIDUAL">
      <mets:name>Sven Svensson</mets:name>
      <mets:note>Phone: 08-123456, Email: sven.svensson@mail.mail</mets:note>
    </mets:agent>
    <mets:agent ROLE="PRESERVATION" TYPE="ORGANIZATION">
      <mets:name>The archives</mets:name>
      <mets:note csip:NOTETYPE="IDENTIFICATIONCODE">ID:1234567</mets:note>
    </mets:agent>
    <mets:altRecordID TYPE="SUBMISSIONAGREEMENT">http://submissionagreement.kb.se/dnr331-1144-2011/20120711/</mets:altRecordID>
    <mets:altRecordID TYPE="PREVIOUSSUBMISSIONAGREEMENT">FM 12-2387/12726, 2007-09-19</mets:altRecordID>
    <mets:altRecordID TYPE="REFERENCECODE">SE/RA/123456/24/P</mets:altRecordID>
    <mets:altRecordID TYPE="PREVIOUSREFERENCECODE">SE/FM/123/123.1/123.1.3</mets:altRecordID>
  </mets:metsHdr>
  <mets:dmdSec ID="dmdSecExample1" CREATED="2018-04-24T14:37:49.609+01:00">
    <mets:mdRef LOCTYPE="URL" MDTYPE="EAD" MDTYPEVERSION="2002" xlink:type="simple" xlink:href="metadata/descriptive/ead2002.xml" SIZE="903" CREATED="2018-04-24T14:37:49.609+01:00" CHECKSUM="F24263BF09994749F335E1664DCE0086DB6DCA323FDB6996938BCD28EA9E8153" CHECKSUMTYPE="SHA-256">
    </mets:mdRef>
  </mets:dmdSec>
  <mets:amdSec>
    <mets:digiprovMD ID="appdx1.digiprov-premis-file-1" CREATED="2018-04-24T14:37:52.783+01:00">
      <mets:mdRef LOCTYPE="URL" xlink:type="simple" xlink:href="metadata/preservation/premis1.xml" MDTYPE="PREMIS" MDTYPEVERSION="3.0" MIMETYPE="text/xml" SIZE="1211" CREATED="2018-04-24T14:37:52.783+01:00" CHECKSUM="8aa278038dbad54bbf142e7d72b493e2598a94946ea1304dc82a79c6b4bac3d5" CHECKSUMTYPE="SHA-256" LABEL="premis1.xml">
      </mets:mdRef>
    </mets:digiprovMD>
    <mets:digiprovMD ID="appdx1.digiprov-premis-file-2" CREATED="2018-04-24T14:47:52.783+01:00">
      <mets:mdRef LOCTYPE="URL" xlink:type="simple" xlink:href="metadata/preservation/premis2.xml" MDTYPE="PREMIS" MDTYPEVERSION="3.0" MIMETYPE="text/xml" SIZE="2854" CREATED="2018-04-24T14:37:52.783+01:00" CHECKSUM="d1dfa585dcc9d87268069dc58d5e47956434ec3db4087a75a3885d287f15126f" CHECKSUMTYPE="SHA-256" LABEL="premis2.xml">
      </mets:mdRef>
    </mets:digiprovMD>
  </mets:amdSec>
  <mets:fileSec ID="appdx1.filesec-docx-file-1">
    <mets:fileGrp ID="appdx1.filegrp-doc" USE="Documentation">
      <mets:file ID="appdx1.docx-file" MIMETYPE="application/vnd.openxmlformats-officedocument.wordprocessingml.document" SIZE="2554366" CREATED="2012-08-15T12:08:15.432+01:00" CHECKSUM="91B7A2C0A1614AA8F3DAF11DB4A1C981F14BAA25E6A0336F715B7C513E7A1557" CHECKSUMTYPE="SHA-256" sip:FILEFORMATNAME="Microsoft Word for Windows" sip:FILEFORMATVERSION="2007 onwards" sip:FORMATREGISTRY="PRONOM" sip:FORMATREGISTRYKEY="fmt/412">
        <mets:FLocat LOCTYPE="URL" xlink:type="simple" xlink:href="documentation/File.docx">
        </mets:FLocat>
      </mets:file>
      <mets:file ID="appdx1.file-2-docx" MIMETYPE="application/vnd.openxmlformats-officedocument.wordprocessingml.document" SIZE="2554366" CREATED="2012-08-15T12:08:15.432+01:00" CHECKSUM="91B7A2C0A1614AA8F3DAF11DB4A1C981F14BAA25E6A0336F715B7C513E7A1557" CHECKSUMTYPE="SHA-256" sip:FILEFORMATNAME="Microsoft Word for Windows" sip:FILEFORMATVERSION="2007 onwards" sip:FORMATREGISTRY="PRONOM" sip:FORMATREGISTRYKEY="fmt/412">
        <mets:FLocat LOCTYPE="URL" xlink:type="simple" xlink:href="documentation/File2.docx">
        </mets:FLocat>
      </mets:file>
    </mets:fileGrp>
    <mets:fileGrp ID="appdx1.filegrp-schema" USE="Schemas">
      <mets:file ID="appdx1.file.ead" MIMETYPE="application/xml" SIZE="123917" CREATED="2018-04-24T14:37:49.617+01:00" CHECKSUM="0BF9E16ADE296EF277C7B8E5D249D300F1E1EB59F2DCBD89644B676D66F72DCC" CHECKSUMTYPE="SHA-256" sip:FILEFORMATNAME="XML Schema Definition" sip:FORMATREGISTRY="PRONOM" sip:FORMATREGISTRYKEY="x-fmt/280">
        <mets:FLocat LOCTYPE="URL" xlink:type="simple" xlink:href="schemas/ead2002.xsd">
        </mets:FLocat>
      </mets:file>
    </mets:fileGrp>
    <mets:fileGrp ID="appdx1.filegrp.data" USE="Representations/Submission/Data" csip:CONTENTINFORMATIONTYPE="SIARDDK">
      <mets:file ID="appdx1.file.siard" MIMETYPE="application/xml" SIZE="1338744" CREATED="2018-04-24T14:37:49.617+01:00" CHECKSUM="7176A627870CFA3854468EC43C5A56F9BD8B30B50A983B8162BF56298A707667" CHECKSUMTYPE="SHA-256" ADMID="appdx1.digiprov-premis-file-2 appdx1.digiprov-premis-file-1" sip:FILEFORMATNAME="Extensible Markup Language" sip:FILEFORMATVERSION="1.0" sip:FORMATREGISTRY="PRONOM" sip:FORMATREGISTRYKEY="fmt/101">
        <mets:FLocat LOCTYPE="URL" xlink:type="simple" xlink:href="representations/submission/data/SIARD.xml">
        </mets:FLocat>
      </mets:file>
    </mets:fileGrp>
  </mets:fileSec>
  <mets:structMap ID="appdx1.struct" TYPE="PHYSICAL" LABEL="CSIP">
    <mets:div ID="appdx1.div.struct" LABEL="uuid-4422c185-5407-4918-83b1-7abfa77de182">
      <mets:div ID="appdx1.div.md" LABEL="Metadata" ADMID="appdx1.digiprov-premis-file-1 appdx1.digiprov-premis-file-2" DMDID="dmdSecExample1">
      </mets:div>
      <mets:div ID="appdx1.div.doc" LABEL="Documentation">
        <mets:fptr FILEID="appdx1.filegrp-doc">
        </mets:fptr>
      </mets:div>
      <mets:div ID="appdx1.div.schm" LABEL="Schemas">
        <mets:fptr FILEID="appdx1.filegrp-schema">
        </mets:fptr>
      </mets:div>
      <mets:div ID="appdx1.div.reps" LABEL="Representations">
        <mets:fptr FILEID="appdx1.filegrp.data">
        </mets:fptr>
      </mets:div>
    </mets:div>
  </mets:structMap>
</mets:mets>

5.3. Appendix C: External Schema

5.3.1. E-ARK SIP METS Extension

Location: https://earksip.dilcis.eu/schema/DILCISExtensionSIPMETS.xsd

Context: XML-schema for the attributes added by SIP

Note:

An extension schema with the added attributes for use in this profile.
The schema is used with a namespace prefix of sip.

5.3.2. E-ARK CSIP METS Extension

Location: http://earkcsip.dilcis.eu/schema/DILCISExtensionMETS.xsd

Context: XML-schema for the attributes added by CSIP

Note:

An extension schema with the added attributes for use in this profile.
The schema is identified using the namespace prefix csip.

5.4. Appendix D: External Vocabularies

5.4.1. Package status

Maintained By: DILCIS Board

Location: http://earksip.dilcis.eu/schema/SIPVocabularyRecordStatus.xml

Context: Used in @RECORDSTATUS

Description:

Describes the status of the package.

5.4.2. Alternative record ID’s

Maintained By: DILCIS Board

Location: http://earksip.dilcis.eu/schema/SIPVocabularyRecordIDType.xml

Context: Used in altrecordID/@TYPE

Description:

Describes the type of the alternative record ID.

5.4.3. Note type

Maintained By: DILCIS Board

Location: http://earkcsip.dilcis.eu/schema/CSIPVocabularyNoteType.xml

Context: Used in @csip:NOTETYPE

Description:

Describes the type of a note for an agent.

5.4.4. OAIS Package type

Maintained By: DILCIS Board

Location: http://earkcsip.dilcis.eu/schema/CSIPVocabularyOAISPackageType.xml

Context: Used in @csip:OAISPACKAGETYPE

Description:

Describes the OAIS type the package belongs to in the OAIS reference model.

5.5. Appendix E: A Full List of E-ARK SIP Requirements

6. Glossary

Postface

I Authors

I.I. Contributors to previous version

II Revision History

III Acknowledgements

The Common Specification for Information Packages was first developed within the E-ARK project in 2014 – 2017. E-ARK was an EC-funded pilot action project in the Competiveness and Innovation Programme 2007- 2013, Grant Agreement no. 620998 under the Policy Support Programme.

We would like to thank the National Archives of Sweden and Karin Bredenberg for their support and the availability of the Swedish national Common Specifications, upon which most of this document has been built.

The authors of this deliverable would like to thank all national archives, tool developers and other stakeholders who provided valuable knowledge about their requirements for information packages and feedback to this specification!

IV Contact & Feedback

The Common Specification for Information Packages is maintained by the Digital Information LifeCycle Interoperability Standard Board (DILCIS Board). For further information about the DILCIS Board or feedback on the current document please consult the website http://www.dilcis.eu/ or contact us at info@dilcis.eu.