An optional short text describing the contents of the package, e.g. "Accounting records of 2017".
+An optional short text describing the contents of the package, e.g. "Accounting records of + 2017".
A way of indicating the status of the package and to instruct the OAIS on how to properly handle the package. If not set, the expected behaviour is equal to NEW.
+A way of indicating the status of the package and to instruct the OAIS on how to properly + handle the package. If not set, the expected behaviour is equal to NEW.
`@TYPE` is used with the value "SUBMISSIONAGREEMENT".
Example: RA 13-2011/5329; 2012-04-12
Example: http://submissionagreement.kb.se/dnr331-1144-2011/20120711/
-Note: It is recommended to use a machine-readable format for a better description of a submission agreement.
-For example, the submission agreement developed by Docuteam GmbH http://www.loc.gov/standards/mets/profiles/00000041.xml
+Note: It is recommended to use a machine-readable format for a better description of a + submission agreement.
+For example, the submission agreement developed by Docuteam GmbH http://www.loc.gov/standards/mets/profiles/00000041.xml
An optional reference to a previous submission agreement(s) which the information may have belonged to.
+An optional reference to a previous submission agreement(s) which the information may have + belonged to.
`@TYPE` is used with the value "PREVIOUSSUBMISSIONAGREEMENT".
Example: FM 12-2387/12726, 2007-09-19
Example: http://submissionagreement.kb.se/dnr331-1144-2011/20120711/
-Note: It is recommended to use a machine-readable format for a better description of a submission agreement.
-For example, the submission agreement developed by Docuteam GmbH http://www.loc.gov/standards/mets/profiles/00000041.xml
+Note: It is recommended to use a machine-readable format for a better description of a + submission agreement.
+For example, the submission agreement developed by Docuteam GmbH http://www.loc.gov/standards/mets/profiles/00000041.xml
An optional reference code indicating where in the archival hierarchy the package shall be placed in the OAIS.
+An optional reference code indicating where in the archival hierarchy the package shall be + placed in the OAIS.
`@TYPE` is used with the value "REFERENCECODE".
Example: FM 12-2387/12726, 2007-09-19
In cases where the SIP originates from other institutions maintaining a reference code structure, this element can be used to record these reference codes and therefore support the provenance of the package when a whole archival description is not submitted with the submission.
+In cases where the SIP originates from other institutions maintaining a reference code + structure, this element can be used to record these reference codes and therefore support the provenance of the package when a + whole archival description is not submitted with the submission.
`@TYPE` is used with the value "PREVIOUSREFERENCECODE".
Example: SE/FM/123/123.1/123.1.3
A wrapper element that enables to encode the name of the organisation or person that originally created the data being transferred. Please note that this might be different from the organisation which has been charged with preparing and sending the SIP to the archives.
+A wrapper element that enables to encode the name of the organisation or person that + originally created the data being transferred. Please note that this might be different from the organisation which has been + charged with preparing and sending the SIP to the archives.
The name of the organisation(s) that originally created the data being transferred.
-Please note that this might be different from the organisation which has been charged with preparing and sending the SIP to the archives.
+Please note that this might be different from the organisation which has been charged with + preparing and sending the SIP to the archives.
The archival creator agent has a note providing a unique identification code for the archival creator.
+The archival creator agent has a note providing a unique identification code for the + archival creator.
A wrapper element that enables to encode the name of the organisation or person submitting the package to the archive.
+A wrapper element that enables to encode the name of the organisation or person submitting + the package to the archive.
The role of the person(s) or institution(s) responsible for creating and/or submitting the package.
+The role of the person(s) or institution(s) responsible for creating and/or submitting the + package.
A wrapper element that enables to encode the name of the contact person for the submission.
+A wrapper element that enables to encode the name of the contact person for the + submission.
A wrapper element that enables to encode the name of the organisation or person that preserves the package.
+A wrapper element that enables to encode the name of the organisation or person that + preserves the package.
The preservation agent has a note providing a unique identification code for the archival creator.
+The preservation agent has a note providing a unique identification code for the archival + creator.
The SIP dmdSec element should comply with dmdSec requirements in the CSIP profile.
+The SIP dmdSec element should comply with dmdSec requirements in + the CSIP profile.
The SIP amdSec element should comply with amdSec requirements in the CSIP profile.
+The SIP amdSec element should comply with amdSec requirements + in the CSIP profile.
An optional attribute may be used if the MIMETYPE is not sufficient for the purposes of processing the information package.
+An optional attribute may be used if the MIMETYPE is not sufficient for the purposes of + processing the information package.
Example: "Extensible Markup Language"
Example: "PDF/A"
Example: "ISO/IEC 26300:2006"
@@ -593,7 +619,8 @@The version of the file format when the use of PREMIS has not been agreed upon in the submission agreement.
+The version of the file format when the use of PREMIS has not been agreed upon in the + submission agreement.
Example: "1.0"
The name of the format registry used to identify the file format when the use of PREMIS has not been agreed upon in the submission agreement.
+The name of the format registry used to identify the file format when the use of PREMIS + has not been agreed upon in the submission agreement.
Example: "PRONOM"
Key of the file format in the registry when use of PREMIS has not been agreed upon in the submission agreement.
+Key of the file format in the registry when use of PREMIS has not been agreed upon in the + submission agreement.
Example: "fmt/101"
The SIP structMap element should comply with structMap requirements in the CSIP profile.
+The SIP structMap element should comply with structMap requirements in the CSIP profile.
Section not defined or used in CSIP, additional own uses may occur.
-Information regarding the structural links is found in the METS Primer
+Information regarding the structural links is found in the METS Primer
Section not defined or used in CSIP, additional own uses may occur.
-Information regarding the behavior section is found in the METS Primer
+Information regarding the behavior section is found in the METS Primer
A suite of tools for e-archiving and digital preservation. The tools provide functionality for producers to archive digital information, for archives to preserve digital information and for consumers to access archived information.
+A suite of tools for e-archiving and digital preservation. The tools provide functionality for + producers to archive digital information, for archives to preserve digital information and for consumers to access archived + information.
ES Solutions - www.essolutions.se
@@ -694,19 +728,27 @@RODA is a digital repository solution that delivers functionality for all the main units of the OAIS reference model. RODA is capable of ingesting, managing and providing access to the various types of digital objects produced by large corporations or public bodies.
-RODA is based on open-source technologies and is supported by existing standards such as the Open Archival Information System (OAIS), Metadata Encoding and Transmission Standard (METS), Encoded Archival Description (EAD), Dublin Core (DC) and PREMIS (Preservation Metadata).
+RODA is a digital repository solution that delivers functionality for all the main units of the + OAIS reference model. RODA is capable of ingesting, managing and providing access to the various types of digital objects produced by + large corporations or public bodies.
+RODA is based on open-source technologies and is supported by existing standards such as the Open + Archival Information System (OAIS), Metadata Encoding and Transmission Standard (METS), Encoded Archival Description (EAD), Dublin + Core (DC) and PREMIS (Preservation Metadata).
RODA is licensed under LGPLv3 for all source-code including interoperability libraries like SIP manipulation libraries.
+RODA is licensed under LGPLv3 for all source-code including interoperability libraries like SIP + manipulation libraries.
RODA-in is a tool specially designed for producers and archivists to create Submission Information Packages (SIP) ready to be submitted to an Open Archival Information System (OAIS). The tool creates SIPs from files and folders available on the local file system.
-RODA-in supports several Submission Information Package formats such as BagIt, E-ARK SIP and the Hungarian SIP format.
+RODA-in is a tool specially designed for producers and archivists to create Submission Information + Packages (SIP) ready to be submitted to an Open Archival Information System (OAIS). The tool creates SIPs from files and folders + available on the local file system.
+RODA-in supports several Submission Information Package formats such as BagIt, E-ARK SIP and the + Hungarian SIP format.
RODA-in is licensed under LGPLv3.