Data model for the EWIG long-term preservation system. The data model follows the Information Model as described in the reference model for an Open Archival Information System (OAIS; ISO 14761:2012). The purpose of the project is to preserve usability and utility of information over the long term.
Digital Preservation Working Group (Zuse Institute Berlin)
TAs/SIPs/AIPs can be a member of an AIC.
Optional structuring information of object.
Submission metadata is mandatory for all IPs, except for Informatio Packages of type Transfer Aggregation (TA)
TransferAggregation (TA), Submission (SIP), Archival (AIP), ArchivalCollection (AIC).
Categorizes files contained in object according to usage in LTDPS.
Every InformationObjects MUST belong to one package.
Embargo scope. I.e. access rights „Institution“ until expiration.
Potentially available to the public or restricted to access by the submitting institution.
Rights statement overrides package rights.
Optional for Information Packages of type Transfer Aggregation (TA)
Owner (legal body) of intellectual property/data that is entitled to select license.
Parent organization or organization the person is loosely affiliated with at the time of recording. For work relation use worksFor.
Description of IE. See Europeana Mapping Guidelines 2.3: http://pro.europeana.eu/files/Europeana_Professional/Share_your_data/Technical_requirements/EDM_Documentation/EDM_Mapping_Guidelines_v2.3_112016.pdf
Parameters for Transfer-/Ingest-Status Responses via callback URLs
Notification Status (Date / Response to external API)
Signifies significant properties to be preserved. Not used yet.
Optional message contextualizing API Status.
Version of submission-manifest as given at time of delivery.
TransferCurator as given at time of delivery
Contact (Responsible Person) as given at time of delivery
SubmittingOrganization as given at time of delivery
Package processing has finished successfully.
Identifier is being auto-generated by API: - for Transfer Aggregations: <contractId>,<submissionName> - for Information Packages: <contractId>,<submissionName>,<ieName>
Permission to use restrictions/license information or rights reserved
Human readable (not necessarily understandable) expression for display
Optional alternative or abbreviation. Will be displayed within ()s in dashboard.
Administrative or functional role within organization regarding data submissions
Net storage allowance in bytes. -1 if unlimited.
The Agent contains information about Persons or Organizations relevant to administrative workflows. They do not act as premis:Agent within the PDI. An Agent cannot be a Person and an Organisation simultaneously.
Contract MUST contain an identifier and information about contract length and size of storage (in Bytes).
Information Objects follow the definition in 4.2.1.1 of the OAIS Reference Model. The Physical Object specialization of the Data Object is modelled as edm:aggregatedCHO. Information Objects are categorized (ewig:use) according to a vocabulary (ewigvocab:use) including IE (PREMIS Intellectual Entity), PDI, SubmissionDocumentation, Transcripts (OCR/TEI), Service/Intermediate files and so on. Information Objects MUST be memberOf a single Information Package within EWIG and MAY contain one or more files (Digital Data Objects). ObjectPreservationTypes define sets of significant properties through another EWIG ontology for IEs which might come into being in the future.
The Information Package in the data model follows the definition 4.2.2.1 in OAIS: 'The conceptual structure for supporting Long Term Preservation of information is the Information Package. An Information Package is a container that contains two types of Information Objects, the Content Information and the Preservation Description Information (PDI);[...]'. The OAIS Package Description is modelled through the aggregation of data from the SubmissionManifest and one or more Information Objects (which ones?) Information Packages aggregate Information Objects and serve as containers during the different stages within the preservation workflow. Information Packages of type TransferAggregation can aggregate *Submission or Archival* Information Packages. Submission or Archival Information Packages aggregate Information Objects comprising Content and Preservation Description Information. Information Packages MUST include a RightsStatement as fallback statement for the Access Functional Entity and the SubmissionManifest as record fort he Administration Functional Entity. Information Packages also include status messages for API access.
RightsStatements MUST include a rights declaration, a rights holder if applicable, licensing information (including PublicDomainMark). The semantics of accessRights are according to the submission agreement. If certain reuse restrictions cannot be expressed through rights and license alone, a human readable legal note can be used in description. Embargos are modelled through pcdm:rightsOverride. If not explicitly stated RightsStatements will be inherited through the hierarchy. RightsStatements take preference over each other though the hierarchy bottom up (pcdm:File, InformationObject, InformationPackage) except for pcdm:rightsOverride.
The SubmissionManifest contains the administrative (including rights) information for Administration Functional Entity. Semantics are according to the submission agreement... Every SubmissionManifest MUST include a reference to a Contract.