 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:
UCSD Simple Object Profile abstract:
The UCSD Libraries uses the UCSD 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 single digital content file may be of any format type, e.g., audio, image, text, or video, and it may be represented in the METS instance with content equivalent file versions. For example, a digital image may be represented in the METS instance by a TIFF file, a JPEG file, and a GIF file, with each containing the same content image. date:
2006-07-07T11:53:31 related_profile:
None 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. extension_schema:
name:
METSRights context:
mets/amdSec/rightsMD/mdWrap/xmlData note:
Used for recording intellectual property rights. description_rules:
All applications of MODS in UCSD 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:
UCSD/UCB file USE attribute values maintenance_agency:
University of California, San Diego values:
value:
Application-PDF value:
Application-PS value:
Audio-Master value:
Audio-Master-Edited value:
Audio-Service value:
Audio-Streaming value:
Audio-Clip value:
Image-Master value:
Image-Master-Edited value:
Image-Service value:
Image-Service-LowRes value:
Image-Service-MedRes value:
Image-Service-HighRes value:
Image-Service-Edited value:
Image-Thumbnail value:
Text-OCR-Edited value:
Text-OCR-Unedited value:
Text-TEI-Translated value:
Text-TEI-Transcripted value:
Text-Georeference value:
Text-Data value:
Text-Data Definition value:
Text-Codebook value:
Video-Master value:
Video-Master-Edited value:
Video-Service value:
Video-Streaming value:
Video-Clip 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. structural_requirements:
metsRootElement:
requirement:
@ID="metsRoot3"
The root <mets> element must include an OBJID attribute value that uniquely identifies the METS instance in the UCSD 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 Office, Geisel Library, University of California, San Diego", and a <note> element with the value "mailto:dlo@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/name/namePart element. If the creator is unknown, the value should be "Creator unknown". requirement:
@ID="dmdSec4"
A conforming METS record must contain a /mods/typeOfResource element for which the value must be taken from the MODS typeOfResource values. requirement:
@ID="dmdSec5"
A conforming METS record must contain a /mods/originInfo/dateCreated element. If the date is not known, the value should be "Date unknown". 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 UCSD Libraries' data provider that is primarily responsible for making the resource available digitally, e.g. Art and Architecture Library. The URL for the provider's main page should be included with their name. requirement:
@ID="dmdSec8"
A conforming METS record should, but is not required to, contain the following descriptive metadata elements when they are applicable: genre (/mods/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 one rightsMD/mdWrap/xmlData section. 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="rightsMD1"
The required <rightsMD> must contain elements from the METSRights schema. requirement:
@ID="rightsMD2"
A conforming METS record must include a <rts:RightsDeclarationMD> element with the RIGHTSCATEGORY attribute encoded as either "COPYRIGHTED", "PUBLIC DOMAIN" or "OTHER". requirement:
@ID="rightsMD3"
A conforming METS record must include a <rts:RightsDeclaration> from the METSRights Schema with the value expressed as either "The work is copyrighted." for works for which the copyright holder(s) can be identified, "The work is copyright by the UC Regents" for materials under copyright to the University of California Regents, "The work is in the public domain" for works known to have entered the public domain, or "Copyright status of the work has not been determined by the UCSD Libraries" for works for which the copyright holder(s) cannot be identified and the work cannot be said to have entered the public domain. requirement:
@ID="rightsMD4"
If necessary, a justification of the rights declaration can be included in <rts:RightsDeclaration> element to explain the copyright assertion. This is not necessary if the basis for the assertion is evident in the descriptive metadata for the object. In cases where this is not evident, a justification statement may be very useful. Examples of such cases include 1) when the copyright holder is different than the creator and 2) when an item has been gifted to the public domain prior to the copyright expiring. requirement:
@ID="rightsMD5"
A conforming METS record must include a <rts:constraintDescription> containing an indication of how the digital asset can be used. See the UCSD Intellectual Rights Metadata Strategy for boilerplate text. requirement:
@ID="rightsMD6"
A conforming METS record may, but is not required to, include a <rts:RightsHolder> from the METSRights Schema for those works for which the copyright holder(s) can be identified. Data can include the name of the copyright holder(s), their contact information and any notes relevant to the copyright holder. 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 |
||||
| |
|
|||
|
|
|||
|
||||