III · 27
Dublin Core Format (KEV)
A KEV metadata format carrying the fifteen elements of unqualified Dublin Core. Discovery systems use it for records that are not articles, books, theses or patents.
The Dublin Core KEV format, info:ofi/fmt:kev:mtx:dc, was registered by NISO Committee AX alongside the standard and is the metadata format of the Dublin Core Community Profile (info:ofi/pro:dccp-2004). It is not part of SAP1, but resolvers and tools commonly accept it. Open-source discovery systems such as VuFind and Blacklight emit it, often in COinS, for videos, statutes, archival material and other records that fit the book or journal formats poorly.
Format identifier
rft_val_fmt=info:ofi/fmt:kev:mtx:dcKeys
Every key is optional and repeatable. Each corresponds to a Dublin Core 1.1 element.
| Key | Dublin Core element |
|---|---|
rft.title | A name given to the resource |
rft.creator | Entity primarily responsible for the content |
rft.subject | Topic, keywords or classification |
rft.description | Account of the content, such as an abstract |
rft.publisher | Entity making the resource available |
rft.contributor | Entity contributing to the content |
rft.date | Date of an event in the resource's life cycle, typically YYYY-MM-DD |
rft.type | Nature or genre (e.g. from the DCMI Type Vocabulary) |
rft.format | Physical or digital manifestation, e.g. a media type |
rft.identifier | Unambiguous reference such as a URI, DOI or ISBN |
rft.source | Resource from which this one is derived |
rft.language | Language of the content (RFC 3066 / ISO 639 codes such as en) |
rft.relation | A related resource |
rft.coverage | Spatial or temporal scope |
rft.rights | Rights information |
Example
url_ver=Z39.88-2004
&ctx_ver=Z39.88-2004
&rft_val_fmt=info:ofi/fmt:kev:mtx:dc
&rfr_id=info:sid/example.org:catalogue
&rft.type=video
&rft.title=The+Art+of+Living
&rft.creator=Example+Studio
&rft.date=2004
&rft.language=en
&rft.format=video%2Fmp4Illustrative values. Discovery systems also use non-DCMI type words (book, statute, video_film_online_resource); the format does not restrict them.
Notes
- Because every key repeats, several creators or subjects are sent as repeated
rft.creatororrft.subjectpairs. - Resolver support varies. Many knowledge-base lookups only work on journal and book metadata, so a DC OpenURL may produce a catalogue search rather than a full-text link.
- For SAP2 (XML) the equivalent is OAI Dublin Core,
info:ofi/fmt:xml:xsd:oai_dc.