 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 Simple Object Profile abstract:
The UC San Diego Libraries uses the UC San Diego Simple Object profile for composing METS instances for digital objects consisting of a single digital content file and associated descriptive, administrative, and structural metadata. 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). The version of the previously registered Simple Object Profile has been revised for the purpose of expressing all rights metadata via the PREMIS schema. date:
2009-04-21T11:53:31 related_profile:
@RELATIONSHIP="Supersedes"
@URI="http://www.loc.gov/standards/mets/profiles/00000012.xml"
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 metadata about content files. Used for access restrictions to the 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. 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> element must contain one, and only one, file.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 one or more <dmdSec> containing a <mdWrap> with <xmlData>. The required dmdSec/mdWrap/xmlData must contain elements from the Metadata Object Description Schema (MODS). Additional <dmdSec> elements are permitted. For each additional metadata schema a separate <dmdSec> must be used, and must contain <mdWrap> with <xmlData>. When adding elements from metadata schemas other than MODS (Dublin Core, VRA, FGDC, etc.) these should conform to standardized guidelines for the schema. requirement:
@ID="dmdSec3"
A conforming METS record must contain a /mods/typeOfResource element for which the value must be taken from the MODS typeOfResource values. requirement:
@ID="dmdSec4"
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="dmdSec5"
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, e.g. Arts Library. The URL for the provider's main page should be included with its name. requirement:
@ID="dmdSec6"
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). 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 requirement:
@ID="techMD1"
The required <techMD> must contain elements from the PREMIS schema. A second <techMD> section may, but is not required to, be used if applicable for the format. If a second <techMD> is used for images, it should conform to the MIX Schema; if used for text, it should conform to the TextMD Schema; if used for audio or video, it 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="techMD2"
The required <techMD> should describe the digital file of the highest, most archival quality. requirement:
@ID="techMD3"
A conforming METS record must contain an /object/objectIdentifierType element with the value "ARK", and an /objectIdentifierValue element with the ARK value. requirement:
@ID="techMD4"
A conforming METS record must contain an /object/preservationLevel element. The value should be either "Full" or "Bit-level". requirement:
@ID="techMD5"
A conforming METS record must contain an /object/objectCategory element. The value should be "File". requirement:
@ID="techMD6"
A conforming METS record must contain an /object/objectCharacteristics/compositionLevel element. The value should be "0" for uncompressed files or "1" for files with one level of compression (e.g., zip or tar file). requirement:
@ID="techMD7"
A conforming METS record must contain an /object/objectCharacteristics/fixity/messageDigestAlgorithm and /messageDigest element. requirement:
@ID="techMD8"
A conforming METS record must contain an /object/objectCharacteristics/size element. requirement:
@ID="techMD9"
A conforming METS record must contain an /object/objectCharacteristics/format/formatName element. requirement:
@ID="techMD10"
A conforming METS record must contain an /object/creatingApplication/dateCreatedByApplication element. requirement:
@ID="techMD11"
A conforming METS record should, but is not required to, include the following PREMIS elements: <pre:storageMedium> (/object/storage/storageMedium), <pre:formatVersion> (/object/objectCharacteristics/formatVersion), <pre:creatingApplicationName> (/object/creatingApplication/creatingApplicationName), and <pre:originalName> (/object/originalName) requirement:
@ID="techMD12"
Source or provenance metadata pertaining to image content files expressed as MIX, 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 Restrictions 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 an action, a conforming METS record must include a rightsStatement/rightsGranted/restriction element with a value from the UC Libraries Rights Resrictions 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. 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. fileSec:
requirement:
@ID="fileSec1"
The <fileSec> for a compliant METS record must contain one, or more, <fileGrp> elements. requirement:
@ID="fileSec3"
Each <fileGrp> must include a file USE attribute representing the intended use of the referenced file. requirement:
@ID="fileSec4"
Each <file> element must reference pertinent <techMD> sections by including the relevant ID values in the ADMID attribute. The AMDID 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="structMap2"
The <structMap> element must contain a TYPE attribute encoded with the value "physical." requirement:
@ID="structMap3"
The <div> element must include a LABEL attribute value, which is derived from and identical to the value encoded in the /mods/titleInfo/title element. requirement:
@ID="structMap4"
The <div> element must reference pertinent <dmdSec> sections by including the relevant ID values in the DMDID attribute. requirement:
@ID="structMap5"
The <div> element must reference pertinent <rightsMD> sections by including the relevant ID values in the AMDID attribute. requirement:
@ID="structMap6"
The <div> element must contain one or more <fptr> elements, each of which references an individual <file> element representing a version of the file. requirement:
@ID="structMap7"
The <fptr> element must use the FILEID attribute to point directly to a <file> element. requirement:
@ID="structMap8"
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. 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. |
 Top
of Page |
||||
| |
|
|||
|
|
|||
|
||||