Telematics for Libraries project BIBLINK (LB 4034)
|
Mapping BIBLINK Core (BC) to UNIMARC Telematics for Libraries project BIBLINK (LB 4034) |
|
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
Version 1.0, 10 September 1998
This mapping is a revised version of that published as part of WP4 [1]. It additionally takes into account the BIBLINK minimum data set and its mapping to DC produced in D4.1 [2].
BIBLINK Core (BC) fields are a set of simple text fields. Their semantics are outlined in the BIBLINK Workspace Functional Specification [3].
It is assumed that Dublin Core QUALIFIERS may be used for the following elements: DC.Creator and DC.Contributor, primarily to indicate differences between personal names and corporate bodies. Also for DC.Title to indicate the existence of a subtitle.
Similarly Dublin Core Schemes may be used for DC.Identifier and DC.Subject. If no SCHEME is present, the default SCHEME for DC.Identifier is URL, and the default SCHEME for DC.Subject are subject keywords.
The information received from publishers will not contain all of this information. For example, it will probably not contain subject information based on defined SCHEMES like DDC or LCSH. It will also be missing the checksum or unique identifiers generated by NBAs at the other end of the BW process.
The UNIMARC generated by this mapping will not be valid. It will be missing the mandatory Record Label and the 100 General Processing Data and 801 Originating Source fields. Depending upon the quality of the DC being input into the mapping process, it may also be missing the mandatory 001 Record Identifier and 200 Title and Statement of Responsibility fields.
Within mapped fields, certain fields will have to be validated. The mapping assumes that personal names and corporate names will be entered in direct order. This need not be the case. Similarly, the LCSH entered in DC.Subject may contain topical, geographical and chronological subdivisions, etc. and there is no easy way of distinguishing between these. The mapping assumes that all subdivisions in LCSH are topical.
This UNIMARC validation is not part of the BW process, and should be carried out by NBAs according to the cataloguing and indexing standards they use.
|
BIBLINK Core |
UNIMARC field |
|
BIBLINK.Checksum |
Suggest that a 9-- National Use Block field should be defined for this. |
|
BIBLINK.Edition |
205 $a Edition Statement |
|
BIBLINK.Extent |
307 $a Notes Pertaining to Physical Description. This field is used in preference to 215 Physical Description and/or 230 Material Specific Area: Computer File Characteristics because 215 & 230 are used to record information in forms corresponding to the relevant ISBD documents. |
|
BIBLINK.Frequency |
326 $a Frequency Statement Note (Serials) |
|
BIBLINK.PlacePublication |
210 $a Place of Publication, Distribution, etc. |
|
BIBLINK.Price |
Suggest that a 9-- National Use Block field should be defined for this to aid conversion back to DC. |
|
BIBLINK.SystemRequirements |
337 $ Technical Details Note (Computer Files) (provisional) |
|
DC.Creator |
700 $a Personal Name - Primary Intellectual Responsibility [if there is only one DC.Creator element present]. Indicator 2 should be "0" for data entry in direct order. |
|
DC.Creator |
701 $a Personal Name - Alternative Intellectual Responsibility [if there is more than one DC.Creator element present]. Indicator 2 should be "0" for data entry in direct order. |
|
DC.Creator |
200 $f First Statement of Responsibility. If more than one DC.Creator element present, all should be included separated by commas. |
|
DC.Creator.Organization |
710 $a Corporate Body Name - Primary Intellectual Responsibility [if there is only one DC.Creator element present]. Indicator 1 should be "O" for Corporate name, Indicator 2 should be "2" for names entered in direct order. |
|
DC.Creator.Organization |
711 $a Corporate Body Name - Alternative Intellectual Responsibility [if there is more than one DC.Creator element present]. Indicator 1 should be "O" for Corporate name, Indicator 2 should be "2" for names entered in direct order. |
|
DC.Creator.Organization |
200 $f First Statement of Responsibility. If more than one DC.Creator element present, all should be included separated by commas. |
|
DC.Contributor |
701 $a Personal Name - Alternative Intellectual Responsibility [if there is more than one DC.Creator element present]. Indicator 2 should be "0" for data entry in direct order. |
|
DC.Contributor.Organization |
711 $a Corporate Body Name - Alternative Intellectual Responsibility [if there is more than one DC.Creator element present]. Indicator 1 should be "0" for Corporate name, Indicator 2 should be "2" for names entered in direct order. |
|
DC.Date |
210 $d Date of Publication, Distribution, etc. |
|
DC.Description |
330 $a Summary or Abstract |
|
DC.Format |
336 $a Type of Computer File (provisional) |
|
DC.Identifier |
856 $a URL |
|
DC.Identifier |
001 Record Identifier [?] |
|
DC.Identifier SCHEME=DOI |
014 $a Article Identifier with $2doi |
|
DC.Identifier SCHEME=ISBN |
010 $a ISBN |
|
DC.Identifier SCHEME=ISSN |
011 $a ISSN |
|
DC.Identifier SCHEME=SICI |
014 $a Article Identifier with $2sici |
|
DC.Language |
101 $a Language of the Item |
|
DC.Publisher |
210 $c Name of Publisher, Distributor, etc. |
|
DC.Rights |
Suggest that a 9-- National Use Block field should be defined for this to aid conversion back to DC. |
|
DC.Source |
324 $a Original Version Note |
|
DC.Subject |
610 $a Uncontrolled Subject Terms. Indicator 1 should be "0" to note that no decision has been taken as to whether the term is primary or secondary. Each term in a comma-separated list in DC.Subject should be prefaced by (repeatable) $a. |
|
DC.Subject SCHEME=LCSH |
606 $a Topical Name Used as Subject, $x for each topical subdivision. Add $2lc on to end of field to indicate that it is LCSH. |
|
DC.Subject SCHEME=DDC |
676 $a DDC |
|
DC.Subject SCHEME=UDC |
675 $a UDC |
|
DC.Subject SCHEME=LCC |
680 $a LCC |
|
DC.Title |
200 $a Title Proper |
|
DC.Title.Alternate |
517 $a Other Variant Titles |
Table - BIBLINK Core to UNIMARC Mapping
Maintained by: Michael Day, Research Officer, UKOLN The UK Office for Library
and Information Networking, University of Bath.
Last updated: 24-Sep-1998.