This profile will be used for composing Submission Information Packages (SIPs) for deliveries of digitized newspapers to the digital archive of the National Library
While the schema referenced above represents v.3.4 of MODS, all v.3.x MODS schemas are largely backwards compatible with previous incremental releases of version 3. METS documents using any version 3 MODS schema are accommodated by this profile.
This schema may also be used in the following contexts: mets/amdSec/righsMD/mdWrap/xmlData and mets/amdSec/digiprovMD/mdWrap/xmlData.
All applications of the MODS schema in conforming METS documents should follow the MODS User Guidelines published by Library of Congress' Network Development and MARC Standards Office (http://www.loc.gov/standards/mods/v3/mods-userguide.html).
"SIP" is the the only supported value for the TYPE attribut in METS for objects confirming to this profile.
These are supported values for the OTHERMDTYPE attribute in METS for objects confirming to this profile.
These are the extended namespaces for objects confirming to this profile.
SUPPLEMENT - extends the previous delivery
REPLACEMENT - replaces the previous delivery
NEW - a new delivery
TEST - a test delivery
DELIVERYTYPE - Which deliverytype does the package belong to
DELIVERYSPECIFICATION - Deliveryspecification for delivery type
SUBMISSIONAGREEMENT - Identification and date for delivery agreement
Agreement - Material delivered to a library with a special agreement for exampel when e-plikt isn't the case - Överenskommen leverans
This is the only supported value for checksum algorithms for objects confirming to this profile.
These are the orginially supported values for the USE attribute for objects confirming to this profile.
These are the orginially supported values for the LABEL attribute within the dmdSec element for objects confirming to this profile.
These are the supported values for the TYPE attribute within the structMap element for objects confirming to this profile.
These are the supported values for the TYPE attribute within the div element for objects confirming to this profile.
These are the supported values for the LABEL attribute within the div element for objects confirming to this profile.
Xsi definititions should be made according to vcNAMESPACES and vcNAMESPACES_extended
The following schema locations are used to make xml-files following this profile able to validate
PROFILE is set to "kbse_mets_profile_001.xml"
OBJID is the unique identifier of the package decided by the supplier
TYPE is set to "SIP"
LABEL - the value here is a descriptive title for the package and the same as in the mods:title element within dmdSec (dmdSec/@LABEL="Primary").
ID is used and referencing the METS document file name.
The METS document filename does not contain Swedish characters, space or special characters. The filename starts with an alphabetic character and end with the suffix ".mets.metadata".
The metsDocumentID contains the same value as the ID attribute, see requirements 3 and 4.
The RECORDSTATUS attribute can be set to indicate the status of the package
RECORDSTATUS uses a vocabulary
The metsHdr element contains two agent elements.
ROLE="ARCHIVIST" TYPE="ORGANIZATION"
Describes the archival creator. Value in the name element is set to "Kungliga biblioteket"
ROLE="CREATOR" TYPE="ORGANIZATION"
Describes the unit or organisation resposible for creation and delivery of the METS document. Example of value in the name element: Riksarkivet/DIT
The metsHdr-element may 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
Conforming METS documents contains two or more dmdSec elements with MODS metadata.
This dmdSec is the "primary" metadata container for the newspaper issue described. The element mdWrap has the attribute LABEL set to "Primary".
For the set of MODS elements required, see http://www.kb.se/namespace/mods
This dmdSec contains local information about the publisher and the supplier of the package. The mdWrap element has the LABEL attribute value set to "Local".
For the set of MODS elements required, see http://www.kb.se/namespace/mods
Conforming METS documents may contain one or more separate dmdSec elements with MODS metadata, describing for example a physical section of a newspaper or journal issue and associated supplements or newsbills, or one or several volumes of a monograph. The dmdSec container must be repeted for each physical section, supplement, newsbill and volume.
The MODS elements required, see http://www.kb.se/namespace/mods
The attribute ID contains the unique identifier for the element in the METS document following the pattern dmdSec001, dmdSec002 etc.
mdWrap is used
MDTYPE value is set to "MODS" according to METS schema
xmlData is used
Conforming METS documents contains one and only one amdSec element.
The attribute ID contains the unique identifier for the element in the METS document. Values following the pattern amdSec001, amdSec002, etc.
Conforming METS documents may contain zero or many rightsMD elements.
Metadata in a rightsMD element appearing in a mdWrap element in a compliant document should conform to the PREMIS:RIGHT schema.
Specification of elements in PREMIS:RIGHT, see http://www.kb.se/namespace/premis.
The attribute ID contains the unique identifier for the rightsMD element in the METS document, values following the pattern rightMD001, rightMD002, etc.
Conforming METS documents contains one techMD element with PREMIS:OBJECT metadata for the "representation" level. This is the metadata container for collected information about the files and/or bitstreams constituating the instance of the resource within the package.
Specification of elements in PREMIS:OBJECT, see http://www.kb.se/namespace/premis
Conforming METS documents contains one techMD element with PREMIS:OBJECT metadata for each datafile and/or bitstream.
Specification of elements in PREMIS:OBJECT, see http://www.kb.se/namespace/premis
The attribute ID contains the unique identifier for the techMD element in the METS document, values following the pattern techMD001, techMD002, etc.
mdWrap is used
MDTYPE value is set to "PREMIS" according to METS schema
xmlData is used
Each fileGrp contains an associated ID attribute with the unique identifier for the element in the METS-document, values following the pattern fileGrp001, fileGrp002, etc.
Each fileGrp element contains an associated USE attribute, according to vcUSE_kbse.
Each file element has an associated ID attribute with the unique identifier for the element in the METS-document, values following the pattern file1, file2, file3, etc.
Each file element has an associated MIMETYPE attribute. This attribute contains the official MIME type value for the content file represented.
Each file element has an associated SIZE attribute according to the referenced filesize in bytes. This size value is repeated within the techMD element (PREMIS:OBJECT).
Each file element has an associated CREATED attribute according to the date of the referenced file in the format yyyy-mm-ddThh:mm:ss+01:00.
Each file element has an associated CHECKSUMTYPE attribute containing the value "MD5" according to vcCHECSUMTYPE. Checksum type is repeated within the techMD element (PREMIS:OBJECT).
Each file element has an associated CHECKSUM attribute containing the calculated checksum value. Calculated checksum value is repeated within the techMD element (PREMIS:OBJECT)
Each file element has an associated USE attribute according to vcUSE_kbse.
Each file element has one or many associated ADMID attribute referencing the correct administrative metadata section(s) - techMD (rightsMD) - used for files referenced through the FLocat element.
Each file element has a FLocat element pointing to the referenced file.
Each FLocat element has an associated LOCTYPE attribute containing the "URL" value.
Each FLocat element has an associated xlink:type attribute containing the "simple" value.
Each FLocat element has an associated xlink:href attribute containing the name of the file preceded by the prefix "file:" value. "file:[name of file]".
Each structMap contains a TYPE attribute according to the vocabulary in vcSTRUCTMAP_TYPE_kbse.
One structMap contains a TYPE attribute with the value set to "physical".
Each structMap element has an associated ID attribute with the unique identifier for the element in the METS-document, values following the pattern structMap001, structMap002, etc.
Each structMap element contains one or more div elements.
Each div element contains an associated ID attribute containing the unique identifier for the element in the METS-document, values following the pattern div001, div002, etc.
Each div element contains a TYPE attribute value according to vcDiv_TYPE_kbse.
A Each div element may or may not contain a LABEL attribute value according to vcDiv_LABEL_kbse.
The mandatory structMap - TYPE "physical" - contains one div element with the TYPE attribute set to "files".
The div element tagged with TYPE="files" contains one div element with the TYPE attribute set to "issue" or "monograph".
The div element tagged with TYPE="issue" or TYPE="monograph" contains the attribute ADMID referencing to the techMD with PREMIS:OBJECT metadata for the "representation" level.
The div element tagged with TYPE="issue" or TYPE="monograph" contains the attribute DMDID referencing to the dmdSec with "primary" metadata about the issue (mdWrap LABEL="Primary").
The div element tagged with TYPE="issue" contains one ore more div elements with the TYPE attribute value set to "page".
The div element tagged with TYPE="monograph" contains one ore more div elements with the TYPE attribute value set to "volume".
The div element tagged with TYPE="issue" contains one ore more div elements with the TYPE attribute value set to "section", "supplement" or "newsbill".
Each div elements with TYPE attribute set to "section", "supplement" and "newsbill" contains one ore more div elements with TYPE value "page".
The div element tagged with TYPE="volume" contains one ore more div elements with the TYPE attribute value set accordning to vcDiv_TYPE_kbse.
Each div element following under those with TYPE attribute set to "volume" or "issue" contains the attribute ORDER with a value 1, 2, 3, etc., indicating the sequence order of all the images in the package
The div element tagged with TYPE="files" contains one div element with the TYPE attribute set to "performance".
All xml-files should have their schemas with them as a part of the package, to allow validation using 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 tool exist at this moment