This profile is intended to work in all different kind of solutions and stages of the OAIS-model as a base profile
No external schemas used in this profile.
It's recommended that context data confirms to all suitable standards. If the reciver of the IP have recommendations these also needs to be followed
These are the originally supported values for the TYPE attribut in METS for objects confirming to this profile.
SIP - Submission Information Package - Inkommande paket - det paket som lämnas till det digitala arkivet
AIP - Archival Information Package - Arkivpaket - det paket som lagras
DIP - Dissemination Information Package - Utlämningspaket - det paket som lämnas ut
AIC - Archival Information Collection - Arkivpaket samling - en samlingspost för flera arkivpaket
AIU - Archival Information Unit - Arkivinformations enhet - det minsta objektet som kan lagras i det digitala arkivet, kan bestå av flera filer
These are the originally supported values for the OTHERMDTYPE attribut in METS for objects confirming to this profile.
ADDML - a standard for describing databases
EAC-F - a comming standard for describing functions
EAG - a standard for describing the archival institution
METS
These are the originally supported values for the OTHERTYPE attribut in METS for objects confirming to this profile.
SOFTWARE - a program that has been involved in the process of the IP
SUPPLEMENT - extends the previous delivery
REPLEACEMENT - replaces the previous delivery
NEW - a new delivery
TEST - a test delivery
OTHER - status not in list
To be decided - more values to come
DELIVERYTYPE - Which deliverytype does the package belong to
DELIVERYSPECIFICATION - Deliveryspecification for delivery type
SUBMISSIONAGREEMENT - Identification and date for delivery agreement
PREVIOUSSUBMISSIONAGREEMENT - Identification and date for previous submission agreement seperated with a ;
DATASUBMISSIONSESSION - Session in delivery agreement
PACKAGENUMBER - A serial number for the package in a session
REFERENCECODE - Referencecode in archival description
PREVIOUSREFERENCECODE - Earlier reference code in archival description
APPRAISAL - States if the packages contains files that can be appraised or not. Which files is shown in for example the archival description or in the delivery specific information.
ACCESSRESTRICT - States if the package contains files that have access restrict of any kind. Which files is shown in for example the archival description or in the delivery specific information.
INFORMATIONCLASS - Explanation to be added
PROJECTNAME - Project name - Explanation to be added
POLICYID - Project code - Explanation to be added
STARTDATE - Startingdate for delivered information
ENDDATE - Ending date for delivered information
ERMS - Electronic Record Management System - Ärende och dokumenthantering
Personel - Personel systems - Personal
Journals - Journals from for example health care - Journal
Economics - Economics systems - Ekonomi
Databases - Databases in flatfiles - Register/Databaser
Webpages - Webpages and whole sites - Webbplatser
GIS - Geografical Information Systems - Geografiska informationssystem
No specification - No assigned specification exist - Ingen specifikation finns
AIC - A collection of packages (AIC) - Samlingspaket
Publication - An electronical publication - Publikation
Deposit - Material delivered to a library according to for example the law about e-plikt - Deposition
Agreement - Material delivered to a library with a special agreement for exampel when e-plikt isn't the case - Överenskommen leverans
These are the originally supported namespaces for objects confirming to this profile.
These are the values to show if the package contains material that can be appraised or not. Which files are shown in the specific XML-file describing the delivery according to deliveryspecification
Yes - The package contains material that can be appraised
No - The package contains nothing to appraise
These are the values to show if the package contains material that have accessrestrictions. Which files are shown in the specific XML-file describing the delivery according to deliveryspecification
Secrecy - The package contains files with confidentiality
PUL - The package contains files with confidentiality regarding personal statesment
Secrecy and PUL - The package cointains both confidentiality and personal confidentiality
These are the values to use when the agent has an identification code
VAT - The VAT-number is used - Momsnummer används
DUNS - The DUNS-number is used - DUNS-nummer används
ORG - The swedish organication number is used - Organisationsnummer används
HSA - An HSA-ID is used - HSA id används
Local - An own defined code is used - En egen kod används
URI - An URN or URL as identification - En URI används
These are the values to use when an formatkey from an formatregistry is usedthe agent has an identification code
PRONOM - The PRONOM registry is used
GDFR - The GDFR registry is used
UDTF - The UDTF registry is used
All elements are referenced with a namespace-prefix.
Xsi-definititions are made according to vcNAMESPACES
The following schema locations are used to make xml-files following this profile able to validate
xsi:schemaLocation="http://www.loc.gov/METS/ http://xml.ra.se/mets/RA_METS_eARD.xsd"
The attributes PROFILE, OBJID and TYPE values must be set
PROFILE is set to the profile that has been used to create the document.
OBJID is set with an globally unique identifier like an GUID or an UUID. The value must be precideed with the name of the type like GUID: and then followed by the value
TYPE is set according to vocabulary vcMETS_TYPE. Example: SIP
The attribute LABEL is recommended for use
LABEL is set to a descriptive title. Example: Intern bildbatch lagring
The attribute ID can be used, it's the identification when referencing itself in the METs-document
ID is set with for example UUID or GUID and starts with an added "ID"
The name can't have swedish characters, space or special characters.
These characters are allowed: a..z, A..Z, 1..9, "-" and "_"
The CREATEDATE attribute must be set.
CREATEDATE is set to the creation date of the package in the form yyyy-mm-ddThh:mm:ss+01:00
The RECORDSTATUS attribute can be set to indicate the status of the package
RECORDSTATUS uses a vocabulary
The metsHdr-element must contain at least three agent-element.
The attribute ID is not used
The attribute ROLE is used
The attribute TYPE is used
The attribute OTHERTYPE is used when TYPE has value OTHER
The name of the agent
Example: "Karin Bredenberg".
Example: "Myndigheten"
Information about the agent and the identification code
Can be zero ore more note-elements.
Usually one note element will be present
ROLE="ARCHIVIST" TYPE="ORGANIZATION"
Describes the archival creator
An note element will be used to state the identification number
The identification number will be type identified with a prefix from vcTypeOfIdentificationCode followed by a ":"
ROLE="CREATOR" TYPE="ORGANIZATION"
Describes the unit or organisation resposible for creation and delivery of the METS-document
An note element will be used to state the identification number
The identification number will be type identified with a prefix from vcTypeOfIdentificationCode followed by a ":"
ROLE="ARCHIVIST" TYPE="OTHER" OTHERTYPE="SOFTWARE"
Describes the creation software for the material delivered
If no common name for the software use a describing text
Use note element to state the version
We suggest the use of some complementary agents. For details look in the example
ROLE="EDITOR" TYPE="ORGANIZATION"
Describes the unit or organisation who has aided in the creation and delivery of the METS-document
An note element will be used to state the identification number
The identification number will be type identified with a prefix from vcTypeOfIdentificationCode followed by a ":"
ROLE="CREATOR" TYPE="OTHER" OTHERTYPE="SOFTWARE"
Describes the creation software for package
If no common name for the software use a describing text
Use note element to state the version
ROLE="PRESERVATION" TYPE="ORGANIZATION"
Describes the unit or organisation who administrates the e-archive
An note element will be used to state the identification number
The identification number will be type identified with a prefix from vcTypeOfIdentificationCode followed by a ":"
ROLE="CREATOR" TYPE="INDIVIDUAL"
Describes the person who can be contacted regarding the delivery in the delivery moment.
Use note to state contacts phone number and e-mail
This information is only valid for a short period
The metsHdr-element must contain the metsDocumentID-element
Is set according to rules in extending profiles. The recommendetion is to use the METS-file name.
The metsHdr-element must contain at least three altRecordID-element.
TYPE="DELIVERYTYPE"
Describes the delivery type the package belongs to
TYPE="DELIVERYSPECIFICATION"
Describes the delivery specification the package belongs to
TYPE="SUBMISSIONAGREEMENT"
Describes identification and date for delivery agreement
TYPE="PREVIOUSSUBMISSIONAGREEMENT"
Identification and date for previous submission agreement
TYPE="DATASUBMISSIONSESSION"
Identification of submission in submission session
TYPE="PACKAGENUMBER"
Identification of serial number
TYPE="REFERENCECODE"
Reference code in archival description
TYPE="PREVIOUSREFERENCECODE"
Previous reference code in archival description
TYPE="APPRAISAL"
States if the package as a whole can be appraised or not
TYPE="ACCESSRESTRICT"
States if the package contains accessrestrictions
Zero or more dmdSec is present
The attribute ID contains the unique identifier (for example UUID or GUID) and starts with an added "ID" for the element in the METS-document
The attribute ID's starts with an added "ID"
mdWrap or mdRef is used
xmlData or binData is used
The recommendation is to use xmlData
When embedding is used, a namespaces prefix is used.
The mdWrap-element attributes used: MDTYPE= According to METS-schema OTHERMDTYPE= According to vcOTHERMDTYPE
An mdRef element referencing metadata in a file in the case of the file being to large to embedd
The mdRef-element attributes used: The attribute ID contains the unique identifier (for example UUID or GUID) and starts with an added "ID" for the element in the METS-document MIMETYPE according to the referenced files mimetype LOCTYPE="URL" MDTYPE according to METS-schema OTHERMDTYPE= According to vcOTHERMDTYPE MDTYPEVERSION records filformat and version for the file in the form "format name";"version";"format registry";"formatkey" SIZE according to the referenced filesize in bytes CREATED according to the date of the referenced file in the format yyyy-mm-ddThh:mm:ss+01:00 CHECKSUMTYPE according to METS-schema (Not mandatory) CHECKSUM the calculated checksum value (Not mandatory) xlink:type="simple" xlink:href="file:nameOfFile.xml" this is the name of the file and it has prefix file:
In case of a persistent link referenced in the IP the mdRef-element attributes used:
The mdRef-element attributes used: The attribute ID contains the unique identifier for the element in the METS-document LOCTYPE="URL" MDTYPE according to METS-schema OTHERMDTYPE= According to vcOTHERMDTYP xlink:type="simple" xlink:href="http://nameOfReference.html" this is the referenced link
Zero or more amdSec is present
The attribute ID contains the unique identifier (for example UUID or GUID) and starts with an added "ID" for the element in the METS-document
The attribute ID's value starts with ID
When embedding is used, a namespaces prefix is used.
The mdWrap-element attributes used: MDTYPE= According to METS-schema OTHERMDTYPE= According to vcOTHERMDTYPE
xmlData or binData is used
The recommendation is to use xmlData
An mdRef element referencing the location of metadata in the case of the file being to large to embed
The mdRef-element attributes used: The attribute ID contains the unique identifier (for example UUID or GUID) and starts with an added "ID" for the element in the METS-document MIMETYPE according to the referenced files mimetype LOCTYPE="URL" MDTYPE according to METS-schema OTHERMDTYPE= According to vcOTHERMDTYPE MDTYPEVERSION records filformat and version for the file in the form "format name";"version";"format registry";"formatkey" SIZE according to the referenced filesize in bytes CREATED according to the date of the referenced file in the format yyyy-mm-ddThh:mm:ss+01:00 CHECKSUMTYPE according to METS-schema (Not mandatory) CHECKSUM the calculated checksum value (Not mandatory) xlink:type="simple" xlink:href="file:nameOfFile.xml"
No rightMD is required
The attribute ID contains the unique identifier (for example UUID or GUID) and starts with an added "ID" for the element in the METS-document
The attribute ID's value starts with "ID"
mdWrap or mdRef is used
Zero or more techMD is present
The attribute ID contains the unique identifier (for example UUID or GUID) and starts with an added "ID" for the element in the METS-document
The attribute ID's value starts with "ID"
mdWrap or mdRef is used
Zero or more digiprovMD is present
The attribute ID contains the unique identifier (for example UUID or GUID) and starts with an added "ID" for the element in the METS-document
The attriubte ID's value starts with "ID"
The recommendation is to use PREMIS for this type of information
mdWrap or mdRef is used
No sourceMD is required
The attribute ID contains the unique identifier (for example UUID or GUID) and starts with an added "ID" for the element in the METS-document
The attribute ID's value starts with "ID"
mdWrap or mdRef is used
One fileSec element is present
There are one or more fileGrp elements.
The attribute USE is strongly recommended
Each file element should have this attributes set (mandatory): ID contains the unique identifier (for example UUID or GUID) and starts with an added "ID" for the element in the METS-document MIMETYPE according to the referenced files mimetype LOCTYPE according to METS-schema xlink:href records the filename SIZE according to the referenced filesize in bytes CREATED according to the date of the referenced file in the format yyyy-mm-ddThh:mm:ss+01:00 USE records filformat and version for the file in the form "format name";"version" after that ;"format registry"(according to vcTypeOfFormatregistry):"formatkey"
Recommended attributes for the file element not mandatory: CHECKSUMTYPE according to METS-schema (This is a change from the origination work made by ENSAM) CHECKSUM the calculated checksum value (This is a change from the origination work made by ENSAM) GROUPID to identify files with special function ADMID can referens to the technical metadata id (example: ID550e8400-e29b-41d4-a716-4466554400xx) referencing the correct technical metadata section DMDID can referens to the descreptive metadata id (example: ID550e8400-e29b-41d4-a716-4466554400aa) referencing the correct descriptive metadata section
Each file element will have a FLocat-element pointing to the referenced file
Each FLocat element will have these attributes set: LOCTYPE according to METS-schema xlink:type="simple" xlink:href="file:nameOfFile.xml"
Every xlink:href will have the prefix "file:" before the filename.
transformFile can be used to give encryptionkey and algorithm for encrypted files
Elements and attriubtes mandatory when using transformFile is used.
Attributes TRANSFORMTYPE, TRANSFORMKEY, TRANSFORMALGORITHM and TRANSFORMORDER are used
One or more structmap-elements is present
When there are more than one structmap use of the attribute LABEL is recommended for describing what the structmap is presenting
The structmap are built up with div's according to extending profile.
Can contain one or more div-elements
Contains zero or more pointers to files, fptr
div/fptr/FILEID points to one file in the filesec
Recommended attributes for the div element not mandatory: LABEL according to extending profiles vocabulary ADMID referencing zero or more ADMID's used for files referenced through fptr-elements DMDID referencing zero or more DMDMID's used for files referenced through fptr-elements
No structLink is required
No behaviorSec is required
No multiSection is required
Requirements which span METS documents sections should appear in the multiSection subelement
All content files should follow known specifications.
All xml-files should have their schemas with them as a part of the package, to allow validation aganist the correct schema.
The schemas should in the structmap be grouped thogether and have a label that indicates that it's a group of schemas
No behavior requirements requiered
None
No tool exist at this moment