People's Network Service
Discovery Service Dublin Core Application Profile (PNDS DCAP)
People's Network Service
|
Title:
|
People's Network Service: Discovery Service Dublin Core Application Profile (PNDS DCAP) |
|
Creator:
|
Andy Powell
|
|
Contributor:
|
Pete Johnston
|
|
Date Issued:
|
2005-06-09
|
|
Identifier:
|
|
|
Replaces:
|
|
|
Is Replaced By:
|
Not applicable
|
|
Latest Version:
|
|
| Description of Document: | This document presents a DC Application Profile for item-level description for the People's Network Service. |
|
|
|
This draft document provides some recommendations for the use of Dublin Core metadata to describe resources being made available via the MLA People's Discovery Network Service (PNDS). Content providers to the PNDS will expose metadata about their content using this application profile and the OAI-PMH.
These recommendations are not primarily targeted at the end-users of the PNDS. Rather, they are intended to guide 'best-practice' for the providers of content to the PNDS in order that such systems can be configured to maximise the benefits of a shared approach to metadata disclosure. The intention is to facilitate more consistent results when 'cross-searching' and browsing metadata records gathered from multiple content providers. Nonetheless, we would hope that these guidelines have some impact on the cataloguing guidelines used within content provider services and on the 'help' sub-systems offered to end-users of those services.
These recommendations are intended to be applicable to a wide range of resource types.
These recommendations draw on four documents:
-- PeteJohnston - 26 Apr 2005
These guidelines are intended to create metadata that supports the following end-user discovery-related requirements. i.e. services should be able to perform the following functions/operations based on this Dublin Core Application Profile.
Services will be able to offer the following types of searches for items
Services will be able to filter/select the results of any of the searches listed above according to:
Services will be able to present items grouped for browsing according to:
Services will be able to display the following information about an item. (Some properties may not apply to all types of item.)
-- PeteJohnston - 18 May 2005
All content providers must support the following set of properties/encoding schemes for describing items:
All content providers should support the following set of properties for describing items:
Content providers may support the following set of properties for describing items:
The value strings provided for these properties must not contain any HTML (or XML) markup.
All content providers must support the qualified DC 'pnds_dc' record format. See
http://www.ukoln.ac.uk/metadata/pns/pndsdcxml/
All content providers must also support the simple DC 'oai_dc' record format (this is mandated by the OAI-PMH).
Admin metadata: in order to maintain and share consistent metadata about PNDS metadata records, content providers should conform to the PNDS admin metadata guidelines.
This section lists the properties that are required by the application profile.
For each property, PNDS-specific guidelines are provided, followed by the authoritative definitions and comments from the Dublin Core Metadata Initiative.
The URI of the resource.
For example:
Property: dc:identifier Syntax Encoding Scheme: dcterms:URI Value String: http://www.lib.cam.ac.uk/Taylor-Schechter/
pnds_dc XML Encoding:
<dc:identifier encSchemeURI="http://purl.org/dc/terms/URI">http://www.lib.cam.ac.uk/Taylor-Schechter/</dc:identifier>
oai_dc XML Encoding:
<dc:identifier>http://www.lib.cam.ac.uk/Taylor-Schechter/</dc:identifier>
DC Label: Resource Identifier
DC Name: dc:identifier
DC Definition: An unambiguous reference to the resource within a given context.
DC Comment: Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Example formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN)).
A name given to the resource.
Transcribe the title preserving the original wording, order and spelling. Capitalize proper nouns only, in accordance with AACR2. Punctuation need not reflect the usage of the original. Subtitles should be separated from the title by space-colon-space, e.g.:
Property: dc:title Value String: Hungary's revolution : forty years on
pnds_dc XML Encoding:
<dc:title>Hungary's revolution : forty years on</dc:title>
oai_dc XML Encoding:
<dc:title>Hungary's revolution : forty years on</dc:title>
DC Label: Title
DC Name: dc:title
DC Definition: A name given to the resource.
DC Comment: Typically, a Title will be a name by which the resource is formally known.
A free-text description of resource.
Property: dc:description Value String: The article provides a summary of the 2003 White Paper on identity cards with a critique from the perspective of the civil liberties organisation, Liberty.
pnds_dc XML Encoding:
<dc:description>The article provides a summary of the 2003 White Paper on identity cards with a critique from the perspective of the civil liberties organisation, Liberty.</dc:description>
oai_dc XML Encoding:
<dc:description>The article provides a summary of the 2003 White Paper on identity cards with a critique from the perspective of the civil liberties organisation, Liberty.</dc:description>
DC Label: Description
DC Name: dc:description
DC Definition: An account of the content of the resource.
DC Comment: Description may include but is not limited to: an abstract, table of contents, reference to a graphical representation of content or a free-text account of the content
The topic of the resource.
For multiple free-text keywords, repeat the property. There are no requirements regarding the capitalization of keywords.
For example
Property: dc:subject Value String: Football
Property: dc:subject Value String: Rugby
pnds_dc XML Encoding:
<dc:subject>Football</dc:subject> <dc:subject>Rugby</dc:subject>
oai_dc XML Encoding:
<dc:subject>Football</dc:subject> <dc:subject>Rugby</dc:subject>
The resource type, using a value selected from the DCMIType vocabulary. Repeat the property for multiple types.
For example:
Property: dc:type Vocabulary Encoding Scheme: dcterms:DCMIType Value String: Image
pnds_dc XML Encoding:
<dc:type encSchemeURI="http://purl.org/dc/terms/DCMIType">Image</dc:type>
oai_dc XML Encoding:
<dc:type>Image</dc:type>
DC Label: Resource Type
DC Name: dc:type
DC Definition: The nature or genre of the content of the resource.
DC Comment: Type includes terms describing general categories, functions, genres, or aggregation levels for content. Recommended best practice is to select a value from a controlled vocabulary (for example, the DCMI Type Vocabulary). To describe the physical or digital manifestation of the resource, use the FORMAT element.
The licence under which the resource is being made available. The URI of the licence must be provided.
See http://www.creativecommons.org.uk/ for details of Creative Commons licence URIs.
For example:
Property: dcterms:license Value URI: http://creativecommons.org/licenses/by/2.0/uk/
pnds_dc XML Encoding:
<dcterms:license valueURI="http://creativecommons.org/licenses/by/2.0/uk/" />
Use dc:rights (with the URI as element content) in place of dcterms:license when exposing simple oai_dc records.
oai_dc XML Encoding:
<dc:rights>http://creativecommons.org/licenses/by-sa/2.0/</dc:rights>
DC Label: License
DC Name: dcterms:license
DC Definition: A legal document giving official permission to do something with the resource.
DC Comment: Recommended best practice is to identify the license using a URI. Examples of such licenses can be found at http://creativecommons.org/licenses/.
The person or organization that owns the copyright over the resource.
Enter personal names, where possible, in the order suggested by AACR2 chapter 22 for headings of persons, i.e. the entry element should be that part of the name under which the person would normally be listed in authoritative alphabetic lists in his or her language or country of residence or activity (rule 22.4A). Separate other elements with a comma, e.g.:
Property: dcterms:rightsHolder Value String: Collinson, Patrick
Property: dcterms:rightsHolder Value String: Gould, Stephen Jay
Property: dcterms:rightsHolder Value String: Hoskins, W.G.
Property: dcterms:rightsHolder Value String: Ng, Tze Beng
pnds_dc XML Encoding:
<dcterms:rightsHolder>Collinson, Patrick</dcterms:rightsHolder> <dcterms:rightsHolder>Gould, Stephen Jay</dcterms:rightsHolder> <dcterms:rightsHolder>Hoskins, W.G.</dcterms:rightsHolder> <dcterms:rightsHolder>Ng, Tze Beng</dcterms:rightsHolder>
Enter corporate names, where possible, in the order suggested by AACR2 chapters 24 for headingds for corporate bodies. In general (rule 24.1) this means entering a corporate body under the name by which it is commonly identified, except when the rules provide for entering it under the name of a higher or related body or the name of a government, e.g.:
Property: dcterms:rightsHolder Value String: Bodleian Library
Property: dcterms:rightsHolder Value String: British Broadcasting Corporation
Property: dcterms:rightsHolder Value String: Loughborough University. Department of Computer Science
Property: dcterms:rightsHolder Value String: United Kingdom. Department for Education and Employment
pnds_dc XML Encoding:
<dcterms:rightsHolder>Bodleian Library</dcterms:rightsHolder> <dcterms:rightsHolder>British Broadcasting Corporation</dcterms:rightsHolder> <dcterms:rightsHolder>Loughborough University. Department of Computer Science</dcterms:rightsHolder> <dcterms:rightsHolder>United Kingdom. Department for Education and Employment</dcterms:rightsHolder>
The inclusion of personal and corporate name headings from authority lists constructed according to AACR2, e.g. the Library of Congress Name Authority File (LCNA), is also acceptable.
This information cannot be expressed using simple oai_dc records.
DC Label: Rights Holder
DC Name: dcterms:rightsHolder
DC Definition: A person or organization owning or managing rights over the resource.
DC Comment: Recommended best practice is to use the URI or name of the Rights Holder to indicate the entity.
This section lists the properties that are recommended by the application profile.
For each property, PNDS-specific guidelines are provided, followed by the authoritative definitions and comments from the Dublin Core Metadata Initiative.
The topic of the resource.
Where terms are taken from a standard subject classification scheme use a vocabulary encoding scheme to indicate the vocabulary being used. An identifier for the encoding scheme should be provided in the form of a URI.
URIs for some widely used subject schemes include the following:
* Dewey Decimal Classification (DDC) http://purl.org/dc/terms/DDC
* Library of Congress Subject Headings (LCSH) http://purl.org/dc/terms/LCSH
* Library of Congress Classification (LCC) http://purl.org/dc/terms/LCC
* Medical Subject Headings (MESH) http://purl.org/dc/terms/MESH
* Universal Decimal Classification (UDC) http://purl.org/dc/terms/UDC
* National Library of Medicine Classification (NLM) http://purl.org/rdn/terms/NLM
* Engineering Index Classification (Ei) http://purl.org/rdn/terms/Ei
* Mathematics Subject Classification (MSC) http://purl.org/rdn/terms/MSC
* Association for Computing Machinery Computing Classification System (ACM) http://purl.org/rdn/terms/ACM
* Higher Education Statistics Authority Subject Categories (HESA) http://purl.org/rdn/terms/HESA
* American Psychological Association PsycINFO Thesaurus(APA) http://purl.org/rdn/terms/APA
* CABI Thesaurus (CABI) http://purl.org/rdn/terms/CABI
* Royal College of Nursing Thesaurus(RCN) http://purl.org/rdn/terms/RCN
* International Bibliography of the Social Sciences (IBSS) http://purl.org/rdn/terms/IBSS
* Humanities and Social Science Electronic Thesaurus (HASSET) http://purl.org/rdn/terms/HASSET
* CareData? thesaurus for social work and social care (CareData) http://purl.org/rdn/terms/CareData
* Library & Information Research subject scheme (LIR) http://purl.org/rdn/terms/LIR
* Biz/ed Subject Scheme for business and economics( Bized) http://purl.org/rdn/terms/Bized
* Joint Academic Coding System subject classification (JACS) http://purl.org/rdn/terms/JACS
* Learndirect Subject Headings (Learndirect) http://purl.org/rdn/terms/Learndirect
Transcribe complete subject descriptor according to the relevant scheme. Use the punctuation and capitalisation used in the original scheme, for example:
Property: dc:subject Vocabulary Encoding Scheme: dcterms:LCSH Value String: World War, 1939-1945 - Germany
Property: dc:subject Vocabulary Encoding Scheme: dcterms:LCSH Value String: Germany - History - 1933-1945
Property: dc:subject Vocabulary Encoding Scheme: dcterms:LCSH Value String: Hitler, Adolf, 1889-45
Property: dc:subject Vocabulary Encoding Scheme: dcterms:DDC Value String: 940.43
pnds_dc XML Encoding:
<dc:subject encSchemeURI="http://purl.org/dc/terms/LCSH">World War, 1939-1945 - Germany</dc:subject> <dc:subject encSchemeURI="http://purl.org/dc/terms/LCSH">Germany - History - 1933-1945</dc:subject> <dc:subject encSchemeURI="http://purl.org/dc/terms/LCSH">Hitler, Adolf, 1889-45</dc:subject> <dc:subject encSchemeURI="http://purl.org/dc/terms/DDC">940.43</dc:subject>
oai_dc XML Encoding:
<dc:subject>World War, 1939-1945 - Germany</dc:subject> <dc:subject>Germany - History - 1933-1945</dc:subject> <dc:subject>Hitler, Adolf, 1889-45</dc:subject> <dc:subject>940.43</dc:subject>
Where the resource is about a person or organisation, their names should be supplied in addition to other keywords.
Enter personal names, where possible, in the order suggested by AACR2 chapter 22 for headings of persons, i.e. the entry element should be that part of the name under which the person would normally be listed in authoritative alphabetic lists in his or her language or country of residence or activity (rule 22.4A). Separate other elements with a comma, e.g.:
Property: dc:subject Vocabulary Encoding Scheme: pndsterms:Agent Value String: Thatcher, Margaret
Property: dc:subject Vocabulary Encoding Scheme: pndsterms:Agent Value String: Spears, Britney
pnds_dc XML Encoding:
<dc:subject encSchemeURI="http://purl.org/mla/pnds/terms/Agent">Thatcher, Margaret</dc:subject> <dc:subject encSchemeURI="http://purl.org/mla/pnds/terms/Agent">Spears, Britney</dc:subject>
oai_dc XML Encoding:
<dc:subject>Thatcher, Margaret</dc:subject> <dc:subject>Spears, Britney</dc:subject>
Enter corporate names, where possible, in the order suggested by AACR2 chapters 24 for headingds for corporate bodies. In general (rule 24.1) this means entering a corporate body under the name by which it is commonly identified, except when the rules provide for entering it under the name of a higher or related body or the name of a government, e.g.:
Property: dc:subject Vocabulary Encoding Scheme: pndsterms:Agent Value String: Manchester United Football Club
Property: dc:subject Vocabulary Encoding Scheme: pndsterms:Agent Value String: British Broadcasting Corporation
pnds_dc XML Encoding:
<dc:subject encSchemeURI="http://purl.org/mla/pnds/terms/Agent">Manchester United Football Club</dc:subject> <dc:subject encSchemeURI="http://purl.org/mla/pnds/terms/Agent">British Broadcasting Corporation</dc:subject>
oai_dc XML Encoding:
<dc:subject>Manchester United Football Club</dc:subject> <dc:subject>British Broadcasting Corporation</dc:subject>
The inclusion of personal and corporate name headings from authority lists constructed according to AACR2, e.g. the Library of Congress Name Authority File (LCNA), is also acceptable.
DC Label: Subject and Keywords
DC Name: dc:subject
DC Definition: The topic of the content of the resource.
DC Comment: Typically, a Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme.
The person or organisation primarily responsible for making the content of the resource.
Enter personal names, where possible, in the order suggested by AACR2 chapter 22 for headings of persons, i.e. the entry element should be that part of the name under which the person would normally be listed in authoritative alphabetic lists in his or her language or country of residence or activity (rule 22.4A). Separate other elements with a comma, e.g.:
Property: dc:creator Value String: Collinson, Patrick
Property: dc:creator Value String: Gould, Stephen Jay
Property: dc:creator Value String: Hoskins, W.G.
Property: dc:creator Value String: Ng, Tze Beng
pnds_dc XML Encoding:
<dc:creator>Collinson, Patrick</dc:creator> <dc:creator>Gould, Stephen Jay</dc:creator> <dc:creator>Hoskins, W.G.</dc:creator> <dc:creator>Ng, Tze Beng</dc:creator>
oai_dc XML Encoding:
<dc:creator>Collinson, Patrick</dc:creator> <dc:creator>Gould, Stephen Jay</dc:creator> <dc:creator>Hoskins, W.G.</dc:creator> <dc:creator>Ng, Tze Beng</dc:creator>
Enter corporate names, where possible, in the order suggested by AACR2 chapters 24 for headingds for corporate bodies. In general (rule 24.1) this means entering a corporate body under the name by which it is commonly identified, except when the rules provide for entering it under the name of a higher or related body or the name of a government, e.g.:
Property: dc:creator Value String: Bodleian Library
Property: dc:creator Value String: British Broadcasting Corporation
Property: dc:creator Value String: Loughborough University. Department of Computer Science
Property: dc:creator Value String: United Kingdom. Department for Education and Employment
pnds_dc XML Encoding:
<dc:creator>Bodleian Library</dc:creator> <dc:creator>British Broadcasting Corporation</dc:creator> <dc:creator>Loughborough University. Department of Computer Science</dc:creator> <dc:creator>United Kingdom. Department for Education and Employment</dc:creator>
oai_dc XML Encoding:
<dc:creator>Bodleian Library</dc:creator> <dc:creator>British Broadcasting Corporation</dc:creator> <dc:creator>Loughborough University. Department of Computer Science</dc:creator> <dc:creator>United Kingdom. Department for Education and Employment</dc:creator>
The inclusion of personal and corporate name headings from authority lists constructed according to AACR2, e.g. the Library of Congress Name Authority File (LCNA), is also acceptable.
DC Label:
Creator
DC Name:
dc:creator
DC Definition:
An entity primarily responsible for making the content of the resource.
DC Comment:
Examples of a Creator include a person, an organisation, or a service. Typically, the name of a Creator should be used to indicate the entity.
A person or organisation responsible for making contributions to the content of the resource.
Enter personal names, where possible, in the order suggested by AACR2 chapter 22 for headings of persons, i.e. the entry element should be that part of the name under which the person would normally be listed in authoritative alphabetic lists in his or her language or country of residence or activity (rule 22.4A). Separate other elements with a comma, e.g.:
Property: dc:contributor Value String: Collinson, Patrick
Property: dc:contributor Value String: Gould, Stephen Jay
Property: dc:contributor Value String: Hoskins, W.G.
Property: dc:contributor Value String: Ng, Tze Beng
pnds_dc XML Encoding:
<dc:contributor>Collinson, Patrick</dc:contributor> <dc:contributor>Gould, Stephen Jay</dc:contributor> <dc:contributor>Hoskins, W.G.</dc:contributor> <dc:contributor>Ng, Tze Beng</dc:contributor>
oai_dc XML Encoding:
<dc:contributor>Collinson, Patrick</dc:contributor> <dc:contributor>Gould, Stephen Jay</dc:contributor> <dc:contributor>Hoskins, W.G.</dc:contributor> <dc:contributor>Ng, Tze Beng</dc:contributor>
Enter corporate names, where possible, in the order suggested by AACR2 chapters 24 for headingds for corporate bodies. In general (rule 24.1) this means entering a corporate body under the name by which it is commonly identified, except when the rules provide for entering it under the name of a higher or related body or the name of a government, e.g.:
Property: dc:contributor Value String: Bodleian Library
Property: dc:contributor Value String: British Broadcasting Corporation
Property: dc:contributor Value String: Loughborough University. Department of Computer Science
Property: dc:contributor Value String: United Kingdom. Department for Education and Employment
pnds_dc XML Encoding:
<dc:contributor>Bodleian Library</dc:contributor> <dc:contributor>British Broadcasting Corporation</dc:contributor> <dc:contributor>Loughborough University. Department of Computer Science</dc:contributor> <dc:contributor>United Kingdom. Department for Education and Employment</dc:contributor>
oai_dc XML Encoding:
<dc:contributor>Bodleian Library</dc:contributor> <dc:contributor>British Broadcasting Corporation</dc:contributor> <dc:contributor>Loughborough University. Department of Computer Science</dc:contributor> <dc:contributor>United Kingdom. Department for Education and Employment</dc:contributor>
The inclusion of personal and corporate name headings from authority lists constructed according to AACR2, e.g. the Library of Congress Name Authority File (LCNA), is also acceptable.
DC Label:
Contributor
DC Name:
dc:contributor
DC Definition:
An entity responsible for making contributions to the content of the resource.
DC Comment:
Examples of a Contributor include a person, an organisation, or a service. Typically, the name of a Contributor should be used to indicate the entity
A person or organisation responsible for making the resource available.
Enter personal names, where possible, in the order suggested by AACR2 chapter 22 for headings of persons, i.e. the entry element should be that part of the name under which the person would normally be listed in authoritative alphabetic lists in his or her language or country of residence or activity (rule 22.4A). Separate other elements with a comma, e.g.:
Property: dc:publisher Value String: Collinson, Patrick
Property: dc:publisher Value String: Gould, Stephen Jay
Property: dc:publisher Value String: Hoskins, W.G.
Property: dc:publisher Value String: Ng, Tze Beng
pnds_dc XML Encoding:
<dc:publisher>Collinson, Patrick</dc:publisher> <dc:publisher>Gould, Stephen Jay</dc:publisher> <dc:publisher>Hoskins, W.G.</dc:publisher> <dc:publisher>Ng, Tze Beng</dc:publisher>
oai_dc XML Encoding:
<dc:publisher>Collinson, Patrick</dc:publisher> <dc:publisher>Gould, Stephen Jay</dc:publisher> <dc:publisher>Hoskins, W.G.</dc:publisher> <dc:publisher>Ng, Tze Beng</dc:publisher>
Enter corporate names, where possible, in the order suggested by AACR2 chapters 24 for headingds for corporate bodies. In general (rule 24.1) this means entering a corporate body under the name by which it is commonly identified, except when the rules provide for entering it under the name of a higher or related body or the name of a government, e.g.:
Property: dc:publisher Value String: Bodleian Library
Property: dc:publisher Value String: British Broadcasting Corporation
Property: dc:publisher Value String: Loughborough University. Department of Computer Science
Property: dc:publisher Value String: United Kingdom. Department for Education and Employment
pnds_dc XML Encoding:
<dc:publisher>Bodleian Library</dc:publisher> <dc:publisher>British Broadcasting Corporation</dc:publisher> <dc:publisher>Loughborough University. Department of Computer Science</dc:publisher> <dc:publisher>United Kingdom. Department for Education and Employment</dc:publisher>
oai_dc XML Encoding:
<dc:publisher>Bodleian Library</dc:publisher> <dc:publisher>British Broadcasting Corporation</dc:publisher> <dc:publisher>Loughborough University. Department of Computer Science</dc:publisher> <dc:publisher>United Kingdom. Department for Education and Employment</dc:publisher>
The inclusion of personal and corporate name headings from authority lists constructed according to AACR2, e.g. the Library of Congress Name Authority File (LCNA), is also acceptable.
DC Label:
Publisher
DC Name:
dc:publisher
DC Definition:
An entity responsible for making the resource available.
DC Comment:
Examples of a Publisher include a person, an organisation, or a service. Typically, the name of a Publisher should be used to indicate the entity.
The language of the resource. Use the language codes defined in RFC 3066.
For example:
Property: dc:language Vocabulary Encoding Scheme: dcterms:RFC3066 Value String: en-GB
pnds_dc XML Encoding:
<dc:language encSchemeURI="http://purl.org/dc/terms/RFC3066">en-GB</dc:language>
oai_dc XML Encoding:
<dc:language>en-GB</dc:language>
DC Label: Language
DC Name: dc:language
DC Definition: A language of the intellectual content of the resource.
DC Comment: Recommended best practice is to use RFC 3066 which, in conjunction with ISO639 [18]), defines two- and three primary language tags with optional subtags. Examples include "en" or "eng" for English, "akk" for Akkadian", and "en-GB" for English used in the United Kingdom.
The spatial coverage of the content of the resource.
The value should be a UK Ordnance Survey Grid Reference. Where more than one term is used, a separate statement should be used for each one.
For example:
Property: dcterms:spatial Syntax Encoding Scheme: pndsterms:OSGridRef Value String: SN 045 055
Property: dcterms:spatial Syntax Encoding Scheme: pndsterms:OSGridRef Value String: NN 166 712
pnds_dc XML Encoding:
<dcterms:spatial encSchemeURI="http://purl.org/mla/pnds/terms/OSGridRef">SN 045 055</dcterms:spatial> <dcterms:spatial encSchemeURI="http://purl.org/mla/pnds/terms/OSGridRef">NN 166 712</dcterms:spatial>
Use dc:coverage in place of dcterms:spatial (without the encScheme attribute) when exposing simple oai_dc records.
oai_dc XML Encoding:
<dc:coverage>SN 045 055</dc:coverage> <dc:coverage>NN 166 712</dc:coverage>
As an alternative to a Grid Reference, the value should be a UK Post Code. Where more than one term is used, a separate statement should be used for each one.
For example:
Property: dcterms:spatial Syntax Encoding Scheme: pndsterms:UKPostCode Value String: BA2 7AY
Property: dcterms:spatial Syntax Encoding Scheme: pndsterms:UKPostCode Value String: BS8 1HH
pnds_dc XML Encoding:
<dcterms:spatial encSchemeURI="http://purl.org/mla/pnds/terms/UKPostCode">BA2 7AY</dcterms:spatial> <dcterms:spatial encSchemeURI="http://purl.org/mla/pnds/terms/UKPostCode">BS8 1HH</dcterms:spatial>
Use dc:coverage in place of dcterms:spatial (without the encScheme attribute) when exposing simple oai_dc records.
oai_dc XML Encoding:
<dc:coverage>BA2 7AY</dc:coverage> <dc:coverage>BS8 1HH</dc:coverage>
DC Label: Spatial
DC Name: dcterms:spatial
DC Definition: Spatial characteristics of the intellectual content of the resource.
DC Comment:
The temporal coverage of the content of the resource.
This may be a term taken from an existing controlled vocabulary or using a format for representing a date or period of time. Where more than one term is used, a separate statement should be used for each one.
Values should be provided using the DCMI Period comma-separated value format.
For example:
Property: dcterms:temporal Syntax Encoding Scheme: dcterms:Period Value String: name=The Great Depression; start=1929; end=1939;
pnds_dc XML Encoding:
<dcterms:temporal encSchemeURI="http://purl.org/dc/terms/Period">name=The Great Depression; start=1929; end=1939;</dcterms:temporal>
Use dc:coverage in place of dcterms:temporal (without the encScheme attribute) when exposing simple oai_dc records.
oai_dc XML Encoding:
<dc:coverage>name=The Great Depression; start=1929; end=1939;</dc:coverage>
Alternatively, values should be provided as a period of time (time interval) formatted according to the rules specified in ISO8601
For example:
Property: dcterms:temporal Syntax Encoding Scheme: pndsterms:ISO8601Per Value String: 1985-04-12T23:20:50/1985-06-25T10:30:00
Property: dcterms:temporal Syntax Encoding Scheme: pndsterms:ISO8601Per Value String: 1985-04-12T23:20:50/P0001-02-15T12:30:00
pnds_dc XML Encoding:
<dcterms:temporal encSchemeURI="http://purl.org/mla/pndsterms/ISO8601Per">1985-04-12T23:20:50/1985-06-25T10:30:00</dcterms:temporal> <dcterms:temporal encSchemeURI="http://purl.org/mla/pndsterms/ISO8601Per">1985-04-12T23:20:50/P0001-02-15T12:30:00</dcterms:temporal>
Use dc:coverage in place of dcterms:spatial (without the encScheme attribute) when exposing simple oai_dc records.
oai_dc XML Encoding:
<dc:coverage>1985-04-12T23:20:50/1985-06-25T10:30:00</dc:coverage> <dc:coverage>1985-04-12T23:20:50/P0001-02-15T12:30:00</dc:coverage>
DC Label: Temporal
DC Name: dcterms:temporal
DC Definition: Temporal characteristics of the intellectual content of the resource.
DC Comment:
A collection of which the resource is part, where applicable.
Provide the URI of the collection's home page. For example:
Property: dcterms:isPartOf Value URI: http://www.intothenet.org/
pnds_dc XML Encoding:
<dcterms:isPartOf valueURI="http://www.intothenet.org" />
Use dc:relation (with the URI as element content) in place of dcterms:isPartOf when exposing simple oai_dc records.
oai_dc XML Encoding:
<dc:relation>http://www.intothenet.org/</dc:relation>
DC Label: Is Part Of
DC Name: dcterms:isPartOf
DC Definition: The described resource is a physical or logical part of the referenced resource.
DC Comment:
An associated thumbnail image representation of the resource, where applicable.
Provide the URI of that image:
Property: pndsterms:thumbnail Value URI: 
pnds_dc XML Encoding:
<pndsterms:thumbnail valueURI="http://www.example.org/images/thumbnails/1234.jpg" />
Use dc:relation (with the URI as element content) in place of pndsterms:thumbnail when exposing simple oai_dc records.
oai_dc XML Encoding:
<dc:relation>http://www.example.org/images/thumbnails/1234.jpg</dc:relation>
Label: Thumbnail Image
Name: pndsterms:thumbnail
Definition: A thumbnail image representation of the resource.
Comment:
This section lists the properties that are optional under the application profile.
For each property, PNDS-specific guidelines are provided, followed by the authoritative definitions and comments from the Dublin Core Metadata Initiative.
The digital manifestation of the resource.
Recommended best practice is to select a term from the IANA registered list of Internet Media Types (or MIME types). For example:
Property: dc:format Vocabulary Encoding Scheme: dcterms:IMT Value String: text/html
pnds_dc XML Encoding:
<dc:format encSchemeURI="http://purl.org/dc/terms/IMT">text/html</dc:format>
oai_dc XML Encoding:
<dc:format>text/html</dc:format>
DC Label:
Format
DC Name:
dc:format
DC Definition:
The physical or digital manifestation of the resource.
DC Comment:
Typically, Format may include the media-type or dimensions of the resource. Format may be used to determine the software, hardware or other equipment needed to display or operate the resource. Examples of dimensions include size and duration Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types (MIME) defining computer media formats (IANA).
The spatial coverage of the content of the resource.
The value may be a term taken from an existing controlled vocabulary (e.g. the Getty Thesaurus of Geographic Names). In this case, use a vocabulary encoding scheme to indicate the vocabulary being used. An identifier for the encoding scheme should be provided in the form of a URI.
Where more than one term is used, a separate statement should be used for each one.
For example:
Property: dcterms:spatial Vocabulary Encoding Scheme: dcterms:TGN Value String: World, Europe, United Kingdom, England, Bath and Northeast Somerset, Bath
Property: dcterms:spatial Vocabulary Encoding Scheme: dcterms:TGN Value String: World, Europe, United Kingdom, England, Bristol
pnds_dc XML Encoding:
<dcterms:spatial encSchemeURI="http://purl.org/dc/terms/TGN">World, Europe, United Kingdom, England, Bath and Northeast Somerset, Bath</dcterms:spatial> <dcterms:spatial encSchemeURI="http://purl.org/dc/terms/TGN">World, Europe, United Kingdom, England, Bristol</dcterms:spatial>
Use dc:coverage in place of dcterms:spatial (without the encScheme attribute) when exposing simple oai_dc records.
oai_dc XML Encoding:
<dc:coverage>World, Europe, United Kingdom, England, Bath and Northeast Somerset, Bath</dc:coverage> <dc:coverage>World, Europe, United Kingdom, England, Bristol</dc:coverage>
DC Label: Spatial
DC Name: dcterms:spatial
DC Definition: Spatial characteristics of the intellectual content of the resource.
DC Comment:
The temporal coverage of the content of the resource.
This may be a term taken from an existing controlled vocabulary or using a format for representing a date or period of time. Where more than one term is used, a separate statement should be used for each one.
Where temporal coverage is provided using a term drawn from a controlled vocabulary, use a vocabulary encoding scheme to indicate the vocabulary being used. An identifier for the encoding scheme should be provided in the form of a URI.
For example:
Property: dcterms:temporal Vocabulary Encoding Scheme: dcterms:LCSH Value String: Middle Ages
pnds_dc XML Encoding:
<dcterms:temporal encSchemeURI="http://purl.org/dc/terms/LCSH">Middle Ages</dcterms:temporal>
Use dc:coverage in place of dcterms:temporal (without the encScheme attribute) when exposing simple oai_dc records.
oai_dc XML Encoding:
<dc:coverage>Middle Ages</dc:coverage>
DC Label: Temporal
DC Name: dcterms:temporal
DC Definition: Temporal characteristics of the intellectual content of the resource.
DC Comment:
The intended audience for the resource.
The value should be a term from the UK Educational Levels vocabulary. For example:
Property: dcterms:audience Vocabulary Encoding Scheme: meg:UKEL Value String: UK Educational Level 5
pnds_dc XML Encoding:
<dcterms:audience encSchemeURI="hppt://purl.org/meg/terms/UKEL">UK Educational Level 5</dcterms:audience>
This information cannot be expressed using simple oai_dc records.
DC Label: Audience
DC Name: dcterms:audience
DC Definition: A class of entity for whom the resource is intended or useful.
DC Comment: A class of entity may be determined by the creator or the publisher or by a third party.
The following properties are in the DCMES but are not used by this application profile. They are provided here for information.
Dates should be entered in W3CDTF format. The following examples are all valid dates:
<dc:date encSchemeURI="http://purl.org/dc/terms/W3CDTF">1999</dc:date> <dc:date encSchemeURI="http://purl.org/dc/terms/W3CDTF">1999-12-25</dc:date>
DC Label:
Date
DC Name:
dc:date
DC Definition:
A date associated with an event in the life cycle of the resource.
DC Comment:
Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 and follows the YYYY-MM-DD format.
A free-text description of the original version of a resource.
DC Label:
Source
DC Name:
dc:source
DC Definition:
A Reference to a resource from which the present resource is derived.
DC Comment:
The present resource may be derived from the Source resource in whole or in part. Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system
-- PeteJohnston - 13 Jun 2005