Storing Dublin Core Metadata in a ROADS database
[This document is a part of DC-ROADS: ROADS as a (Dublin Core) Metadata Management Environment ]
This document only considers the representation of the basic 15 Dublin Core elements. Qualified Dublin Core is not considered at this point although this will become an issue in the near future.
UKOLN has a direct requirement to be able to extract Dublin Core metadata from a ROADS database and dynamically embed in into web pages. A Dublin Core template for this purpose is presented.
A mapping between the major ROADS templates and the Dublin Core elements sets already exists  so this option should be relatively straightforward.
This approach is the obvious solution if resources are already described according to a standard ROADS template.
This approach might be suitable in circumstances where the aim is to catalogue resources directly in terms of the Dublin Core, for example if the cataloguers are already familiar with the Dublin Core.
At its simplest a ROADS Dublin Core template would be:
# Dublin Core Basic Template-Type: DUBLINCOREBASIC Handle::::m: Title-v*::::o: Creator-v*::::o: Subject-v*::::o: Description-v*::::o: Publisher-v*::::o: Contributors-v*::::o: Date-v*::::o: Type-v*::::o: Format-v*::::o: Identifier-v*::::o: Source-v*::::o: Language-v*::::o: Relation-v*::::o: Coverage-v*::::o: Rights-v*::::o:
This template allows all 15 elements to be repeated with all elements being optional. The template type and handle attributes are added to provide a valid ROADS template.
The possibility of creating a new ROADS DOCUMENT template based on the Dublin Core is discussed in  . The main change from the above template is to suggest the use of ROADS 'clusters' for describing the complex elements Creator, Publisher, and Contributor. In  it is suggested that Creator and Contributor should be represented by a PERSON cluster and Publisher by an ORGANIZATION cluster. We modify this slightly to model all three complex elements using an AGENT cluster which has an attribute to distinguish between person and corporate body. This is a more flexible approach.
A simple AGENT cluster is defined as:
Template-Type: AGENT Handle::::o: Name::::o: Type:::Person|CorporateBody:o: Email::::o:
This AGENT template is used within a slightly more complex template than the one above:
Template-Type: DUBLINCORESIMPLE Handle::::m: Title::::o: Creator-(AGENT*)::::o: Subject::::o: Description::::o: Publisher-(AGENT*)::::o: Contributor-(AGENT*)::::o: Date-v*::::o: Type::::o: Format::::o: Identifier-v*::::o: Source::::o: Language::::o: Relation-v*::::o: Coverage::::o: Rights::::o:
Note that some elements have been made non-repeatable based on local requirements. A more general template would allow all elements to be repeated.
It may also be appropriate to add a RECORD element as discussed in  for recording metadata regarding the record itself (metadata author, creation date, etc).
The next step would be to create a ROADS template for qualified Dublin Core and to create authority files for elements with controlled vocabularies.
[<A HREF="http://www.ukoln.ac.uk/metadata/">Metadata</A>] [<A HREF="http://www.ukoln.ac.uk/">UKOLN</A>]