Digital Content Creation

 


 

Digital Content Creation

415 Library, MC-522
1408 W. Gregory
Urbana, IL 61801

(217) 244-2062

Email: digicc [at] library.illinois.edu

CONTACT US

Scholarly commons

Illinois Harvest logo

 

 

Visit us on Flickr

Hathi Trust Digital Library


Pixels RSS Feed

8.0 Best Practices for Descriptive Metadata

Download PDF for Chapter 8

Introduction:

A wide variety of descriptive metadata schemas currently exist, but as of yet no single metadata schema has accepted as the 'best metadata standard' for every project. In any case, deciding which metadata schema to use should be determined before materials are digitized. This document was created to provide project coordinators with a set of guidelines "for creating rich and sharable metadata, which can be useful to metadata aggregators and end users".[1]

Table of Contents

8.1 How to Select the Best Metadata Standard

8.2 Metadata Recommendations

8.2.1 Minimum Requirements

8.2.2 Collection Level Records

8.3 Best Practices for Metadata

8.3.1 Title

8.3.2 Name

8.3.3 Type

8.3.4 Publisher

8.3.5 Language

8.3.6 Format

8.3.7 Abstract

8.3.8 Table of Contents

8.3.9 Audience

8.3.10 Description

8.3.11 Subject

8.3.12 Related Item

8.3.13 Identifier

8.3.14 Source

8.3.15 Rights

8.3.16 Collection Title

8.4 Other Metadata Standards

8.4.1 EAD

8.4.2 VRA

8.4.3 CDWA

 

 

 

_________________________________________________________________________________________________

8.1 How to Select the Best Metadata Standard

 

Descriptive metadata is a resource for discovery and identification, used for the indexing, discovery, and identification of the digital resources, e.g., title, author, and keyword. The decision of which metadata standard to adapt, and what levels of description to apply must be determined within the context of the digital collection, collection users, and systems in which digital collection is stored and accessed. The NISO <http://www.niso.org/framework/Framwork2.html> recommends the following things to consider when selecting the metadata standard:

Purpose of the digital collection

User needs & intended usage

Metadata standard selection and usage

What system will be  used to store and access the digital collection

The Metadata Working Group in UIUC Library requires metadata for all digital resources to enable:

8.2 Metadata Recommendations

 

The Metadata Working Group in UIUC Library recommends that digitization project coordinators use Qualified Dublin Core as a metadata standard since our digital content management system supports Qualified Dublin Core. However, this document provides a mapping to both MARC and MODS for each element, so we could convert the metadata to richer standards in the future. (If there are MARC format records for the items, then convert the records to Qualified Dublin Core instead of creating new records. Please add the reference identifier for the original records in the metadata.  In addition we would like to address that the degree of the granularity of metadata should be determined by project coordinators based on the materials being described and users.

The elements described below are recommended requirements. We encourage project coordinators to use these minimum requirements as well as other elements as needed.

 

8.2.1 Minimum Requirements

 

For sharable metadata creation, we recommend using the following elements as a minimum required element set.  We list the element set for both Dublin Core and MODS.

See "Dublin Core metadata element set mapping to MODS version 3 <http://www.loc.gov/standards/mods/dcsimple-mods.html> updated in November 22, 2006. Every element can be repeated when it is needed.

Required Elements:
LabelQualified Dublin CoreMODSNoteControlled Vocabulary
Title

<dc:title>

<titleInfo>

   <title>

The actual title of the resource, or a brief descriptive phrase.

nR

Subject (if applicable)

<dc:subject>

 

<subject>

       <topic>

       <temporal>

       <geographical>

 

 

Topic of the resource. Use the controlled vocabulary which works best for the collection.

R

Type

 

<dc:type>

 

<typeOfResource>

        <genre>

 

 

 

 

The type of the original object being described. If possible, add more granular type information in another <type> element.

 

R

Publisher

 

<dc:publisher>

 

<originInfo>

      <publisher>

       <location>

 

The institution that makes the resource available on the web.

 

 

R

(For UIUC Library names)

Format*

(*when using <dc:format>, please describe digital format, instead of original resource)

<dc:format>

<dcterms:extent>

 

 

 

 

<dc:format>

<dcterms :medium>

<physicalDescription>

            <internetMediaType>

<physicalDescription>

            <extent>

<physicalDescription>

            <form>

 

The extent of the original item being described. Can be in number of pages or linear feet, dimension, etc.

 

The physical manifestation of the original object represented by a controlled vocabulary term.

 

 

 

 

R

Identifier

 

<dc:identifier>

<dcterms:URI>

 

<identifier>

<uri>

 

A character string or record number clearly and uniquely identifies a digital objects or resource. The element may be the accession number, record number, ISBN number, or the URI.

 

R

Language

(If applicable>

 

<dc:language>

 

 

<language>

The language(s) of the intellectual content of the resource. This can be the language(s) in which a text is written or the spoken language(s) of an audio or video resource.

 

 

R

Date

<dc:date>

<dcterms:created>

<dcterms:issued>

 

 

<originInfo><dateCreated>

<originInfo><dateIssued>

<originInfo><dateCaptured>

<originInfo><dateOther>

 

The date of creation of the original item, or other date related information, e.g., issued, or captured.

Use date description standard such as ISO 8601.

 

R

Rights

 

<dc:rights>

<dcterms:accessCondition>

 

<accessCondition>

 

A right management or usage statement, a URL that links to rights management statement, or a URL that links to a service providing information on rights management of the resource.

 

 

nR

 

 

Optional elements (When information is available) 

 

LabelQualified Dublin CoreMODSNoteControlled Vocabulary
Name

 

<dc:creator>

<dc:contributor>

 

<name><namePart>

 

The person(s), organization(s) or corporate bodies primarily responsible for the creation of the object, collection, or item being described.

 

 

R

Description

 

<dc:description>

 

 

<note>

<tableOfContent>

 

A textual description of the content of the image, such as abstract, tables of content or free-text account of the object.

 

 

 

nR

Collection Title

 

<dc:relation>

<dcterms:IsPartOf>

 

<relatedItem>+

<titleInfo><title> or

<location><url>

 

 

When the item is a part of series, serials, a collection, or has different formats. Please add a collection record as a URL if it is available.

 

 

nR

 

 

8.2.2 Collection  Level Records

 

The Metadata Working Group recommends that collection-level records be created for all collections created through a digitization project.  Also at least three elements of collection records should be included in each item record - collection title and URL of the collection, and a repository name - to create sharable metadata. The collection level record enables users and metadata providers use each digital resource in same context regardless of metadata providers. Please find the following sites for the collection level records metadata elements and examples. 

 

8.3 Metadata Recommendations

 

This document was created based on DCMI Terms <http://dublincore.org/documents/dcmi-terms/>, MODS User Guidelines Version 3 <http://www.loc.gov/standards/mods/v3/mods-userguide.html>, Digital Library Federation / Aquifer Implementation Guidelines for Sharable MODS Records <http://www.diglib.org/aquifer/dlfmodsimplementationguidelines_finalnov2006.pdf>, Resource Description and Access <http://www.rdaonline.org/>. Please use this document as Guidelines only. Depends on the characteristics of each project, users, and systems, we encourage project coordinators develop and use their own data, content, and encoding standards and create metadata in consistent way.

(All the examples are drawn from MODS User Guidelines Version 3, Detailed Description of MODS Elements <http://www.loc.gov/standards/mods/v3/mods-userguide-elements.html>.

 

8.3.1 Title: <titleInfo> Required (# 2XX, #130, #730, #740 fields in MARC)

Dublin Core:

<dc:title>

<dcterms:titleAlternative>

MODS Mapping-Subelements:

<title>

<subTitle>

<partNumber>

<partName>

<partSort>

MODS-Attributes:

<titleInfo>

type - abbreviated

type - translated

type - alternative

type - uniform

type - authority

type - displayLable

 

When adding <title> information, please consider the following recommendations:

 

For 'A Alma Mater'-

<dc:title>A Alma Mater</dc:title>

 

Examples:

Title: The winter mind: William Bonk and American letters

 

<dc:title>The winter mind: William Bonk and American letters</dc:title>

 <titleInfo>  

<nonSort>The</nonSort>  

 <title>winter mind</title>  

 <subTitle>William Bonk and American letters</subTitle>

</titleInfo>

 

 

<titleInfo type="translated" lang="eng">  

<title>Land surveying and agriculture equipment</title>

</titleInfo>

 

<titleInfo type="uniform" authority="naf" xlink:href="http://www.loc.gov/sru-lccn/?query=n 93028706">  

<title>Missale Carnotense</title>

</titleInfo>

8.3.2 Name: <name> Required (#1xx, #7xx fields in MARC) - When the information is available

Dublin Core:

<dc:creator>

<dc:contributor>

Use <dc:creator>, if you have source data that clearly identifies the name as creator. If there are more than one creators, repeat the elements as needed.

MODS Mapping-Subelements:

<namePart>

<displayForm>

<affiliation>

<role>

<roleTerm>

<description>

<dc:contributor>

Use <dc:creator>, if you have source data that clearly identifies the name as creator. If there are more than one creators, repeat the elements as needed.

MODS - Attributes:

<name>

type - personal

           corporate

           conference

authority

 

<namePart>

type - date

           family

           given

            termsOfAddress

<role>

type - code

           text

 

<name> element is for the name(s) of individuals, organizations, or events that bear some important relationship to the content can be put into this element. Use the name as it was presented in the resource.  To ensure the best search result, using the controlled vocabulary is recommended. The controlled vocabulary can be created locally depending on characteristics of each collection.

 

Examples:

Name: Alteman, Eric

<dc:creator>Alterman, Eric</dc:creator>

 

<name type="personal">  

<namePart type="family">Alterman</namePart>

<namePart type="given"> Eric</namePart>

<displayForm>Eric Alterman</displayForm>  

<role>    

<roleTerm type="text">creator</roleTerm>    

<roleTerm type="code">cre</roleTerm>  

</role>

</name>

 

<name type="personal" authority="naf">  

<namePart>Woolf, Virginia</namePart>  

                <namePart type="date">1882-1941</namePart>

 </name>

 

<name type="corporate">  

<namePart>United States</namePart>  

<namePart>Court of Appeals (2nd Circuit)</namePart>

 </name>

 

<name type="conference">  

<namePart>Paris Peace Conference (1919-1920)</namePart>

</name>

 

8.3.3 Type: <typeOfResource> Required (MARC Leader 06/07)

Dublin Core:

<dc:type>

MODS Mapping-Sub elements:

No Sub elements

MODS-Attributes:

collection

manuscript

*when Attributes are associated with a specific value used in <typeOfResource>, use the value as a first <typeOfResource>.

<type> contains a term that specifies the characteristics and general type of content of the resource. A controlled list of textual values is used, such as Dublin Core Metadata Initiative Type Vocabulary <http://dublincore.org/documents/dcmi-type-vocabulary/>. Please add terms that provide more granular information than the broad terms in DCMI type controlled vocabulary. You could also create a list of controlled vocabulary for your own collection. The following values may be used with <typeOfResource>:

Examples:

Type: Cartographic

<dc:type>cartographic</dc:type>

<titleInfo>  

<nonSort>The </nonSort>  

<title>new naval and military map of the United States</title> </titleInfo> <typeOfResource>cartographic</typeOfResource>

<genre>map</genre>

 

                *Other examples

<titleInfo>  

<title>Glove</title> </titleInfo>

<physicalDescription>  

<form authority="gmd">[sound recording]</form> </physicalDescription> 

<typeOfResource>sound recording-musical</typeOfResource>

8.3.4 Publisher: <originInfo> Required

Dublin Core:

<dc:publisher>

Mods - Mapping Sub elements:

<place>

<publisher>

Mods - Attributes

<originInfo>

type

authority

 

<publisher> is a place holder for the original publisher information.

 

Examples:

Publisher: Library of Congress, Cataloging Distribution Service, in collaboration with Follett Software Company

<originInfo>  

<place>    

<placeTermtype="code"authority="marccountry">dcu</placeTerm>    

 <placeTerm type="text">Washington,DC</placeTerm>  

</place>  

<publisher>Library of Congress, Cataloging Distribution Service, in collaboration with Follett Software Company</publisher>  

 <dateIssued>2003</dateIssued>  

<edition>7th ed.</edition>  

<issuance>monographic</issuance>

 </originInfo>

Other Examples:

<originInfo>  

   <place>    

      <placeTermtype="code"authority="marccountry">cau</placeTerm>    

      <placeTerm type="text">Menlo Park, CA</placeTerm>  

   </place>  

   <publisher>Center for Computer Assisted Research in the Humanities</publisher>  

   <dateIssued>1988</dateIssued>  

   <dateIssued encoding="marc" point="start">1985</dateIssued>  

   <dateIssued encoding="marc" point="end">1988</dateIssued>  

   <issuance>continuing</issuance>  

   <frequency>annual</frequency>

</originInfo>

 

8.3.5 Language: <language> Required - when the collection includes textual materials.

Dublin Core:

<dc:language>

MODS Subelements:

<languageTerm>

MODS Attributes:

<languageTerm>

type - text

           code

authority - ISO 639-2, etc

 

<language> contains the language(s) of the content of the resource. It may be expressed in textual or coded form. Use as many <language> elements as necessary to describe the languages represented in the resource. (ex. English, or eng)

 

The following are the controlled vocabulary sites for language code:

Examples:

Language: English

<dc:language>English</dc:language>

 <language>  

<languageTerm type="code" authority="rfc3066">en</languageTerm>

</language>

Other examples:

<language>  

<languageTerm type="text">Italian</languageTerm>

</language>

 

8.3.6 Format: <physicalDescription> Required

Dublin Core:

<dc:format>

<dcterms:extent>

<dcterms:medium>

Mods - Mapping Sub elements:

<form>

<reformattingQuality>

<internetMediaType>

<extent>

<digitalOrigin>

<note>

MODS-Attributes:

<form>

type

authority

<note>

type

displayLabel

 

Information in <format> is about the digital resource being described. Value is generally taken from a controlled list, especially from the Internet Media types <www.iana.org/assignments/media-types/index.html>.

 

The following are the examples of the controlled vocabulary sites:

Examples:

format: text/html

extent: 26 cm

<dc:format>text/html</dc:format>

<dcterms:extent> 26 cm. </dcterms>

 

<physicalDescription>  

   <form authority="marcform">electronic</form>  

   <digitalOrigin>born digital</digitalOrigin>  

   <reformattingQuality>access</reformattingQuality>  

   <internetMediaType>text/html</internetMediaType>

</physicalDescription>

Other Examples:

<physicalDescription>

   <form authority="marcform"> print </form> 

   <extent>26 cm</extent>  

   <reformattingQuality>replacement</reformattingQuality>

</physicalDescription>


8.3.7 Abstract: <abstract>

Dublin Core:

<dcterms:abstract>

Mods - Mapping Sub elements:

No sub elements

MODS-Attributes:

Type

Display Label

<abstract> is a summary of the content of the resource, roughly equivalent to MARC 21 field 520.  Information in <abstract> can be a link.

Example:

Abstract: Describes the results of an ongoing evaluation of State activity relating to improvement of criminal records. Activities reviewed include upgrading of accuracy and completeness of records, automation, implementation of positive identification procedures and procedures for responding to firearm background check inquiries. The report describes the nature of activities initiated, time until completion, and impact on availability of records. Characteristics of individual states are represented in some areas. The document was prepared by Queues Enforth Development under BJS award 95-RU-RX-K002. 2/00 NCJ 179768

<dc:description> Describes the results of an ongoing evaluation of State activity relating to improvement of criminal records. Activities reviewed include upgrading of accuracy and completeness of records, automation, implementation of positive identification procedures and procedures for responding to firearm background check inquiries. The report describes the nature of activities initiated, time until completion, and impact on availability of records. Characteristics of individual states are represented in some areas. The document was prepared by Queues Enforth Development under BJS award 95-RU-RX-K002. 2/00 NCJ 179768</dc:description>

 

<abstract xlink:href= "http://www.ojp.usdoj.gov/bjs/abstract/cchrie98.htm"/>

<abstract>Describes the results of an ongoing evaluation of State activity relating to improvement of criminal records. Activities reviewed include upgrading of accuracy and completeness of records, automation, implementation of positive identification procedures and procedures for responding to firearm background check inquiries. The report describes the nature of activities initiated, time until completion, and impact on availability of records. Characteristics of individual states are represented in some areas. The document was prepared by Queues Enforth Development under BJS award 95-RU-RX-K002. 2/00 NCJ 179768</abstract>

 

8.3.8 Table of Contents: <tableOfContents> (#505 field in MARC)

Dublin Core:

<dcterms:tableOfContent>

Mods - Mapping Sub elements:

No sub elements

MODS-Attributes:

type

displayLabel

 

<tableOfContents> contains contents notes for a resource, equivalent to MARC 21 field 505. Information in <tableOfContent> can be in a link. Please be careful when use the punctuation in <tableOfContent>. See <http://www.oclc.org/bibformats/en/5xx/505.shtm>.

Information in <tableOfContent> can be a link.

Example:

Table of Contents: http://www.loc.gov/catdir/toc/99176484.html

<dcterms:tableOfContent>http://www.loc.gov/catdir/toc/99176484.html</dcterms:tableOfContents>

<tableOfContents xlink:href= "http://www.loc.gov/catdir/toc/99176484.html"/> </tableOfContents>

 

Other examples:

<tableOfContents type="partial contents">Baptisms, 1816-1872 --Church members, 1816-1831 --History of the Second Presbyterian Church of West Durham</tableOfContents>

8.3.9 Audience: <targetAudience>

Dublin Core:

<dcterms:Audience>

Mods - Mapping Sub elements:

No sub elements

MODS-Attributes:

authority

 

<audience> describes the intellectual level of the audience for which the resource is intended. Either a controlled list of values or free text may be used.

MARC Source Code for Target Audience <http://www.loc.gov/marc/sourcecode/target/targetsource.html> can be used as a controlled vocabulary.

Examples:

Audience: Adolescent

 

<dcterms:audience>adolescent</dcterms:audience>

<targetAudience authority="marctarget">adolescent</targetAudience>

<targetAudience authority="marctarget">adult</targetAudience>

 

8.3.10 Description <note>  (#5xx fields in MARC)

Dublin Core:

<dcterms:Description>

Mods - Mapping Sub elements:

No sub elements

MODS-Attributes:

Type

displayLabel

 

<description> contains general textual information relating to a resource. <description> is roughly equivalent to MARC 21 fields 5XX.  See MODS <note> Types <http://www.loc.gov/standards/mods/mods-notes.html> for reference.

 

Examples:

Description: Performers: Anne Baxter (Louise), Maria Perschy (Angela), Gustavo Rojo (Bill), Reginald Gilliam (Mr. Johnson), [Catherine Elliot?] (Aunt Sallie), Ben Tatar (waiter)

<dc:description>Performers: Anne Baxter (Louise), Maria Perschy (Angela), Gustavo Rojo (Bill), Reginald Gilliam (Mr. Johnson), [Catherine Elliot?] (Aunt Sallie), Ben Tatar (waiter)</dc:description>

 

<note type="performers"> Anne Baxter (Louise), Maria Perschy (Angela), Gustavo Rojo (Bill), Reginald Gilliam (Mr. Johnson), [Catherine Elliot?] (Aunt Sallie), Ben Tatar (waiter) </note>

Other Examples:

<note type="statement of responsibility">written by Burt Kimmelman</note>

<note>Based on a play which originally appeared in France as "Un peu plus tard, un peu plus tôt"</note>


8.3.11 Subject: <subject> Required (#6xx fields in MARC)

Dublin Core:

<dc:subject>

<dc:coverage>

<dcterms:temporal>

<dcterms:spatial>

Mods - Mapping Sub elements:

<topic>

<geographic>

<temporal>

<titleInfo>

<name>

<geographicCode>

<hierarchicalGeographic>

<cartographics>

<occupation>

MODS-Attributes:

authority

<temporal>

encoding

 

<subject> is an element that contains topical, geographic coverage, and temporal coverage.  The controlled vocabulary should be chosen depending on main user groups and resources of the digitization projects.

 

The following are commonly used controlled vocabulary sites:
For Topical Subject Heading:
For Geographical terms:

 

Examples:

Subject: Real Property

Spatial Coverage:  Mississippi, Tippah County

 

<dc:subject> Real property </dc:subject>

<dcterms:spatial>Mississippi, Tippah County</dcterms:spatial>

 <subject authority="lcsh">  

<topic>Real property--Mississippi--Tippah County--Maps</topic>

</subject>

<subject authority="lcsh">  

<topic>Real property</topic>  

<geographic>Mississippi</geographic>  

 <geographic>Tippah County</geographic>  

<genre>Maps</genre>

</subject>

 

<subject authority="lcsh">  

<name>  

<namePart>Garcia Lorca, Federico</namePart>  

<namePart type="date">1898-1936</namePart>  

 </name>

 </subject>

 

<subject authority="lcsh">  

<topic>Real property</topic>  

<geographic>Mississippi</geographic>  

<geographic>Tippah County</geographic>  

<genre>Maps</genre>

</subject>

 

<subject authority="lctgm">  

<topic>Educational buildings</topic>  

<geographic>Washington (D.C.)</geographic>  

<temporal>1890-1910</temporal>

</subject

8.3.12 Related Item: <relatedItem> When an item is belonged to a series, serials, or have different formats. (#4xx, #7xx, #8xx fields in MARC)

Dublin Core:

<dc:relation>

<dcterms:hasPart>

<dcterms:hasFormat>

<dcterms:isVersionOf>

<dcterms:isFormatOf>

 

Mods - Mapping Sub elements:

All MODS elements can appear as subelements of <relatedItem>

MODS-Attributes:

type - preceding

           succeeding

           original

           host

           constituent

           series

           otherVersion

           otherFormat

           isReferencedBy

xlink:href

displayLabel

ID

 

<relatedItem> gives information that identifies a related resource. When the resource is a part of a series, or a different version/format of the resources it is required to use <relatedItem>.

Examples:

Related Item (title): Portrait of Charlie Parker and Tommy Potter, Three Deuces, New York, N.Y., ca. Oct. 1947

Related Item (name): Gottlieb, William P. (1917-)

Related Item (identifier): LC-GLB23-0542

 

<titleInfo>   <title>William P. Gottlieb Collection</title> </titleInfo>

<relatedItem type="constituent">  

     <titleInfo>

          <title>Portrait of Charlie Parker and Tommy Potter, Three Deuces, New York, N.Y., ca. Oct. 1947</title> 

     </titleInfo>  

     <name>    

          <namePart>Gottlieb, William P.</namePart>    

          <namePart type="date">1917-</namePart>  

     </name>  

     <identifier type="local">LC-GLB23-0542</identifier>

</relatedItem>

In Dublin Core:

<dc:relation> Portrait of Charlie Parker and Tommy Potter, Three Deuces, New York, N.Y., ca. Oct. 1947; Gottlieb, William P. (1917-); LC-GLB23-0542</dc:relation>

or

<dc:relation> Portrait of Charlie Parker and Tommy Potter, Three Deuces, New York, N.Y., ca. Oct. 1947</dc:relation>

<dc:relation> Gottlieb, William P. (1917-)</dc:relation>

<dc:relation>LC-GLB23-0542</dc:relation>

Other examples:

<relatedItem type="host">  

     <titleInfo>    

          <title>Post-Fordism</title>    

          <subTitle>A Reader</subTitle>  

     </titleInfo>  

     <name type="personal">    

          <namePart type="given">Ash</namePart>    

          <namePart type="family">Amin</namePart>    

          <role>        

               <roleTerm type="text">editor</roleTerm>    

          </role>  

     </name>  

     <originInfo>    

          <dateIssued>1994</dateIssued>    

          <publisher>Blackwell Publishers</publisher>    

          <place>      

               <placeTerm type="text">Oxford</placeTerm>    

          </place>  

     </originInfo>  

     <part>    

          <extent unit="page">      

               <start>23</start>      

               <end>45</end>    

          </extent>  

     </part>

</relatedItem>

8.3.13 Identifier: <identifier> Required (#010, #020, #022, #024, #856 fields in MARC)

Dublin Core:

<dc:identifier>

Mods - Mapping Sub Elements:

No Sub elements

MODS-Attributes:

 

Type - doi

            isbn

            issn

            iccn

            uri 

 

displayLabel

 

<identifier> contains a unique standard number or code that distinctively identifies a resource. It is equivalent to MARC fields 010, 020, 022, 024, 856. It is repeatable, so you can put as many as identifiers as possible if that is useful for identifying a resource. However, the ideal format of value is actionable URI. (Using collection URL is not recommended for <identifier> element. This URL can represent the whole collection, not the resource you want to describe and must be included in <isPartOf>. The URL should belong to the <location> element instead of <identifier>.)

Identifier: N.M. 275 Nova Music

<dc:identifier> N.M. 275 Nova Music </dc:identifier>       

 <identifier type="music publisher">N.M. 275 Nova Music</identifier>

<identifier type="isbn" invalid="yes">0877780116</identifier>

 

8.3.14 Source: <location> Required

Dublin Core:

<dc:source>

MODS Mapping Sub Elements:

<physicalLocation>

<url>

MODS-Attributes

<physicalLocation>

displayLabel

authority

<url>

displayLabel

 

dateLastAccessed

note

usage: "primary display"

<source> Identifies the institution or repository holding the resource, or a remote location in the form of a URL where it is available.  <physicalLocation> should be used in controlled vocabulary when the each item is housed in different library. For the collection level description, you may decide whether using controlled vocabulary or not. You can also use the MARC Code List for Organizations <http://www.loc.gov/marc/organizations/>.

Examples:

Source: N.M. 275 Nova Music

<dc:source>DLC MicRR Microfilm 82/528 MicRR </dc:source>

 <location>  

     <physicalLocation authority="marcorg">DLC MicRR Microfilm 82/528 MicRR</physicalLocation>

</location>

Other Examples:

<location>  

     <physicalLocation>Library of Congress Manuscript Division</physicalLocation> </location>

<location>  

     <url displayLabel="French version">http://www.cgiar.org/ifpri/reports/0297rpt/0297-ft.htm</url>

</location>

8.3.15 Rights: <accessCondition> (#506, #540 fields in MARC)

Dublin Core:

<dcterms:accessRights>

<dc:rights>

Mods - Mapping Sub elements:

No Sub elements

MODS-Attributes:

type

displayLabel

<right> Contains information about restrictions imposed on access to a resource. If there is no specific access restriction, use <dc:rights>.

Examples:

Access Rights:Classified under national security provisions; Department of Defense; Title 50, chapter 401, U.S.C

<dcterms:accessRights> Classified under national security provisions; Department of Defense; Title 50, chapter 401, U.S.C </dcterms:accessRights>

 <accessCondition>Classified under national security provisions; Department of Defense; Title 50, chapter 401, U.S.C</accessCondition>

 Other examples:

<accessCondition type="restrictionOnAcces">Restricted: cannot be viewed until 2010; Members of donor's family</accessCondition>

<accessCondition type="useAndReproduction">Literary rights of Carrie Chapman Catt have been dedicated to the public</accessCondition>

8.3.16 IsPartOf: <recordInfo> Required

Dublin Core:

<dcterms:isPartOf>

Mods - Mapping Sub Elements:

<recordContentSource>

<recordCreationDate>

<recordChangeDate>

<recordIdentifier>

<recordOrigin>

<languageOfCataloging>

 - <languageTerm>

MODS-Attributes:

<recordContentSource>

authority

<recordCreationDate>

<recordChangeDate>

encoding

point

keyDate

qualifier

<recordIdentifier>

source

<languageTerm>

authority

<isPartOf> is used for collection information where each item belongs. The collection information can be added as URL followed by a title of the collection.

Examples:

isPartOf: German Emblem Project <http://images.library.uiuc.edu:8081/cdm4/browse.php?CISOROOT=/emblems>

<dcterms:isPartOf>German Emblem Project http://images.library.uiuc.edu:8081/cdm4/browse.php?CISOROOT=/emblems</dcterms:isPartOf>

8.4 Metadata Recommendations

 

Depending on the resources of the digital collection, you might need other metadata standards than Qualified Dublin Core - EAD (Encoded Archival Description) is used in archival community, and VRA Core (Visual Resources Association Core Categories) and ObjectID are used for describing visual resources.

 

8.4.1 EAD (Encoded Archival Description)

The Encoded Archival Description (EAD) standard is used by digital libraries to create machine-readable finding aids. Please find following links for more information.

 

8.4.2 VRA Core (Visual Resources Association Core Categories)

VRA is a metadata standard for the visual resources. Please find the following link for the detailed information. The link includes the MARC mapping <http://www.vraweb.org/vracore3.htm>.

8.4.3 CDWA (Categories for the Description of Arts)

CDWA is used for describing and accessing information about works of art, architecture, other material culture, groups and collections of works, and related images.

< http://www.getty.edu/research/conducting_research/standards/cdwa/index.html>

Generally the CDWA is used in museum community and CDWA and VRA use CCO (Cataloging Cultural Objects < http://www.vrafoundation.org/ccoweb/index.htm> as its content standards.

 

_________________________________________________________________________________

[1] Digital Library Federation (DLF) Aquifer Project. (2006).  Retrieved January 21, 2009, from http://www.dlib.org/dlib/may06/kott/05kott.html.

9.0 Best Practices for Controlled Vocabularies

Back to Table of Contents