Dublin Core/FINMARC/GILS Crosswalk

GILS:

• Title

Author or Creator

The person(s) or organization(s) primarily responsible for the intellectual content of the resource. For example, authors in the case of written documents, artists, photographers, or illustrators in the case of visual resources. Qualifier possible: type.

FINMARC:

• 720$a (Uncontrolled Name added entry heading -- Entry element (e.g. usually the last name; the section preceding the comma in the DC Author/Creator tag); and 720$h (Uncontrolled name added entry heading -- Forenames (the section after the comma in the DC Author/Creator tag, if present).
  
• If type=personal: 100$a (Personal name main entry heading -- Entry element (e.g. usually the last name; the section preceding the comma in the DC Author/Creator tag); and 100$h (Personal name main entry heading -- Forenames (the section after the comma in the DC Author/Creator tag, if present).
• If type=corporate: 110$a (Corporate name main entry heading -- Entry element)

If the Author element is repeated in the DC record, the data from repeats should go either to 700$a and $h or 710$a (see contributor tag for details) or 720$a and $h, depending on the type values.

GILS:

• Originator

Subject and Keywords

The topic of the resource, or keywords or phrases that describe the subject or content of the resource. The intent of the specification of this element is to promote the use of controlled vocabularies and keywords. This element might well include scheme-qualified classification data (for example, Library of Congress Classification Numbers or Dewey Decimal numbers) or scheme-qualified controlled vocabularies (such as MEdical Subject Headings or Art and Architecture Thesaurus descriptors) as well. Qualifier possible: scheme.

FINMARC:

• If scheme=UDC: 080$a (Universal Decimal Classification
  
• If scheme=DDC: 082$a (Dewey Decimal Call Number/Classification number)
  
• If scheme=NLM: 090$a (National Library of Medicine
  
• If scheme=YKL: 098$a (Finnish Public Library Classification
  
• If scheme=LCSH: 650$a (Subject added entry--topical term)
  
• If scheme=YSA: 652 $a (Finnish general thesaurus - subject heading). If the heading contains hyphens, the first of these should be converted into $b, and the rest to $x, which may be repeated.
  
• If scheme=FIMU: 653 $a (Finnish music thesaurus - subject heading). If the heading contains hyphens, the first of these should be converted into $b, and the rest to $x, which may be repeated.
  
• If scheme=FIGE: 655 $a (Geographical name as subject heading). If the heading contains hyphens, the first of these should be converted into $b, and the rest to $x, which may be repeated.
  
• If scheme=FILE: 665 $a (Finnish legal subject headings). If the heading contains hyphens, the first of these should be converted into $b, and the rest to $x, which may be repeated.
  
• If scheme=FISO: 670 $a (Finnish thesaurus of the Social Sciences - subject heading). If the heading contains hyphens, the first of these should be converted into $b, and the rest to $x, which may be repeated.
  
• If scheme=FIRE: 680 $a (Religion indexes subject headings). If the heading contains hyphens, the first of these should be converted into $b, and the rest to $x, which may be repeated.
  
• If scheme=FIFO: 685 $a (Finnish forestry subject headings). If the heading contains hyphens, the first of these should be converted into $b, and the rest to $x, which may be repeated.
  
• If scheme=FIAG: 686 $a (Finnish agrcultural subject headings). If the heading contains hyphens, the first of these should be converted into $b, and the rest to $x, which may be repeated.
  
• If scheme=FIEP: 660 $a (Finnish index terms for education and psychology). If the heading contains hyphens, the first of these should be converted into $b, and the rest to $x, which may be repeated.
  
• If scheme=MESH: 690$a (Medical Subject Heading)
  
• 692$a (Index Term--Uncontrolled)
  

GILS:

• Uncontrolled Term

Description

A textual description of the content of the resource, including abstracts in the case of document-like objects or content descriptions in the case of visual resources. Future metadata collections might well include computational content description (spectral analysis of a visual resource, for example) that may not be embeddable in current network systems. In such a case this field might contain a link to such a description rather than the description itself.

FINMARC:

• 519$a (Abstract)

GILS:

• Abstract

Publisher

The entity responsible for making the resource available in its present form, such as a publisher, a university department, or a corporate entity. The intent of specifying this field is to identify the entity that provides access to the resource.

FINMARC:

• 260$b (Publication statement/Name of publisher)

GILS

• Distributor

Other Contributors

Person(s) or organization(s) in addition to those specified in the CREATOR element who have made significant intellectual contributions to the resource but whose contribution is secondary to the individuals or entities specifed in the CREATOR element (for example, editors, transcribers, illustrators, and convenors). Qualifier possible: type.

FINMARC:

• 720$a (Added Entry--Uncontrolled Name/Name) $e [content of role qualifier]
  
• If type=personal: 700$a (Added entry--Personal Name-- Entry element (e.g. usually the last name; the section preceding the comma in the DC Author/Creator tag); and 700$h (Added entry--Personal Name-- Forenames (the section after the comma in the DC Author/Creator tag, if present)
  
• If type=corporate: 710$a (Added Entry--Corporate Name)
  

GILS

• Contributor (to be renamed from Author)

Date

The date the resource was made available in its present form. The recommended best practice is an 8 digit number in the form YYYYMMDD as defined by ANSI X3.30-1985. In this scheme, the date element for the day this is written would be 19961203, or December 3, 1996. Many other schema are possible, but if used, they should be identified in an unambiguous manner. Qualifier possible: type
FINMARC:

• 260$c (Date of publication)
  

• Date of Publication

Resource Type

The category of the resource, such as home page, novel, poem, working paper, technical report, essay, dictionary. It is expected that RESOURCE TYPE will be chosen from an enumerated list of types. A preliminary set of such types can be found at the following URL: http://www.roads.lut.ac.uk/Metadata/DC-ObjectTypes.html.

FINMARC:

• 500$a (General notes - keyword indexed), except:
  
• 502$a (Dissertation note), if the data content of the element is Diss., Dissertation, PhD Thesis, Väitösk., Väitöskirja or Avhandling.
  
• 509$a (Thesis note - not diss.), if the data content of the element is Masters Thesis, Honours Thesis, Opinn. or Opinnäyte.
  Conversion of this DC element to FINMARC is problematic, since some proposed resource categories like "Dissertation" have their own tags, but many of them can only be accommodated in the generic notes tag. From the Nordic Metadata point of view, it will not be possible to facilitate provision of resource type names in local languages via single template - national template modifications are probably necessary. An alternative to this is an intelligent converter, which could alter for instance "PhD Thesis" into "Väitöskirja".

GILS

• Medium

Format

The data representation of the resource, such as text/html, ASCII, Postscript file, executable application, or JPEG image. The intent of specifying this element is to provide information necessary to allow people or machines to make decisions about the usability of the encoded data (what hardware and software might be required to display or execute it, for example). As with RESOURCE TYPE, FORMAT will be assigned from enumerated lists such as registered Internet Media Types (MIME types). In principal, formats can include physical media such as books, serials, or other non-electronic media.

FINMARC:

• 258$c (File format). The data content should be converted from text/html to HTML.

  If MARBI accepts a proposed modification of USMARC, this tag may be later replaced by:

• 856$q (Electronic Location and Access/File transfer mode)
  

• Available Linkage Type

Resource Identifier

String or number used to uniquely identify the resource. Examples for networked resources include URLs and URNs (the latter will hopefully replace the former as an identifier in the long run). Other globally-unique identifiers,such as International Standard Book Numbers (ISBN) or other formal names would also be candidates for this element. Qualifier possible: scheme.

FINMARC:

• 856$u (Uniform Resource Locator)
  
• If type is IP address: 856$b (Access number)
• If scheme=NBN: 015$a (National Bibliography Number)
  
• If scheme=ISBN: 021$a (International Standard Book Number)
  
• If scheme=ISSN: 022$a (International Standard Serial Number)
  
• If scheme=URN: 856$g (URN)
  
• If scheme=ISRC: 024 $a (International Standard Recording Code)
  
• If scheme=ISMN: 025$a (International Standard Music Number
  
• If scheme=ISRN: 027$a (International Standard Report Number
  

When generating exchange records, the ID's based on the following systems should be converted also to the 001 tag: NBN, ISBN, ISRC, ISMN and ISRN.

If the converter has means of checking validity of ISBN and other established codes, and finds that the ID is not correct, the conversion is done to subfield $c in respective tag.

If NBN, ISBN, ISRC, ISMN or ISRN data is repeated in the DC record, all occurrences after the first one are ignored.

URN's are always based on other identifiers like NBN's or ISBN's. It is possible to extract the basic ID from URN string. For URN's based on NBN's, this is done by stripping string "URN:NBN:fi-" from the beginning of the URN; the rest may be placed into 015$a.

GILS:

• Available Linkage

Source

The work, either print or electronic, from which this resource is derived, if applicable. For example, an html encoding of a Shakespearean sonnet might identify the paper version of the sonnet from which the electronic version was transcribed.

FINMARC:

• 501$a (General notes - not keyword indexed)

• Sources of Data

Language

Language of the intellectual content of the resource. Where practical, the content of this field should coincide with the Z39.53 three character codes for written languages. Qualifier possible: scheme.
FINMARC:

• If scheme=Z39.53: 041$a (Language of the main work)

GILS:

• Language of Resource (note that GILS assumes use of Z39.53)

A three-character language code standard is currently under development as: ISO 639-2 (not yet available electronically)

Relation

Relationship to other resources. The intent of specifying this element is to provide a means to express relationships among resources that have formal relationships to others, but exist as discrete resources themselves. For example, images in a document, chapters in a book, or items in a collection. A formal specification of RELATION is currently under development. Users and developers should understand that use of this element should be currently considered experimental. Possible qualifiers: scheme, type.

FINMARC:

• 501$a (General notes - not keyword indexed)

GILS:

• Cross Reference Relationship
  
• If scheme=URL: Cross Reference Linkage

Coverage

The spatial locations and temporal durations characteristic of the resource. Formal specification of COVERAGE is currently under development. Users and developers should understand that use of this element should be currently considered experimental. Possible qualifier: type.

FINMARC:

• 500$a (General note)
  
• If type=spatial: 655 $a (Geographical name as subject heading). If the heading contains hyphens, the first of these should be converted into $b, and the rest to $x, which may be repeated.
  
• If type=temporal: 652$a (Finnish General Thesaurus - Subject heading)

GILS:

• Supplemental Information
  
• If type=spatial: Bounding Coordinates
  
• If type=temporal: Time Period Textual

Rights Management

The content of this element is intended to be a link (a URL or other suitable URI as appropriate) to a copyright notice, a rights-management statement, or perhaps a server that would provide such information in a dynamic way. The intent of specifying this field is to allow providers a means to associate terms and conditions or copyright statements with a resource or collection of resources. No assumptions should be made by users if such a field is empty or not present. Qualifiers possible: URL, URN. Nota bene: not available in the Nordic Metadata template yet (will be added shortly).

FINMARC:

• If there is no scheme information, no FINMARC conversion is possible
  
• If scheme=URL: 856$u (with $3=rights)

• Use Constraints

Notes

Leader: a fixed field comprising the first 24 character positions (00-23) of each record that provides information for the processing of the record. The following positions should be generated:

Character Position 06: Type of record
• If resource is an electronic information resource, use code "m" (default in Nordic Metadata)
• If resource is geospatial, use code "e"
• All others use code "a"

008 Fixed Length Data Elements: Forty character positions (00-39) containing positionally-defined data elements that provide coded information about the record as a whole or about special bibliographic aspects of the item being cataloged. For records originating as Dublin Core, the following character positions are used:

• Character positions 00-05: Date the FINMARC record was created or converted (from Date element with scheme=ANSI X3.30 or ISO 8601 and qualifier type=modified or may be generated; formatted as YYMMDD)
• Character positiion 06: Time indicator. Default value "s" (single date) should be always generated
• Character positions 07-10: Date of Publication (YYYY portion from Date if present)
• Character positions 35-37: Language. May be generated from data in Language if scheme=Z39.53.
• Other character positions can default to fill characters (ASCII 7C)

Uses for mapping Dublin Core to MARC

Enhancement of simple resource description record. A cataloging agency may wish to extract the metadata provided in Dublin Core style (presumably in HTML or SGML) and convert the data elements to MARC fields, resulting in a skeletal record. That record might then be enhanced as needed to add additional information generally provided in the particular catalog.

Searching across syntaxes and databases. Libraries have large systems with valuable information in MARC bibliographic records (which may also be called metadata). Over the past few years with the expansion of electronic resource over the Internet, other syntaxes have also been considered for providing metadata. The Library of Congress has worked with a group of SGML experts to create a Document-Type Definition (DTD) for MARC, so that conversions can be made between SGML and MARC in a standardized way. It will be important for systems to be able to search metadata in different syntaxes and databases and have commonality in the definition and use of elements.