It's recommended that context data confirms to all sutible standards
mets/@TYPE
This are the supported valus for the TYPE attribut in mets for objects confirming to this profile.
mets/fileSec/fileGrp/file/@USE
These are the supported values for element file USE attributes in objects conforming to this profile.
Explanation for the values:"Packages" is the USE-value for the filegroup containing the TAR-file. For filegroups there are no mimetypes.
"Package" is the USE-value used for the TAR-file containing the preserved files. Mimetype for TAR-files is "application/x-tar".
"Files" is the USE-value used for the filegroup containing the preserved files. For filegroups there are no mimetypes.
The USE-values "Datafile, "Manual" and "Information" are used for files created by agencies and delivered to the National Archives. The USE-values can be retrieved from the ADDML-file. For files lacking USE-values in the ADDML-file the default value is "Datafile".
The USE-value "Datafile" is used for files marked as "Datafile" in the ADDML-file. Mimetypes for "Datafile" can be one of the mime-types the National Archives accepts for archival files. Mimetypes can be "application/pdf", "application/xml-dtd", "application/xhtml-xml", "application/xslt-xml", "audio/mpeg", "image/gif", "image/jpeg", "image/jp2", "image/png", "image/tiff", "text/css", "text/csv", "text/html", "text/plain", "text/xml", "video/mpeg".
The USE-value "Manual" is used for files marked as "manual" in a ADDML-file. All mime-types used for "Datafile" can also be used for "manual".
The USE-value "Information" is used for all files marked as "information" in a ADDML-file. All mime-types used for "Datafile" can also be used for "information".
The USE-values "RA Datafile, "RA Manual" and "RA Information" are used for files created by the National Archives.
The USE-value "RA Datafile" is used for files marked as "RA Datafile" in a ADDML-file. All mime-types used for "Datafile" can also be used for "RA Datafile". All TIFF-files listed and described in RES-files are created by the National Archives. All files referenced in RES-files are given the USE value "RA Datafile".
The USE-value "RA Manual" is used for files marked as "RA manual" in a ADDML-file. All mime-types used for "RA Datafile" can also be used for "RA manuals".
The USE-value "RA Information" is used for all files marked as "RA information" in a ADDML-file. All mime-types used for "RA Datafile" can also be used for "RA information".
mets/amdSec/***MD/@OTHERMDTYPE
mets/structmap/div/@LABEL
mets/metsHdr/Agent/@OTHERROLE
mets/metsHdr/Agent/@OTHERTYPE
The following xsi-definititions are made:
xmlns="http://xml.ra.se/METS/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:premis="http://xml.ra.se/PREMIS"
SchemalocationsThe following schema locations are used to make xml-files following this profile able to validate
xsi:schemaLocation="http://xml.ra.se/METS/ http://xml.ra.se/METS/RA_METS_SWERA003.xsd"
AttributesThe attributes PROFILE, ID, OBJID, LABEL and TYPE values must be set
PROFILE is set to the profile from RA that has been used to create the document
ID is set to the METS-document filename. Example: Q2006061_METS.xml
OBJID is set to the batchID. Example: Q2006061
LABEL is set to a descriptive title. Example: Intern bildbatch lagring
TYPE is set according to vocabulary vc1. Example: AIP
FilenameThe name is made from PREMIS:ObjectIdentifierValue combined with the string "_METS". An ObjectIdentifierValue is set for all PREMIS-objects (including AIP:s) in the database. The ObjectIdentifierValue is typically an eight character code unique for all PREMIS-objects. The value is retrieved from the database and used as the basis for filenames.
METS-document filenameThe filename starts with the ObjectIdentifierValue and ends with "_METS". The extension is xml
Example: Q2006061_METS.xml
Packed filenameThe filename is the ObjectIdentifierValue. The extension is tar
Example: Q2006061.tar
The CREATEDATE attribute must be set.
CREATEDATE is set to creationdate of the package in the form yyyy-mm-ddThh:mm:ss+01:00
Agent-elementThe METS-header must contain one and only one agent-element.
All AIP:s are automatically created by one agent: The archival storage system.
Agent-element-attributesThe attribute ID is not used
The attribute ROLE is set to STORAGESYSTEM
The attribute TYPE is set to AUTOMATICCREATION
Agent-element-name-elementThe name-element is set to a string identifying the archival storage system.
Example: "ESSArch_Marieberg".
No dmdSec is present
Only one amdSec exist
The amdSec, identifies by an ID attribute with the value "amdSec001".
No rightMD is required
Each techMD element is given an identifier in the form "techMD001" etc, numbered sequentially.
mdWrapIn most cases each techMD element embedds the information
The mdWrap-element attributes used: MDTYPE= According to METS-schema OTHERMDTYPE= According to vc3
mdRefEach techMD element contains an mdRef element referencing the location of technical metadata in the case of the file beeing to large to embedd
The mdRef-element attributes used: ID contains the prefix "file" and the filename of the file that is referenced MIMETYPE="text/xml" LOCTYPE="URL" MDTYPE= According to METS-schema OTHERMDTYPE= According to vc3 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 xlink:type="simple" xlink:href="file:nameOfFile.xml"
Each digiprovMD element is given an identifier in the form "digiprovMD001" etc, numbered sequentially.
digprovMD contains references or embedds the PREMIS-files
In the PREMIS information MIX information is embedded in the case of the metadata is describing images.
mdWrapIn most cases each digiprovMD element embedds the information
The mdWrap-element attributes used: MDTYPE= PREMIS
mdRefEach digiprovMD element contains an mdRef element referencing the location of technical metadata in the case of the file beeing to large to embedd
The mdRef-element attributes used: ID contains the prefix "file" and the filename of the file that is referenced MIMETYPE="text/xml" LOCTYPE="URL" MDTYPE="PREMIS" xlink:type="simple" xlink:href="file:nameOfFile.xml"
No sourceMD is required
There are two fileGrp elements.
The first fileGrp consist of one and only one file-element refrencing the tar-package
The ID attribute is set to "fgrp001" and the USE attribute is set to "PACKAGES"
Second fileGrpThe second fileGrp consist of file-elements refrencing all the other files in the package
Descreptive metadafile and technical metadatafiles are also referenced here since they are a part of the package
The ID attribute is set to "fgrp002" and the USE attribute is set to "FILES"
Each file element will have this attributes set: ID contains the prefix "file" and the filename of the file that is referenced MIMETYPE according to the referenced file mimetype 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 set according to vocabulary vc2 ADMID referens to the technical metadata id (example: techMD001) referencing the correct technical metadata section CHECKSUM is used for files in fileGrp fgrp001 and is the checksum CHECKSUMTYPE is used for files in fileGrp fgrp001 and is the checksum algorithm
Each file element will have a FLocat-element pointing to the referenced file
Each FLocat element will have these attributes set: LOCTYPE="URL" xlink:type="simple" xlink:href="file:nameOfFile.xml"
One structmap is present
The structmap consist of one main div, this contains of upto six divs
Main divContains pointer to the packagefile
@LABEL has value "PACKAGE" according to vc4
@ADMID has all ASMID's
div/fptr/FILEID points to the packagefile
Div 1Contains pointer to all descriptive information, pointers to PREMIS-files, ADDML and RES
@LABEL has value "Content description" according to vc4
@ADMID has all ASMID's thar are in use
div/fptr/FILEID points to the descriptionsfiles
In cases where the metadata has been embedded this will be an empty div with only the required AMDID's referenced
Div 2Contains pointers to all datafiles
@LABEL has value "Datafiles" according to vc4
@ADMID has all ASMID's that are in use
div/fptr/FILEID points to the datafiles
Div 3Contains pointers to other informationfiles described as "Manuals"
@LABEL has value "Manuals" according to vc4
@ADMID has all ASMID's thar are in use
div/fptr/FILEID points to this files
Div 4Contains pointers to other informationfiles described as "Information"
@LABEL has value "Information" according to vc4
@ADMID has all ASMID's thar are in use
div/fptr/FILEID points to this files
Div 5Contains pointers to other informationfiles described as "RA Manuals"
@LABEL has value "RA Manuals" according to vc4
@ADMID has all ASMID's thar are in use
div/fptr/FILEID points to this files
Div 6Contains pointers to other informationfiles described as "RA Information"
@LABEL has value "RA Information" according to vc4
@ADMID has all ASMID's thar are in use
div/fptr/FILEID points to this files
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 follows the specification from RA.
No behavior requirements requiered
None
No tool exist at this moment