mets/fileSec/fileGrp/@USE

mets/fileSec/fileGrp/file/@USE

These are the values supported for <file> and <fileGrp> USE attributes for digital objects conforming to this profile.

mets/amdSec/rightsMD/mdWrap/xmlData/rightsStatement/rightsBasis

These are the values supported for the PREMIS rightsBasis element for digital objects conforming to this profile.

mets/amdSec/rightsMD/mdWrap/xmlData/rightsStatement/copyrightStatus

These are the values supported for the PREMIS copyrightStatus element for digital objects conforming to this profile.

mets/amdSec/rightsMD/mdWrap/xmlData/rightsStatement/rightsGranted/restriction

mets/amdSec/rightsMD/mdWrap/xmlData/rightsStatement/rightsGranted/action

These are the values supported for the PREMIS act and restriction elements for digital objects conforming to this profile.

The root <mets> element must include a LABEL attribute value.

The root <mets> element must include a PROFILE attribute value.

The root <mets> element must include an OBJID attribute value that uniquely identifies the object in the UC San Diego digital repository.

A METS record conforming to this profile must contain a <metsHdr> element.

The <metsHdr> element must contain the CREATEDATE attribute.

The <metsHdr> element must contain a <agent> with the ROLE attribute value "CREATOR" and a TYPE attribute value "ORGANIZATION".

The <metsHdr> must include a child <agent> element to identify the department and or staff person responsible for creating the METS record.

The <metsHdr> element should, but is not required to, contain a LASTMODDATE attribute reflecting the date of the last modification to the METS record.

A METS record conforming to this profile must contain one or more <dmdSec> containing a <dmdWrap> with <xmlData>. The required dmdSec/dmdWrap/xmlData must contain elements from the Metadata Object Description Schema (MODS). Additional <dmdSec> elements are permitted. For each additional metadata schema a separate <dmdSec> should 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.

A conforming METS record must contain a /mods/titleInfo/title element for the title of the dissertation or thesis.

A conforming METS record must contain a /mods/name/namePart element indicating the author of the dissertation or thesis.

A conforming METS record must contain a /mods/typeOfResource element for which the value must be "text " or "mixed material". If only the primary pdf file is present, the value should be "text". When this primary file is accompanied by associated files, the value should be "mixed material".

A conforming METS record must contain a /mods/originInfo/dateCreated element.

A conforming METS record must contain a /mods/note element with the value constructed as follows: "[Thesis] ([degree])--University of California, San Diego, [date]."

A conforming METS record must contain a /mods/subject/genre with the attribute authority="local". The value for the element should be as follows: "Dissertations, Academic. UCSD. [Subject]".

A conforming METS record should contain when applicable a /mods/identifier element with the attribute type="proquest". The value for the element should be the ProQuest number assigned to the dissertation or thesis.

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/)

A conforming METS record should, but is not required to, contain the following descriptive metadata elements when they are applicable: description (/mods/abstract/), subject (/mods/subject/...), language of the object (/mods/language).

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 two rightsMD/mdWrap/xmlData sections.

The required <techMD> must contain elements from the PREMIS schema.

The required techMD/mdWrap/xmlData must describe the primary (pdf) digital file.

The required techMD/mdWrap/xmlData must contain a /object/objectIdentifierType and /objectIdentifierValue element

The required techMD/mdWrap/xmlData must contain a /object/preservationLevel element. The value should be either "Full" or "Bit-level".

The required techMD/mdWrap/xmlData must contain a /object/objectCategory element. The value should be "File".

The required techMD/mdWrap/xmlData must contain a /object/objectCharacteristics/compositionLevel element with the value set to "0".

The required techMD/mdWrap/xmlData must contain a /object/objectCharacteristics/fixity/messageDigestAlgorithm and /messageDigest element.

The required techMD/mdWrap/xmlData must contain a /object/objectCharacteristics/size element.

The required techMD/mdWrap/xmlData must contain a /object/objectCharacteristics/format/formatName element with the value set to "PDF".

The required techMD/mdWrap/xmlData must contain a /object/creatingApplication/dateCreatedByApplication element.

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)

If there are appended file(s) considered to be preservation master(s), it is recommended, but not required, that these be described in additional <techMD> sections containing elements from the PREMIS schema.

Additional <techMD> sections may be used, but are not required, to supplement PREMIS technical descriptions for preservation master files. If the supplemental description is for images, it should utilize elements from the MIX schema. If description is for text, it should utilize elements from the TextMD schema. If the description is for audio or video files, 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).

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.

The required rightsMD/mdWrap/xmlData must contain elements from the PREMIS Rights schema.

A conforming METS record must include a rightsStatement/rightsBasis element with the value expressed as "Copyright."

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, or expressed as “In the public domain” if copyright for the work has expired or been gifted to the public domain.

A conforming METS record must include a rightsStatement/copyrightInformation/copyrightJurisdiction element containing the value “us” for the United States for UC San Diego dissertations and thesis. If the dissertation or thesis was not authored in a US institution, then the appropriate code for the jurisdictional context of the copyright should be taken from ISO 3166.

A conforming METS record must have one rightsStatement/copyrightInformation/copyrightNote element for identifying the rights holder(s) of a thesis or dissertation. The value encoded is to be the name of the copyright holder(s); usually the author(s) of the thesis or dissertation. The note should be in the form of: “Rights Holder(s): [rights holder’s name in normal order]".

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].” The note text is: “Use: This work is available from the UC San Diego Libraries. This digital copy of the work is intended to support research, teaching, and private study. ”

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].” For a work under US copyright, a typical dissertation or thesis, the note text shall be: “This work is protected by the U.S. Copyright Law (Title 17, U.S.C.). Use of this work beyond that allowed by “fair use” requires written permission of the copyright holder(s). Responsibility for obtaining permissions and any use and distribution of this work rests exclusively with the user and not the UC San Diego Libraries. Inquiries can be made to the UC San Diego Libraries department having custody of the work [include email alias for department].” If the work is in the public domain, the note text shall be “This work may be used without prior permission.”

A second required rightsMD/mdWrap/xmlData must contain elements from the PREMIS Rights schema.

A conforming METS record must include a rightsStatement/rightsBasis element with the value expressed as "License."

A conforming METS record must include a rightsStatement/rightsGranted/act element with the value expressed as "Display."

In cases when public display is restricted (postponed) by the licensor, a conforming METS record must include a rightsStatement/rightsGranted/restriction element with the value expressed as "Display".

In cases when public display is restricted by the licensor, a conforming METS record must include a rightsStatement/rightsGranted/termOfGrant/startDate element with the value indicating the time at which the restriction begins (typically a date stipulated by the Office of Graduate Studies). Date must be expressed in form YYYY-MM-DD.

In cases when public display is restricted by the licensor, 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.

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),

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.

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.

The <fileSec> for a compliant UC San Diego ETD METS record must contain one <fileGrp> for the primary PDF.

The <fileGrp> must reference a file with the MIMETYPE of application/pdf.

The <fileSec> for a compliant UC San Diego ETD METS record may contain one or more additional <fileGrp> for one or more files associated with the primary PDF file. For example, the <fileSec> of an UC San Diego ETD METS record consisting of a PDF plus one sound recording would contain one <fileGrp> representing the primary PDF and another <fileGrp> representing the sound recording. No sequential relationship (using the SEQ attribute) for these files need be expressed.

The additional <fileGrp> may only reference files with MIMETYPE of TIFF, MP3, MPEG2, WAV, AIFF, EXE, MOV or AVI.

Each <fileGrp> must include a file USE attribute representing the intended use of the referenced file(s).

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>.

A conforming METS record must contain one <structMap> element with the value encoded as "physical."

A conforming METS record may contain an additional <structMap> element with the value encoded as "logical."

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.

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 objects full structure.

All <div> elements within the top level containing <div> must have an ORDER attribute.

When applicable, <div> elements must reference pertinent <dmdSec> sections by including the relevant ID values in the DMDID attributes.

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>.

When applicable, <div> elements must reference pertinent <rightsMD> sections by including the relevant ID values in the ADMID attributes.

Each <fptr> element must reference an individual <file> element representing a version of the file.

The <fptr> element must use the FILEID attribute to point directly to a <file> element.

The <fptr> element may not contain an <area>, <par>, or <seq> element. These elements are not supported in objects conforming to this profile.

The <mptr> element is not supported in this profile.

This profile stipulates no requirements for the <structLink> element.

This profile stipulates no requirements for the <behaviorSec> element.

The <file> elements will only reference elements in the <techMD>, <sourceMD>, <digiprovMD>, and <rightsMD> sections.

The <div> element will only reference metadata in the <dmdSec> and <rightsMD> sections. That is, descriptive metadata are always and only expressed in conjunction with division of the <structMap> and not in conjunction with the content file(s), whereas rights metadata is expressed in conjunction with division of the <structMap> and / or with the content file(s).

This profile supports only PDF files and associated TIFF, WAV, AIFF, MP3, MOV, MPEG2, AVI and EXE files.

The profile does not prescribe association to any behaviors.

The 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.