NDLTD - Interoperability Metadata Standard for Electronic Theses and Dissertations

Interoperability Metadata Standard for Electronic Theses and Dissertations -- version .02

This version

http://www.ndltd.org/standards/metadata/draft-09-11-2000.html

Current version

http://www.ndltd.org/standards/metadata/current.html

Previous version

http://www.ndltd.org/standards/metadata/draft-07-09-2000.html

Editors

Anthony Atkins, Virginia Tech

Dr. Edward Fox, Virginia Tech

Outline

1. Introduction

2. Metadata Elements

2.1 dc.title
2.2 dc.creator
2.3 dc.publisher
2.4 dc.subject
2.5 dc.description
2.6 dc.contributor
2.7 dc.date
2.8 dc.type
2.9 dc.format
2.10 dc.identifier
2.11 dc.source
2.12 dc.language
2.13 dc.relation
2.14 dc.coverage
2.15 dc.rights

3.History

4.Contributors

1.Introduction

This document defines a standard set of metadata elements used to describe an electronic thesis or dissertation.

Institutions dealing with electronic theses and dissertations have all developed their own standards or adapted existing metadata standards. These metadata standards all attempt to describe the author, the work, and the context in which the work was produced in a way that will be useful to the researcher as well as the librarians and/or technical staff maintaining the work in its electronic form.

This document is not a replacement for the metadata schemes developed for a particular university or environment. Rather, this document should be used as a guideline to develop a faithful cross-walk between local metadata standards and a single standard used for sharing information about ETDs.

2. Metadata Elements

The following is a description of the common Dublin Core metadata elements, and which information related to an ETD belongs in each field. If a more general element (i.e. dc.creator) is described as mandatory, it should be specified fully, even if qualified elements (i.e. dc.creator.given) are also specified. If a more general element is repeatable, (i.e. dc.contributor) it should be assumed that sub-elements (i.e. dc.contributor.family) are also repeatable.

2.1 dc.title

Element Description Mandatory? Repeatable?

dc.title title of the thesis or dissertation in source language Y

dc.title.alternative translated title of the thesis or dissertation

2.2 dc.creator

Element Description Mandatory? Repeatable?

dc.creator Author(s) of the work Y

dc.creator.family Family name of the author.

dc.creator.given Given name of the author.

dc.creator.bday The author's birthday. Used to distinguish between authors with the same name.

dc.creator.orgname The department(s) university(ies) the author is associated with. This is typically the department and university granting the degree associated with the work.

dc.creator.email Email address most appropriate for contacting the author

dc.creator.street Street or equivalent portion of the author's postal address

dc.creator.locality Locality (city, town, etc.) portion of the author's postal address

dc.creator.region Region (state, province, etc.) portion of the author's postal address

dc.creator.country Country portion of the author's postal address

dc.creator.pcode Postal code (zip code, etc.) portion of the author's postal address

2.3 dc.publisher

Element Description Mandatory? Repeatable?

dc.publisher Institution or organization responsible for publishing the electronic thesis or dissertation

dc.publisher.orgname Name of the organization or institution

dc.publisher.email Email address most appropriate for contacting the organization or institution

dc.publisher.street Street or equivalent portion of the organization or institution's postal address

dc.publisher.locality Locality (city, town, etc.) portion of the organization or institution's postal address

dc.publisher.region Region (state, province, etc.) portion of the organization or institution's postal address

dc.publisher.country Country portion of the publisher's postal address

dc.publisher.pcode Postal code (zip code, etc.) portion of the organization or institution's postal address

2.4 dc.subject

Element Description Mandatory? Repeatable?

dc.subject Subject(s) or keyword(s) the work pertains to Y Y

dc.subject.classification Description of the vocabulary or scheme used to determine the subject(s)

2.5 dc.description

Element Description Mandatory? Repeatable?

dc.description Abstract of the thesis or dissertation

dc.description.notes Additional information regarding the thesis or dissertation. Example: acceptance note of the department

2.6 dc.contributor

Element Description Mandatory? Repeatable?

dc.contributor Person(s) other than the author who contributed to the creation or approval of the work. Typical use would be for advisors or committee members. Y

dc.contributor.role Role the person played in the creation or approval of the work.

dc.contributor.family Family name of the contributor.

dc.contributor.given Given name of the contributor.

dc.contributor.title Title (Dr., Dean, etc.) of the contributor.

dc.contributor.orgname Typically the department and university the contributor is associated with. May also contain the organization the contributor is associated with if the contributor is not associated with a university.

dc.contributor.email Email address most appropriately used to contact the contributor.

dc.contributor.street Street or equivalent portion of the contributor's postal address

dc.contributor.locality Locality (city, town, etc.) portion of the contributor's postal address

dc.contributor.region Region (state, province, etc.) portion of the contributor's postal address

dc.contributor.country Country portion of the contributor's postal address

dc.contributor.pcode Postal code (zip code, etc.) portion of the contributor's postal address

2.7 dc.date

Element Description Mandatory? Repeatable?

dc.date Date most commonly associated with the work. Y

dc.date.created Date the finished version of the work was created.

dc.date.valid Date the work was considered to be "valid" by the institution granting the degree associated with the work.

dc.date.available Date the work was made available to the public.

dc.date.issued Date the work was added to the local electronic repository of electronic theses and dissertations.

dc.date.modified Date the work was changed.

2.8 dc.type

Element Description Mandatory? Repeatable?

dc.type Type of document. This is used to indicate the level of education this work is associated with. Y

dc.type.degree The degree the author of this work received in relation to this work.

2.9 dc.format

Element Description Mandatory? Repeatable?

dc.format Description of the electronic format(s) in which the work is stored and/or delivered Y

2.10 dc.identifier

Element Description Mandatory? Repeatable?

dc.identifier Unique identifier used to distinguish the work from any other electronic thesis or dissertation. Y

2.11 dc.source

Element Description Mandatory? Repeatable?

dc.source Source materials or references from which the work was derived. Y

2.12 dc.language

Element Description Mandatory? Repeatable?

dc.language Language(s) the full text of the work is written in. Y

2.13 dc.relation

Element Description Mandatory? Repeatable?

dc.relation Reference to a related work, including a sub-part of the work. It is important to note that in our concept, the work is treated as a whole, individual chapters or files are not handled separately. Y

dc.relation.isversionof

dc.relation.hasversion

dc.relation.isreplacedby

dc.relation.replaces

dc.relation.isrequiredby

dc.relation.requires

dc.relation.ispartof

dc.relation.haspart This field can be used to indicate the presence of separate files containing the full text, figures, or any supplemental media related to this ETD.

dc.relation.isreferencedby

dc.relation.references

dc.relation.isformatof

dc.relation.hasformat

2.14 dc.coverage

Element Description Mandatory? Repeatable?

dc.coverage Region in space or time with which the work is concerned.

2.15 dc.rights

Element Description Mandatory? Repeatable?

dc.rights Copyright or availability information for this work. Typically, this describes the conditions under which the work may be distributed, reproduced, etc., how these conditions may change over time, and whom to contact regarding the copyright of the work.

Element	Description	Mandatory?	Repeatable?
dc.title	title of the thesis or dissertation in source language	Y
dc.title.alternative	translated title of the thesis or dissertation

Element	Description	Mandatory?
dc.creator	Author(s) of the work	Y
dc.creator.family	Family name of the author.
dc.creator.given	Given name of the author.
dc.creator.bday	The author's birthday. Used to distinguish between authors with the same name.
dc.creator.orgname	The department(s) university(ies) the author is associated with. This is typically the department and university granting the degree associated with the work.
dc.creator.email	Email address most appropriate for contacting the author
dc.creator.street	Street or equivalent portion of the author's postal address
dc.creator.locality	Locality (city, town, etc.) portion of the author's postal address
dc.creator.region	Region (state, province, etc.) portion of the author's postal address
dc.creator.country	Country portion of the author's postal address
dc.creator.pcode	Postal code (zip code, etc.) portion of the author's postal address

Element	Description	Mandatory?	Repeatable?
dc.publisher	Institution or organization responsible for publishing the electronic thesis or dissertation
dc.publisher.orgname	Name of the organization or institution
dc.publisher.email	Email address most appropriate for contacting the organization or institution
dc.publisher.street	Street or equivalent portion of the organization or institution's postal address
dc.publisher.locality	Locality (city, town, etc.) portion of the organization or institution's postal address
dc.publisher.region	Region (state, province, etc.) portion of the organization or institution's postal address
dc.publisher.country	Country portion of the publisher's postal address
dc.publisher.pcode	Postal code (zip code, etc.) portion of the organization or institution's postal address

Element	Description	Mandatory?	Repeatable?
dc.subject	Subject(s) or keyword(s) the work pertains to	Y	Y
dc.subject.classification	Description of the vocabulary or scheme used to determine the subject(s)

Element	Description	Mandatory?	Repeatable?
dc.description	Abstract of the thesis or dissertation
dc.description.notes	Additional information regarding the thesis or dissertation. Example: acceptance note of the department

Element	Description	Repeatable?
dc.contributor	Person(s) other than the author who contributed to the creation or approval of the work. Typical use would be for advisors or committee members.	Y
dc.contributor.role	Role the person played in the creation or approval of the work.
dc.contributor.family	Family name of the contributor.
dc.contributor.given	Given name of the contributor.
dc.contributor.title	Title (Dr., Dean, etc.) of the contributor.
dc.contributor.orgname	Typically the department and university the contributor is associated with. May also contain the organization the contributor is associated with if the contributor is not associated with a university.
dc.contributor.email	Email address most appropriately used to contact the contributor.
dc.contributor.street	Street or equivalent portion of the contributor's postal address
dc.contributor.locality	Locality (city, town, etc.) portion of the contributor's postal address
dc.contributor.region	Region (state, province, etc.) portion of the contributor's postal address
dc.contributor.country	Country portion of the contributor's postal address
dc.contributor.pcode	Postal code (zip code, etc.) portion of the contributor's postal address

Element	Description	Mandatory?
dc.date	Date most commonly associated with the work.	Y
dc.date.created	Date the finished version of the work was created.
dc.date.valid	Date the work was considered to be "valid" by the institution granting the degree associated with the work.
dc.date.available	Date the work was made available to the public.
dc.date.issued	Date the work was added to the local electronic repository of electronic theses and dissertations.
dc.date.modified	Date the work was changed.

Element	Description	Mandatory?	Repeatable?
dc.type	Type of document. This is used to indicate the level of education this work is associated with.	Y
dc.type.degree	The degree the author of this work received in relation to this work.

Element	Description	Mandatory?	Repeatable?
dc.format	Description of the electronic format(s) in which the work is stored and/or delivered		Y

Element	Description	Mandatory?	Repeatable?
dc.identifier	Unique identifier used to distinguish the work from any other electronic thesis or dissertation.	Y

Element	Description	Mandatory?	Repeatable?
dc.source	Source materials or references from which the work was derived.		Y

Element	Description	Mandatory?	Repeatable?
dc.language	Language(s) the full text of the work is written in.		Y

Element	Description	Mandatory?	Repeatable?
dc.coverage	Region in space or time with which the work is concerned.

Element	Description	Mandatory?	Repeatable?
dc.rights	Copyright or availability information for this work. Typically, this describes the conditions under which the work may be distributed, reproduced, etc., how these conditions may change over time, and whom to contact regarding the copyright of the work.

Sample Record

Here is a sample record from the Virginia Tech ETD collection, with information for the appropriate fields as described above. For demonstration purposes, this information is encoded in a simplified XML form. The same information could be encoded in any structured format.


<dc.title>A Contemporary Turkish Coffeehouse Design Based on Historic Traditions</dc.title>

<dc.creator>Timur Oral</dc.creator>

<dc.publisher>Virginia Polytechnic Institute and State University<dc.publisher>

<dc.subject>turkish</dc.subject>
<dc.subject>coffee</dc.subject>
<dc.subject>coffeehouse</dc.subject>
<dc.subject>tradition</dc.subject>
<dc.subject>culture</dc.subject>
<dc.subject>franchising</dc.subject>
<dc.subject>shop design</dc.subject>


<dc.description>
	The custom of coffee drinking in Turkey dates back to the sixteenth century 
	coffeehouses of Istanbul, which were once important forums for community integration. 
	Even though coffee drinking today is still an important custom in Turkey, traditional 
	coffeehouses have lost their importance in urban areas and are rapidly being replaced 
	by contemporary cafes that promote European themes. With the new generation 
	placing less emphasis on traditional values and accepting a modernized lifestyle, the 
	existence of Turkish coffeehouse culture is struggling to survive. 
	
	
	
	The purpose of this thesis project was to develop a design concept for a 
	contemporary Turkish coffeehouse franchise retaining important aspects of the traditional 
	coffeehouses of the past. Historic features were identified through observations and 
	visual recordings of historic Turkish coffeehouses and interviews with older 
	patrons of traditional coffeehouses. Focus group discussions were held with graduate 
	and undergraduate Turkish students enrolled at Virginia Tech to obtain information on 
	their perceptions of traditional coffeehouses and responses to the idea of a 
	contemporary coffeehouse. 
	
	
	
	Based on the information gathered, design criteria were established for the design of 
	individual coffeehouse components with a consistent image, adaptable to various sites and 
	spaces. Coffeehouse logo, nameplate, and facade designs were proposed. Presentations for 
	the design included detailed elevations, plans, sketches, and perspective views. 
</dc.description>

<dc.contributor role="Committee Chair">Jeanette Bowker</dc.contributor>

<dc.contributor role="Committee Member">Eric Wiedegreen</dc.contributor>

<dc.contributor role="Committee Member">Muzaffer Uysal</dc.contributor>

<dc.date>April 16, 1997</dc.date>

<dc.type>Master's Thesis</dc.type>

<dc.format>application/pdf</dc.format>
<dc.format>application/quicktime</dc.format>

<dc.identifier>etd-2227102539751141</dc.identifier>
<dc.language>english</dc.language>

<dc.rights>This work can be viewed or printed without restrictions.  The author retains all other copyrights.</dc.rights>

In the example above, note that for the most part qualifiers are not used. It is possible to specify the metadata in much greater detail, but the example given above shows how simple it is to provide enough information for interoperability.

Document History

This document is based primarly on the Dublin Core Metadata Initiative and the proposed set of qualifiers put forward by the DC Date Working Group. Like the Dublin Core, the standard proposed by this document does not require that these metadata elements be implemented in any particular encoding scheme.

This document is also a distillation of the discussions which took place at the workshop "DTDs and the usage of new XML-technologies for electronic theses and dissertations" held in May of 2000 at Humboldt University in Berlin. A list of the participants is included in the contributors section. More information regarding this workshop can be found at: http://dochost.rz.hu-berlin.de/epdiss/dtd-workshop/.

This document is also based in part on a prior document entitled "NDLTD Metadata" drafted by Gail McMillan and Paul Mather.

Contributors

The following individuals and groups contributed to this document:

Dr. Edward Fox, Director, National Digital Library of Theses and Dissertations

Gail McMillan, Director Digital Library and Archives

Anthony Atkins, Technical Director, Digital Library and Archives

The following people participated in the metadata discussion led by Nuno Freire and Thorsten Bahne, which was part of the workshop "DTDs and the usage of new XML-technologies for electronic theses and dissertations" held at Humboldt University in Berlin in May of 2000:

Per Åkerlund, SLU (Swedish University of Agricultural Sciences) Libraries, SWEDEN, Per.Akerlund@bibul.slu.se

Anthony Atkins, Virginia Polytechnic Institute and State University, University Libraries, USA, anthony.atkins@vt.edu

Thorsten Bahne, Mathematics, University of Duisburg, Dissertation Online Project, GERMANY, bahne@,math.uni-duisburg.de

Viviane Bouletreau, Sentiers, Université Lumiére, Lyon 2, FRANCE vboletr@univ-lyon2.fr

Wolfgang Coy, School of Informatics, Humboldt-University Berlin, GERMANY, coy@informatik.hu-berlin.de

Peter Diepold, Humboldt-University Berlin, School of Educational Science, GERMANY, diepold@educat.hu-berlin.de

Susanne Dobratz, Humboldt-University Berlin, Computing Center, GERMANY dobratz@rz.hu-berlin.de

Havard Fosseng, University of Oslo, Center for Information technology Services, NORWAY, havard.fosseng@usit.uio.no

Nuno Freire, National Library Portugal, PORTIGAL, nuno.freire@ext.bn.pt

Martin Hess, Informatik Uni Frankfurt: GERMANY hess@tm.informatik.uni-frankfurt.de

Uwe Müller, Humboldt-University Berlin, Computing Center GERMANY u.mueller@rz.hu-berlin.de

Phil Potter, University of Iowa, Academic Technologies (part of Information Technology Services), USA phil-potter@uiowa.edu

Sebastian Rahtz, TeX User Group, UK; sebastian.rahtz@computing-services.oxford.ac.uk

Paul W. Schaffner, University of Michigan at Ann Arbor, Library, USA, pfs@umich.edu

Matthias Schulz, Humboldt-University Berlin, Computing Center, GERMANY matthias.schulz.1@rz.hu-berlin.de

Peter Schirmbacher, Humboldt-University Berlin, Computing Center GERMANY schirmbacher@rz.hu-berlin.de

Tuija Sonkkila, Helsinki University of Technology, Library, FINLAND sonkkila@cc.hut.fi

Christof Steinbeck, Mack-Planck Institute of Chemical Ecology, Jena GERMANY, steinbeck@ice.mpg.de

Kerstin Zimmermann, University of Oldenburg; Department of Physics; GERMANY; kerstin@merlin.physik.uni-oldenburg.de

Element	Description	Repeatable?
dc.relation	Reference to a related work, including a sub-part of the work. It is important to note that in our concept, the work is treated as a whole, individual chapters or files are not handled separately.	Y
dc.relation.isversionof
dc.relation.hasversion
dc.relation.isreplacedby
dc.relation.replaces
dc.relation.isrequiredby
dc.relation.requires
dc.relation.ispartof
dc.relation.haspart	This field can be used to indicate the presence of separate files containing the full text, figures, or any supplemental media related to this ETD.
dc.relation.isreferencedby
dc.relation.references
dc.relation.isformatof
dc.relation.hasformat