 The
Library of Congress >> Standards |
|
 |
|
 |
|
| |
|
|
|
METS_Profile:
@xsi:schemaLocation="http://www.loc.gov/METS_Profile/ http://www.loc.gov/standards/mets/profile_docs/mets.profile.v1-2.xsd"
title:
UC San Diego Complex Object Profile abstract:
The UC San Diego Libraries uses the UC San Diego Complex Object profile for composing METS instances for digital objects in which the primary content of the digital object is contained in two or more digital files. The content files must be in an archival quality file format supported by the UC San Diego Libraries (see https://libraries.ucsd.edu/ark:/20775/br61775312/1-1.pdf). There can be any combination of formats within a single complex object. There are no restrictions placed on the type of logical structure represented in the complex object. The decision to require a complex object’s structure to be represented by both physical and logical <structMap>s, as described in the profile, is influenced by the current requirements of the METS Navigator application. This revision of the previous version of the UCSD Complex Object Profile is motivated by the opportunity to express all rights metadata for an object via the PREMIS metadata standard. date:
2009-04-21T10:53:31 contact:
name:
Digital Library Program address:
Geisel Library, University of California, San Diego email:
dlp@ucsd.edu related_profile:
@RELATIONSHIP="Supersedes"
@URI="http://www.loc.gov/standards/mets/profiles/00000017.xml"
UC San Diego Complex Object Profile related_profile:
@RELATIONSHIP="Extends"
UC San Diego Simple Object Profile extension_schema:
name:
MODS context:
mets/dmdSec/mdWrap/xmlData note:
Used for descriptive metadata representing the intellectual object. extension_schema:
name:
PREMIS context:
mets/amdSec/techMD/mdWrap/xmlData note:
Used for technical and rights metadata about content files. description_rules:
All applications of MODS in UC San Diego METS records adhere to the MODS User Guidelines published by the Library of Congress's Network Development and MARC Standards Office. MODS usage in UC San Diego METS records is also informed by The Digital Library Federation / Aquifer Implementation Guidelines for Shareable MODS Records. controlled_vocabularies:
vocabulary:
name:
UC San Diego file USE attribute values maintenance_agency:
University of California, San Diego Libraries context:
@ID="vc1"
@RELATEDMAT="fileSec2"
mets/fileSec/fileGrp/@USE mets/fileSec/fileGrp/file/@USE Each <fileGrp> must include a file USE attribute, with a value taken from the UCSD controlled vocabulary for file use attributes referenced above, representing the intended use of the referenced file(s).description:
These are the values supported for <file> and <fileGrp> USE attributes for digital objects conforming to this profile. vocabulary:
name:
UC San Diego Rights Basis Vocabulary maintenance_agency:
University of California, San Diego Libraries context:
@ID="vc2"
@RELATEDMAT="copyrightMD2 licenserightsMD2 statuterightsMD2"
mets/amdSec/rightsMD/mdWrap/xmlData/rightsStatement/rightsBasis description:
These are the values supported for the PREMIS rightsBasis element for digital objects conforming to this profile. vocabulary:
name:
UC San Diego Rights Status Vocabulary maintenance_agency:
University of California, San Diego Libraries context:
@ID="vc3"
@RELATEDMAT="copyrightMD3"
mets/amdSec/rightsMD/mdWrap/xmlData/rightsStatement/copyrightStatus A conforming METS record must include a rightsStatement/copyrightInformation/copyrightStatus element with the value expressed as "Under copyright” if the work is still in copyright to an agent other than UC Regents, "Copyright UC Regents" if the work is copyrighted to the UC Regents, “Public Domain” if copyright for the work has expired or been gifted to the public domain, or "Unknown" if the copyright status of the work cannot be determined.description:
These are the values supported for the PREMIS copyrightStatus element for digital objects conforming to this profile. vocabulary:
name:
UC San Diego Rights Actions Vocabulary maintenance_agency:
University of California, San Diego Libraries context:
@ID="vc4"
@RELATEDMAT="licenserightsMD3 licenserightsMD4 statuterightsMD4"
mets/amdSec/rightsMD/mdWrap/xmlData/rightsStatement/rightsGranted/restriction mets/amdSec/rightsMD/mdWrap/xmlData/rightsStatement/rightsGranted/action description:
These are the values supported for the PREMIS act and restriction elements for digital objects conforming to this profile. structural_requirements:
metsRootElement:
requirement:
@ID="metsRoot3"
The root <mets> element must include an OBJID attribute value that uniquely identifies the METS instance in the UC San Diego digital repository. The value must be an ARK. . metsHdr:
requirement:
@ID="metsHdr1"
A METS record conforming to this profile must contain a <metsHdr> element. requirement:
@ID="metsHdr3"
The <metsHdr> element must contain an <agent> with the ROLE attribute value "CREATOR" and a TYPE attribute value "ORGANIZATION". requirement:
@ID="metsHdr4"
The <agent> element must contain the <name> element with the value "Digital Library Program, Geisel Library, University of California, San Diego", and a <note> element with the value "mailto:dlp@ucsd.edu". requirement:
@ID="metsHdr5"
The <metsHdr> element should, but is not required to, contain a LASTMODDATE attribute reflecting the date of the last modification to the METS record. dmdSec:
requirement:
@ID="dmdSec1"
A METS record conforming to this profile must contain at least one <dmdSec> containing a <mdWrap> with <xmlData>. requirement:
@ID="dmdSec3"
The required dmdSec/mdWrap/xmlData must contain elements from the Metadata Object Description Schema (MODS) and describe the digital object as a whole. requirement:
@ID="dmdSec5"
A conforming METS record must contain a mods/typeOfResource element for which the value must be taken from the MODS typeOfResource values. Type of resource values should be determined by the materials content and not the file format. For example an image of a page of text should have the value "text". requirement:
@ID="dmdSec6"
A conforming METS record must contain a mods/identifier element, with the attribute type="ARK". The element should contain the actionable URL ARK for the digital object as a whole, not a constituent file. requirement:
@ID="dmdSec7"
A conforming METS record must contain a mods/note element, with the attribute displayLabel="Digital object made available by". The element should name the UC San Diego Libraries' data provider that is primarily responsible for making the resource available digitally with the URL for the provider's main webpage, e.g. Mandeville Special Collections Library, University of California, San Diego, La Jolla, CA 92093-0175 (http://orpheus.ucsd.edu/speccoll/) requirement:
@ID="dmdSec8"
A conforming METS record should, but is not required to, contain the following descriptive metadata elements when they are applicable: creator (mods/name/namePart), date of creation (mods/originInfo/dateCreated), genre (mods/subject/genre), description (mods/abstract), subject (mods/subject/...), language of the object (mods/language), publisher (mods/originInfo/publisher), place of publication (mods/originInfo/place) and the name of the project or collection to which the object belongs (mods/relatedItem/titleInfo/title). requirement:
@ID="dmdSec9"
If present, descriptive metadata for each component part of the digital object must be placed in a separate <dmdSec> element and expressed with the MODS metadata schema. requirement:
@ID="dmdSec10"
If parallel description, in a schema other than MODS (e.g., Dublin Core, VRA, FGDC, etc.), is provided for the object or its components, each parallel description must be placed in a separate <dmdSec> element. When adding elements from metadata schemas, these should conform to standardized guidelines for the schema. amdSec:
requirement:
@ID="amdSec1"
A METS record conforming to this profile must have an <amdSec> section. The <amdSec> section must contain at least one techMD/mdWrap/xmlData section and at least one rightsMD/mdWrap/xmlData section pertaining to the digital object as a whole. requirement:
@ID="techMD1"
The required <techMD> sections must contain elements from the PREMIS schema. requirement:
@ID="techMD2"
The required <techMD> sections should describe the digital files of the greatest archival quality and from which derivatives are typically generated. requirement:
@ID="techMD3"
A conforming METS record must contain a pre/object/objectIdentifier/objectIdentifierType element with the value "ARK", and a pre/object/objectIdentifier/objectIdentifierValue element with the unique ID. requirement:
@ID="techMD4"
A conforming METS record must contain a pre/object/preservationLevel element. The value should be either "Full" or "Bit-level". requirement:
@ID="techMD5"
A conforming METS record must contain a pre/object/objectCategory element. The value should be "File". requirement:
@ID="techMD6"
A conforming METS record must contain a pre/object/objectCharacteristics/compositionLevel element. The value should be "0" for uncompressed files. requirement:
@ID="techMD7"
A conforming METS record must contain a pre/object/objectCharacteristics/fixity/messageDigestAlgorithm element and a pre/object/objectCharacteristics/fixity/messageDigest element. requirement:
@ID="techMD8"
A conforming METS record must contain a pre/object/objectCharacteristics/size element. requirement:
@ID="techMD9"
A conforming METS record must contain a pre/object/objectCharacteristics/format/formatName element. requirement:
@ID="techMD10"
A conforming METS record must contain a pre/object/creatingApplication/dateCreatedByApplication element. requirement:
@ID="techMD11"
A conforming METS record should, but is not required to, include the following PREMIS elements: medium on which the object is stored (pre/object/storage/storageMedium), file format version (pre/object/objectCharacteristics/formatDesignation/formatVersion), name of the application that created the file (pre/object/creatingApplication/creatingApplicationName), and the original file name (pre/object/originalName) requirement:
@ID="techMD12"
Additional <techMD> sections may, but are not required to, be used for the description of files other than the master file, or for inclusion of format specific metadata for any file. requirement:
@ID="techMD13"
Additional format specific <techMD> sections for the description of images must be expressed with the MIX schema. requirement:
@ID="techMD14"
Additional format specific <techMD> sections for the description of text must be expressed with the TextMD schema. requirement:
@ID="techMD15"
Additional format specific <techMD> sections for the description of audio or video, should conform to an extension schema endorsed by the METS Editorial Board (although at this date of publication extension schemas have not yet been endorsed for audio or video). requirement:
@ID="techMD16"
Source or provenance metadata, expressed as MIX metadata pertaining to image content files, can be included in a <techMD> section instead of a separate <sourceMD> section. requirement:
@ID="copyrightMD1"
The required rightsMD/mdWrap/xmlData must contain elements from the PREMIS Rights schema. requirement:
@ID="copyrightMD2"
A conforming METS record must include a rightsStatement/rightsBasis element with the value expressed as "Copyright." requirement:
@ID="copyrightMD3"
A conforming METS record must include a rightsStatement/copyrightInformation/copyrightStatus element with the value expressed as "Under copyright” if the work is still in copyright to an agent other than UC Regents, "Copyright UC Regents" if the work is copyrighted to the UC Regents, “Public Domain” if copyright for the work has expired or been gifted to the public domain, or "Unknown" if the copyright status of the work cannot be determined. requirement:
@ID="copyrightMD4"
A conforming METS record may include a rightsStatement/copyrightInformation/copyrightJurisdiction element containing the appropriate code for the jurisdictional context of the copyright with a value taken from ISO 3166. requirement:
@ID="copyrightMD5"
A conforming METS record may have one rightsStatement/copyrightInformation/copyrightNote element for identifying the rights holder(s). The value encoded is to be the name of the copyright holder(s)and should be in the form of: “Rights Holder(s): [rights holder’s name in normal order]". requirement:
@ID="copyrightMD6"
A conforming METS record must have one rightsStatement/copyrightInformation/copyrightNote elment for describing the use intended for in distribution of the work. The note should be in the form of: “Use: [note text]”. requirement:
@ID="copyrightMD7"
A conforming METS record must have one rightsStatement/copyrightInformation/copyrightNote element for describing constraints placed on re-use or re-distribution of the work. The note should be in the form of: “Constraint(s) on Use: [note text]”. requirement:
@ID="licenserightsMD1"
Additional rightsMD/mdWrap/xmlData elements must contain elements from the PREMIS Rights schema. requirement:
@ID="licenserightsMD2"
A conforming METS record may include a rightsStatement/rightsBasis element with the value expressed as "License". requirement:
@ID="licenserightsMD3"
When rightsBasis is "License", a conforming METS record must include a rightsStatement/rightsGranted/act element with a value from the UC Libraries Rights Actions Vocabulary. requirement:
@ID="licenserightsMD4"
In cases when an action is not permitted, a conforming METS record must include a rightsStatement/rightsGranted/restriction element with a value from the UC Libraries Rights Actions Vocabulary. requirement:
@ID="licenserightsMD5"
In cases when an action is restricted, a conforming METS record must include a rightsStatement/rightsGranted/termOfGrant/startDate element with the value indicating the time at which the restriction begins. Date must be expressed in form YYYY-MM-DD. requirement:
@ID="licenserightsMD6"
In cases when public display is restricted, a conforming METS record must include a rightsStatement/rightsGranted/termOfGrant/endDate element with the value indicating the time at which the restriction concludes. Date must be expressed in form YYYY-MM-DD. requirement:
@ID="licenserightsMD7"
A conforming METS record may, but is not required, to include the following PREMIS Rights elements: <pre:rightsStatementIdentifierType> (/rightsStatement/rightsStatementIdentifier/rightsStatementIdentifierType), <pre:rightsStatementIdentifierValue> (/rightsStatement/rightsStatementIdentifier/rightsStatementIdentifierValue), <pre:licenseIdentifierType> (/rightsStatement/licenseInformation/licenseIdentifier/licenseIdentifierType), <pre:licenseIdentifierValue> (/rightsStatement/licenseInformation/licenseIdentifier/licenseIdentifierValue), <pre:licenseTerms> (/rightsStatement/licenseInformation/licenseTerms), <pre:licenseNote> (/rightsStatement/licenseInformation/licenseNote), and <pre:rightsGrantedNote> (/rightsStatement/rightsGranted/rightsGrantedNote), requirement:
@ID="statuterightsMD1"
Additional rightsMD/mdWrap/xmlData elements must contain elements from the PREMIS Rights schema. requirement:
@ID="statuterightsMD2"
A conforming METS record may include a rightsStatement/rightsBasis element with the value expressed as "Statute". requirement:
@ID="statuterightsMD3"
When rightsBasis is "Statute", a conforming METS record must include a rightsStatement/statuteInformation/statuteCitation to identify the applicable statute.The preferred citation is the name of the citation and a URI linking to it. requirement:
@ID="statuterightsMD4"
In cases when legal statute prohibits prohibits an action, a conforming METS record must include a rightsStatement/rightsGranted/restriction element with a value from the UC Libraries Rights Actions Vocabulary. requirement:
@ID="statuterightsMD5"
In cases when an action is restricted, a conforming METS record must include a rightsStatement/rightsGranted/termOfGrant/startDate element with the value indicating the time at which the restriction begins (typically, the date the content was created). Date must be expressed in form YYYY-MM-DD. requirement:
@ID="statuterightsMD6"
In cases when public display is restricted, a conforming METS record must include a rightsStatement/rightsGranted/termOfGrant/endDate element with the value indicating the time at which the restriction concludes. Date must be expressed in form YYYY-MM-DD. requirement:
@ID="statuterightsMD7"
A conforming METS record may, but is not required, to include the following PREMIS Rights elements: <pre:rightsStatementIdentifierType> (/rightsStatement/rightsStatementIdentifier/rightsStatementIdentifierType), <pre:rightsStatementIdentifierValue> (/rightsStatement/rightsStatementIdentifier/rightsStatementIdentifierValue), <pre:licenseIdentifierType> (/rightsStatement/licenseInformation/licenseIdentifier/licenseIdentifierType), <pre:licenseIdentifierValue> (/rightsStatement/licenseInformation/licenseIdentifier/licenseIdentifierValue), <pre:licenseTerms> (/rightsStatement/licenseInformation/licenseTerms), <pre:licenseNote> (/rightsStatement/licenseInformation/licenseNote), and <pre:rightsGrantedNote> (/rightsStatement/rightsGranted/rightsGrantedNote), requirement:
@ID="sourceMD1"
If source metadata is recorded, elements in the <sourceMD> sections should be expressed using an extension schema endorsed by the METS Editorial Board designed for expressing source metadata (although at this date of publication an extension schema has not yet been endorsed for source metadata). requirement:
@ID="digiprovMD1"
If provenance metadata is recorded, elements in the <digiprovMD> sections should be expressed using an extension schema endorsed by the METS Editorial Board designed for expressing provenance metadata (although at this date of publication an extension schema has not yet been endorsed for provenance metadata). fileSec:
requirement:
@ID="fileSec1"
The <fileSec> for a compliant METS record must contain one, or more, <fileGrp> elements. requirement:
@ID="fileSec2"
Each <fileGrp> must include a file USE attribute, with a value taken from the UCSD controlled vocabulary for file use attributes referenced above, representing the intended use of the referenced file(s). requirement:
@ID="fileSec4"
Each <file> element must reference pertinent <techMD> sections by including the relevant ID values in the ADMID attribute. The ADMID attribute should also reference pertinent <sourceMD> and <provenanceMD> elements, if present. The <file> element should only reference ID values at the levels of <techMD>, <sourceMD>, and <digiprovMD>. structMap:
requirement:
@ID="structMap1"
A conforming METS record must contain two <structMap> elements, one with the TYPE attribute value encoded as "logical", a second with the value encoded as "physical". requirement:
@ID="structMap2"
The physical <structMap> represents a flattened structure and must only contain two levels of <div> elements with no further nesting. The top level <div> element required by the METS schema contains one level of child <div> elements to represent the linear sequence of the components of the digital object. requirement:
@ID="structMap3"
The logical structMap represents the full hierarchical structure of the digital object, and so can contain as many levels of nested <div> elements as required to express the object's full structure. requirement:
@ID="structMap4"
All <div> elements within the top level containing <div> must have an ORDER attribute. requirement:
@ID="structMap5"
When applicable, <div> elements must reference pertinent <dmdSec> sections by including the relevant ID values in the DMDID attributes. requirement:
@ID="structMap6"
When applicable, <div> elements should include a LABEL attribute with the value derived from, and identical, to the value encoded in the /mods/titleInfo/title element in the related <dmdSec>. requirement:
@ID="structMap7"
When applicable, <div> elements must reference pertinent <rightsMD> sections by including the relevant ID values in the ADMID attributes. requirement:
@ID="structMap8"
Each <fptr> element must reference an individual <file> element representing a version of the file. requirement:
@ID="structMap9"
The <fptr> element must use the FILEID attribute to point directly to a <file> element. requirement:
@ID="structMap10"
The <fptr> element may not contain an <area>, <par>, or <seq> element. These elements are not supported in objects conforming to this profile. structLink:
requirement:
@ID="structLink1"
This profile stipulates no requirements for the <structLink> element. behaviorSec:
requirement:
@ID="behaviorSec1"
This profile stipulates no requirements for the <behaviorSec> element. multiSection:
requirement:
@ID="multi1"
Only <file> elements will reference elements in the <techMD>, <sourceMD>, and <digiprovMD> sections. requirement:
@ID="multi2"
Only the <div> element will reference metadata in the <dmdSec> and <rightsMD> sections. That is, descriptive metadata and rights metadata are always and only expressed in conjunction with division of the <structMap> and not in conjunction with the content file(s). technical_requirements:
content_files:
requirement:
The profile does not prescribe a format for the file, but it is strongly recommended that the file format and resolution for at least one version of the image be of an archival quality. metadata_files:
requirement:
This profile does not prescribe referencing of external metadata records. If an external metadata record is referenced, it is recommended that the file be valid for the schema in which it is written, i.e., that it be a valid MARC record. tool:
description:
Some of the requirements of this profile, especially the requirement for two <structMap>s, are influenced by the METS Navigator application as it is currently available. |
 Top
of Page |
||||
| |
|
|||
|
|
|||
|
||||