Interoperability between metadata formats

Mapping ROADS/IAFA templates to Dublin Core

Michael Day
UKOLN: The UK Office for Library and Information Networking,
University of Bath, Bath, BA2 7AY, United Kingdom
http://www.ukoln.ac.uk/
m.day@ukoln.ac.uk

November 1997


The most widely used ROADS/IAFA templates are the DOCUMENT and SERVICE templates. The mappings in this document will therefore concentrate on these template types:

1. Summary mapping from ROADS/IAFA DOCUMENT template to Dublin Core.

ROADS/IAFA TemplateDublin Core
Template Type: DOCUMENT
Handle:No DC equivalent
Category:Type
Title:Title
URI-v1:Identifier (scheme=URL)
Short-Title:Title
Alternative-Title: Title
Author-Handle-v1:No DC equivalent
Author-Name-v1:Creator
Author-Work-Phone-v1:No DC equivalent
Author-Work-Fax-v1:No DC equivalent
Author-Work-Postal-v1:No DC equivalent
Author-Job-Title-v1:No DC equivalent
Author-Department-v1:No DC equivalent
Author-Email-v1:No DC equivalent
Author-Home-Phone-v1:No DC equivalent
Author-Home-Postal-v1:No DC equivalent
Author-Home-Fax-v1:No DC equivalent
Admin-Handle-v1:No DC equivalent
Admin-Name-v1: Contributor (type=administration)
Admin-Work-Phone-v1:No DC equivalent
Admin-Work-Fax-v1: No DC equivalent
Admin-Work-Postal-v1:No DC equivalent
Admin-Job-Title-v1:No DC equivalent
Admin-Department-v1:No DC equivalent
Admin-Email-v1:No DC equivalent
Admin-Home-Phone-v1:No DC equivalent
Admin-Home-Postal-v1:No DC equivalent
Admin-Home-Fax-v1:No DC equivalent
Source:Source
Requirements:No DC equivalent
Description:Description
Citation:No DC equivalent
Publication-Status:No DC equivalent
Publisher-Handle-v1:No DC equivalent
Publisher-Name-v1:Publisher
Publisher-Type-v1:No DC equivalent
Publisher-Postal-v1:No DC equivalent
Publisher-City-v1:No DC equivalent
Publisher-State-v1:No DC equivalent
Publisher-Country-v1:No DC equivalent
Publisher-Email-v1:No DC equivalent
Publisher-Phone-v1:No DC equivalent
Publisher-Fax-v1:No DC equivalent
Copyright:No DC equivalent
Creation-Date:Date
Discussion:No DC equivalent
Keywords:Subject (scheme=keyword)
Version-v1:No DC equivalent
Format-v1:Format
Size-v1:No DC equivalent
Language-v1:Language
Character-Set-v1:Format
ISBN-v1:Identifier (scheme=ISBN)
ISSN-v1:Identifier (scheme=ISBN)
Last-Revision-Date-v1:No DC equivalent
Subject-Descriptor-Scheme-v1:Subject (Scheme)
Subject-Descriptor-v1:Subject
To-Be-Reviewed-Date:No DC equivalent
Record-Last-Verified-Email:No DC equivalent
Record-Last-Verified-Date:No DC equivalent
Comments:No DC equivalent
Destination:No DC equivalent
Record-Last-Modified-Date: No DC equivalent
Record-Last-Modified-Email: No DC equivalent
Record-Created-Date: No DC equivalent
Record-Created-Email:No DC equivalent

NOTES

Qualifiers: Dublin Core has in the past supported the idea of defining qualifiers. This is currently under discussion, so reference has only been made here to those qualifiers referred to in the Dublin Core/USMARC crosswalk: http://lcweb.loc.gov/marc/dccross.html.

Title: ROADS templates permit the inclusion of alternative and short titles. Dublin Core does allow for the inclusion of more than one title but a scheme for abbreviated or other titles is not currently defined.

Admin-name: The name of a administrator could be included under Dublin Core "Contributors", but the term might have to be used as a "role" qualifier, e.g.

Contributors (type=admin): Oxford
University Computing Service
.

Format and Character-set: The ROADS Format element is designed to describe the formats in which a resource is available, while the Character-Set attribute would include well-known information about the character-set used, e.g. ASCII. This information might be usefully added to the Dublin Core "Format" attribute, so the information in both fields could be mapped there.

Subject-Descriptor-Scheme and Subject-Descriptor: The Dublin Core "Subject" element can be qualified with a scheme. When mapping from ROADS templates the Subject-Descriptor-Scheme attribute should become the "scheme", while the Subject-Descriptor would become the attribute, e.g.:

Subject-Descriptor-Scheme-v1: DDC
Subject-Descriptor-v1: 027.00254

to:

Subject (scheme=DDC): 027.00254

Variants: ROADS templates are designed to cope with variants, e.g. a document in more than one language can be described. Variants are identified in ROADS templates in the following way:

Language-v1: English
Language-v2: German
URL-v1:http://www.ub2.lu.se/tk/demos/DO9603-meng.html
URL-v2:http://www.ub2.lu.se/tk/demos/DO9603-manus.html

Dealing with these variants, where present, could be problematic, although it is possible that each variant could form a separate Dublin Core record

Administrative metadata: The ROADS template contains a lot of administrative metadata which is not relevant to the Dublin Core context


2. Summary mapping from ROADS/IAFA SERVICE template to Dublin Core.

ROADS/IAFA TemplateDublin Core
Template-Type: SERVICE
Handle: No DC equivalent
Title: Title
URI-v1:Identifier (scheme=URL)
Admin-Handle-v1:No DC equivalent
Admin-Name-v1: Contributor (role=administration)
Admin-Work-Phone-v1:No DC equivalent
Admin-Work-Fax-v1: No DC equivalent
Admin-Work-Postal-v1:No DC equivalent
Admin-Job-Title-v1:No DC equivalent
Admin-Department-v1:No DC equivalent
Admin-Email-v1:No DC equivalent
Admin-Home-Phone-v1:No DC equivalent
Admin-Home-Postal-v1:No DC equivalent
Admin-Home-Fax-v1:No DC equivalent
Owner-Handle-v1:No DC equivalent
Owner-Name-v1:Contributor (role=owner)
Owner-Type-v1:No DC equivalent
Owner-Postal-v1:No DC equivalent
Owner-City-v1:No DC equivalent
Owner-State-v1:No DC equivalent
Owner-Country-v1:No DC equivalent
Owner-Email-v1:No DC equivalent
Owner-Phone-v1:No DC equivalent
Owner-Fax-v1:No DC equivalent
Sponsoring-Handle-v1:No DC equivalent
Sponsoring-Name-v1:Contributor (role=sponsor)
Sponsoring-Type-v1:No DC equivalent
Sponsoring-Postal-v1:No DC equivalent
Sponsoring-City-v1:No DC equivalent
Sponsoring-State-v1:No DC equivalent
Sponsoring-Country-v1:No DC equivalent
Sponsoring-Email-v1:No DC equivalent
Sponsoring-Phone-v1:No DC equivalent
Sponsoring-Fax-v1:No DC equivalent
Publisher-Handle-v1:No DC equivalent
Publisher-Name-v1:Publisher
Publisher-Type-v1:No DC equivalent
Publisher-Postal-v1:No DC equivalent
Publisher-City-v1:No DC equivalent
Publisher-State-v1:No DC equivalent
Publisher-Country-v1:No DC equivalent
Publisher-Email-v1:No DC equivalent
Publisher-Phone-v1:No DC equivalent
Publisher-Fax-v1:No DC equivalent
Description: Description
Authentication:No DC equivalent
Registration:No DC equivalent
Charging-Policy:No DC equivalent
Access-Policy:No DC equivalent
Access-Times:No DC equivalent
Keywords: Subject (scheme=keyword)
Subject-Descriptor-v1:Subject
Subject-Descriptor-Scheme-v1:Subject
Short-Title: Title
Alternative-Title:Title
Language: Language
ISSN:Identifier (scheme=ISSN)
Discussion:No DC equivalent
Source:Source
Category:Type
To-Be-Reviewed-Date:No DC equivalent
Record-Last-Verified-Email:No DC equivalent
Record-Last-Verified-Date:No DC equivalent
Comments:No DC equivalent
Destination:No DC equivalent
Record-Last-Modified-Date: No DC equivalent
Record-Last-Modified-Email: No DC equivalent
Record-Created-Date:No DC equivalent
Record-Created-Email:No DC equivalent

NOTES

Comments are much the same as for the DOCUMENT template above. There is possibly a need for Contributor-Name and Sponsor-Name to map to the Dublin Core "Contributors" element, but "roles" would have to be defined for this


3. Summary mapping from ROADS/IAFA IMAGE template to Dublin Core.

ROADS/IAFA TemplateDublin Core
Template Type: IMAGE
Handle:No DC equivalent
Category:Type
Title:Title
URI-v1:Identifier (scheme=URL)
Short-Title:Title
Alternative-Title: Title
Author-Handle-v1:No DC equivalent
Author-Name-v1:Creator
Author-Work-Phone-v1:No DC equivalent
Author-Work-Fax-v1:No DC equivalent
Author-Work-Postal-v1:No DC equivalent
Author-Job-Title-v1:No DC equivalent
Author-Department-v1:No DC equivalent
Author-Email-v1:No DC equivalent
Author-Home-Phone-v1:No DC equivalent
Author-Home-Postal-v1:No DC equivalent
Author-Home-Fax-v1:No DC equivalent
Admin-Handle-v1:No DC equivalent
Admin-Name-v1: Contributor (type=administration)
Admin-Work-Phone-v1:No DC equivalent
Admin-Work-Fax-v1: No DC equivalent
Admin-Work-Postal-v1:No DC equivalent
Admin-Job-Title-v1:No DC equivalent
Admin-Department-v1:No DC equivalent
Admin-Email-v1:No DC equivalent
Admin-Home-Phone-v1:No DC equivalent
Admin-Home-Postal-v1:No DC equivalent
Admin-Home-Fax-v1:No DC equivalent
Source:Source
Requirements:No DC equivalent
Description:Description
Citation:No DC equivalent
Publication-Status:No DC equivalent
Publisher-Handle-v1:No DC equivalent
Publisher-Name-v1:Publisher
Publisher-Type-v1:No DC equivalent
Publisher-Postal-v1:No DC equivalent
Publisher-City-v1:No DC equivalent
Publisher-State-v1:No DC equivalent
Publisher-Country-v1:No DC equivalent
Publisher-Email-v1:No DC equivalent
Publisher-Phone-v1:No DC equivalent
Publisher-Fax-v1:No DC equivalent
Copyright:No DC equivalent
Creation-Date:Date
Discussion:No DC equivalent
Keywords:Subject (scheme=keyword)
Format-v1:Format
Size-v1:No DC equivalent
Language-v1:Language
Character-Set-v1:Format
ISBN-v1:Identifier (scheme=ISBN)
ISSN-v1:Identifier (scheme=ISBN)
Last-Revision-Date-v1:No DC equivalent
Subject-Descriptor-Scheme-v1:Subject (Scheme)
Subject-Descriptor-v1:Subject
To-Be-Reviewed-Date:No DC equivalent
Record-Last-Verified-Email:No DC equivalent
Record-Last-Verified-Date:No DC equivalent
Comments:No DC equivalent
Destination:No DC equivalent
Record-Last-Modified-Date: No DC equivalent
Record-Last-Modified-Email: No DC equivalent
Record-Created-Date: No DC equivalent
Record-Created-Email:No DC equivalent

NOTES

See comments on DESCRIPTION template.


Acknowledgements

UKOLN is funded by the British Library Research and Innovation Centre, the Joint Information Services Committee of the UK Higher Education Funding councils, as well as by project funding from JISC's eLib Programme and the European Union. UKOLN also receives support from the University of Bath, where it is based.


For mappings from ROADS/IAFA to Dublin Core, see <URL:http://www.ukoln.ac.uk/metadata/interoperability/iafa_dc.html>.


This work was carried out for the Resource Organisation And Discovery in Subject-based services (ROADS) project funded by the Electronic Libraries (eLib) Programme.

More information on ROADS can be found on the project's Web pages: <URL:http://www.ilrt.bris.ac.uk/roads/>


Maintained by: Michael Day of UKOLN The UK Office for Library and Information Networking, University of Bath.
Document created: 3-Nov-1997
Last updated: 12-Aug-1998

[UKOLN Metadata] [UKOLN Mapping Between Metadata Formats]