The Library of Congress >> Especially
for Librarians and Archivists >> StandardsThe Library of Congress >> Especially
for Librarians and Archivists >> Standards
HOME >> MARC Development >> Proposals List
DATE: May 25, 2007
REVISED:
NAME: Changes for the German and Austrian conversion to MARC 21
SOURCE: Deutsche Nationalbibliothek (German National Library) (DNB)
SUMMARY: The German and Austrian communities are converting to MARC 21 from a format that they have used for many years, Maschinelles Austauschformat für Bibliotheken (MAB, Automated Library Exchange Format). This Proposal describes additions to MARC 21 that they need in order to support their existing data transfer activities. It is divided into 13 subparts.
KEYWORDS: MAB; Germany; Subfield $0 for authority record control numbers (BD, AD, CD, CI); Subfield $w for bibliographic record control numbers (BD); Number normalization (BD); Multivolume level code (BD); Nature of contents codes (BD); Field 015 (BD); National Bibliographic Number (BD); Replacement record information (BD); Field 682 (AD); Deleted Heading Information (AD); Field 653 (BD); Index term - Uncontrolled (BD); Type indicator in field 653 (BD); Former call numbers (BD, HD); Geographic name added entry (BD); Normalized publication numbering (BD); Normalized publication dates (BD)
RELATED:
STATUS/COMMENTS:
5/25/2007 - Made available to the MARC community for discussion.
06/24/2007 - Results of the MARC Advisory Committee discussion
07/13/2007 - Results of LC/LAC/BL review - Approved
1 BACKGROUND
1.1 Introduction
When electronic data processing made its entrance in the cataloging departments of libraries in the 1970s the desire awoke to rationalize the descriptive and subject cataloging by shared and cooperative creation and use of the cataloging records at the same time. This is the reason why library networks were founded in some of the German states. Nowadays seven library networks exist in Germany and Austria playing a key role in the process of data exchange (coordinate the application of library codes and standards, organize the interlibrary loan, etc.).
The headquarters of the library networks act as service providers offering a broad spectrum of products for often heterogeneous institutions, e.g. state, regional and university libraries as well as public and special libraries, and have to consider different premises and needs. The library networks cooperate closely with the German National Library (Deutsche Nationalbibliothek, DNB) and the German Union Catalogue of Serials (Zeitschriftendatenbank, ZDB), e.g. within the Consortium of Library Networks (Arbeitsgemeinschaft der Verbundsysteme, AGV).
The German National Library maintains and hosts the three national authority files for personal names (Personennamendatei, PND), corporate bodies (Gemeinsame Körperschaftsdatei, GKD), and subject headings (Schlagwortnormdatei, SWD). The authority files are updated, edited and managed by the German National Library in cooperation with the library networks. The German Union Catalogue of Serials comprises series and other continuing resources. Maintained by the Berlin State Library (Staatsbibliothek zu Berlin) and technically supported by German National Library, the ZDB supplies bibliographic and holding information records to the library networks. Altogether the seven library networks, the German National Library and the German Union Catalogue of Serials hold 360 million records representing around 90 million unique titles.
All exchange procedures are done by means of a national library data exchange format (Maschinelles Austauschformat für Bibliotheken, MAB) that was developed in 1973. The Data Formats Expert Group (Expertengruppe Datenformate) has been responsible for the development and the maintenance of the MAB format under the auspices of the German National Library. The latest format version, MAB2, is a national data exchange format and therefore restricted to Germany and Austria.
In December 2004 the Committee for Library Standards (Standardisierungsausschuss) confirmed its willingness to improve the exchange and interoperability of data between Germany and Austria and the world by introducing major changes into national library standards. As a first step it was decided to move from the German and Austrian data exchange format MAB2 to the international standard MARC 21. The Committee for Library Standards decided to use MARC 21 uniformly and delegated the preparation for the change to the German National Library and its Office for Library Standards (Arbeitsstelle für Standardisierung, AfS) as well as to the Data Formats Expert Group.
A complete mapping from MAB2 to MARC 21 was considered basic to the work so it was begun in 2005. Based on a comparison of both data exchange formats the Data Formats Expert Group devoted several meetings to work out and discuss essential points and aspects in advance. During 2006 the concordance between MAB2 and MARC 21 was completed which functions as a reference for the mapping of format elements. It shows on the one hand where MAB2 data appears in MARC 21, and on the other hand where the mapping fails.
Dealing with the differences between MAB2 and MARC 21 was the primary task for the Expert Group which identified the following vital areas (1) the connection between headings and appropriate authority files, (2) the mapping of hierarchical structures in the context of multivolume works (multipart monographs, series), and (3) sorting of volume numbers and dates. All these aspects are part of the German library tradition and crucial for them when it comes to data exchange; they therefore raise the question, if and how it is possible to transport the connected information without a loss. Keeping in mind that stability and consistency of MARC 21 are of high priority the experts got more acquainted with the MARC format and in many cases were finally able to find solutions either by proposing the needed format elements into MARC 21 or at last by defining them on a national basis (D-MARC). By doing so the experts minimized the amount of change needed for their use of MARC 21. Only the remaining data elements considered to be absolutely necessary for the information transfer were collected and transformed into discussion items for the meeting of the MARBI Committee. For some items, several alternative ways to satisfy the German need are presented for discussion.
Discussion Paper No. 2007-DP01 (Changes for the German and Austrian conversion to MARC 21) was presented to the MARC community in December 2006. It was discussed in detail during the MARBI meetings of the ALA Midwinter Meeting 2007 in Seattle. The very valuable reactions of the international experts at MARBI led to discussions in the German and Austrian Experts' Group. This document is a set of proposals developed from that Discussion Paper.
1.2 Multivolume work record model
Several proposals relate to the model that the MAB community uses for describing multivolume works, including both multivolume monographs and monographic series. The MAB community create one record for every volume of a multivolume work as follows: every single volume has a record of its own; one additional bibliographic record is created for the multivolume work (the set record); every record has to contain all the bibliographically relevant information in order to be complete and independent. They do not create authority records for the multivolume monograph or the monographic series.
From the descriptive cataloging rules in German speaking countries ("Regeln für die Alphabetische Katalogisierung", RAK) there is the distinction between a "Stücktitel", i.e. an independent single volume (a single volume with a strong title), and a "Bandaufführung", i.e. a dependent single volume (a single volume without a strong title, for brevity called a “weak” title below). A strong title is a text string that describes the content of the single volume without any more context needed; a weak title needs the title of the multivolume work to “support” the weak title. An example of a weak title is “A-J” for a volume of an encyclopedia.
Further typical examples for a weak title would be "Abschlussbericht" (Final report), "Allgemeiner Teil" (General part), "Besonderer Teil" (Special part), "Einführung" (Introduction), "Grundlagen" (Basics), "Katalog" (Catalogue), "Kommentar" (Commentary), "Lösungen" (Solutions), "Materialien" (Material), "Textbuch" (Text book), and "Übungen" (Exercises). A title is also considered weak if it is only fully understandable within the context of the multivolume monograph as a whole.
In a case where a single volume of a multivolume work has a strong title the MARC model of fields 490 + 8XX is used in the single volume record (field 440 is not used). The volume title is in the 245 and the set title is transcribed into the 490 and given in its access form in the 8XX. Both places also indicate any volume numbers appropriate to the part represented by the single volume.
In cases where a single volume of a multivolume work has
the German model uses the 245 with $a, $n and $p for the single volume record. Field 245 $a contains the title of the multivolume work, 245 $n contains information about the volume number, and 245 $p contains the weak title of the volume as the name of the part. A linking entry field 773 (Host item entry) provides the connection from the record for the single volume to the record for the multivolume set. It contains at least $w (Record control number) for the set record.
1.3 Use of record control numbers
The German authority files PND (personal name authority file), GKD (corporate body authority file), and SWD (subject heading file) are maintained by the Deutsche Nationalbibliothek. They are updated, edited and managed by the DNB in cooperation with the German regional library networks. The regional networks provide catalogs at the regional level that include authority records for headings that appear in the regional bibliographic records and authority record control numbers in access point fields of the bibliographic records. The DNB provides a weekly update service for the national authority files which the regional networks and other subscribers import as routine updates. In these update processes the authority control numbers are used to match and update authority records and also to match and update headings in the bibliographic records. Because of the heavy dependence on the record control numbers for update and other processes, fields in bibliographic and authority formats that contain established headings need also a subfield for the authority record control number for that heading.
The PND and GKD contain primarily headings for German people and German corporate bodies as the collections of the DNB also focus on German material. But the collections of the other libraries in Germany may contain a large amount of foreign imprints and headings coming from these publications are also added to the DNB authority file. Because of the authority record and heading update practices for the German headings, the same use of record numbers is used between the DNB and the regional catalogs, who in turn send updates to local catalogs in their regions.
In the case of multivolume works, the German community also records bibliographic record control numbers in some instances in volume bibliographic records, as described above in section 1.2.
1.4 Conventions
In some examples * has been supplied to indicate the nonfiling data marker (MARC8 88 (Non-sort begin) and 89 (Non-sort end) that Germany intends to use. Pointed brackets < > are sometimes used to indicate a new element in a field. BD is Bibliographic data format, AD is Authority data format, HD is Holdings data format, CD is Classification data format, and CI is Community Information format. In this paper, multivolume work will refer to both multivolume monographs and monographic series.
DATE: May 25, 2007
SUMMARY: This proposal adds a subfield for the authority record control number to main added and subject access entry fields. The control number is for the authority record for the heading in the field.
KEYWORDS: Fields 1XX (BD, CI); Field 240 (BD); Fields 6XX (BD, CI); Fields 7XX (BD, CD, CI)
1 Discussion
The MAB community has from the early days of the MAB format carried both the headings and the record control numbers of the authority records for the headings in the bibliographic format fields for controlled access points. The purpose of the control numbers has been to facilitate the linking of the headings with the appropriate authority records. The MARC community has relied on the matching of the heading strings for this type of linking when records are taken into a system since the authority record control numbers are not universal. In Germany both the heading strings and the record control numbers are carried. The record control numbers are largely standardized as the DNB number. It is carried in records even if a local control number is also assigned within local systems. The DNB number is similar to the NACO control numbers used for the NACO authority file.
It should be noted that for field 240, the NACO authority file does not contain separate authority records for titles in the 240 field. Those titles are part of author/title heading authority records.
Subfield $0 is proposed to be consistent with its use to link to authority records in the authority 5XX and 7XX fields.
2 Proposed Changes
In the fields and formats listed below define the following subfield for the record control number of the linked authority record for the heading in the field:
$0 -- Authority record control number (R)
The number content would have the same structure as the record control numbers in the 035: the MARC organization code (in parentheses) followed immediately by the number, e.g., (CaBVaU)2835210335.
The Bibliographic, Classification, and Community Information format fields for which the $0 would be defined are the following:
Main Entry Fields
100 - Main Entry–Personal Name (NR) (BD, CI)
110 - Main Entry– Corporate Name (NR) (BD, CI)
111 - Main Entry– Meeting Name (NR) (BD, CI)
130 - Main Entry– Uniform Title (NR) (BD)
240 - Uniform Title (NR) (BD)
Subject Access Fields
600 - Subject Added Entry– Personal Name (R) (BD, CI)
610 - Subject Added Entry– Corporate Name (R) (BD, CI)
611 - Subject Added Entry– Meeting Name (R) (BD, CI)
630 - Subject Added Entry– Uniform Title (R) (BD, CI)
648 - Subject Added Entry– Chronological Term (R) (BD, CI)
650 - Subject Added Entry– Topical Term (R) (BD, CI)
651 - Subject Added Entry– Geographic Name (R) (BD, CI)
654 - Subject Added Entry– Faceted Topical Terms (R) (BD, CI)
655 - Index Term– Genre/form (R) (BD)
656 - Index Term– Occupation (R) (BD, CI)
657 - Index Term– Function (R) (BD, CI)
662 - Subject Added Entry– Hierarchical Place Name (R) (BD)
700-754 - Index Term Fields (CD)
Added Entry Fields
700 - Added Entry–Personal Name (R) (BD, CI)
710 - Added Entry–Corporate Name (R) (BD, CI)
711 - Added Entry–Meeting Name (R) (BD, CI)
730 - Added Entry–Uniform Title (R) (BD, CI)
752 - Added Entry–Hierarchical Place Name (R) (BD)
754 - Added Entry–Taxonomic Identification (R) (BD)
3 Examples
Examples of the use of $0, converted from German records:
110 2# $aSeminar Naturschutz und Landwirtschaft$0(DE-101b)200568-2
110 2# $aUnited States$bTask Force on International Education$0(DE-101b)5302625-1
650 #7 $aSoziologie$0(DE-101b)4077624-4$2swd
650 #7 $aProduct placement$0(DE-101b)4197318-5$2swd
700 1# $aReger, Max,$d1873-1916$0(DLC)n79108398
700 1# $aJoyce, James,$d1882-1941$0(DLC)n79056824
------------------------------
001 310008891
003 DE-101c
100 1# $aBach, Johann Sebastian$d1685-1750
001 300005350
003 DE-101c
100 1# $aBach, Johann Sebastian$t*Die* Brandenburgischen Konzerte
001 310008891
003 DE-101c
100 1# $aBach, Johann Sebastian$4aut$0(DE-101c)310008891
240 10 $a*Die* Brandenburgischen Konzerte$0(DE-101c)300005350
245 00 $aSechs Brandenburgische Konzerte$hMusikdruck$bBWV 1046 - 1051 = Six Brandenburg concertos$cJ. S. Bach. Hrsg. von Heinrich Besseler
700 1# $aBesseler, Heinrich$eHrsg.$4edt$0(DE-101c)310018390
--------------------------------
100 1# $aFaulkes, William$4aut$0(DE-101c)311140009
240 10 $aWerke, Org$0(DE-101c)300847858
245 00 $aAcht festliche Orgelstücke$hMusikdruck$cWilliam Faulkes. Hrsg. von Tobias Zuleger
700 1# $aZuleger, Tobias$eHrsg.$4edt$0(DE-101c)31113999X
100 1# $aHändel, Georg Friedrich$4aut$0(DE-101c)310084954
240 10 $aMessiah <Ausw.>$0(DE-101c)300065175
245 00 $a*Der* Messias$hTonträger$bOratorium HWV 56 ; Highlights = Messiah$cGeorg Friedrich Händel. Text: Charles Jennens ; Dt.: Gottfried Gervinus
700 1# $aGervinus, Gottfried$eText$4aut$0(DE-101c)310801311
100 1# $aNicolau, Dimitri$4aut$0(DE-101c)310768578
240 10 $aDances and melodies$0(DE-101c)300770049
245 00 $aDances and melodies$hTonträger$bop. 125$cDimitri Nicolau
DATE: May 25, 2007
SUMMARY: This proposal adds a subfield for the bibliographic record control number for the series set for use in the series entry fields. The control number is for the bibliographic record for the series heading in the field.
KEYWORDS: Fields 4XX (BD); Fields 8XX (BD)
1 Discussion
The MAB community creates bibliographic set records for multivolume monographs and monographic series, in addition to records for all of the individual items in the monograph/series. (They do not create authority records for the multivolume monograph or the monographic series.) They carry the record control number for the bibliographic set record in each volume/item record along with added entry for the set. The purpose of the control numbers is to facilitate the linking of the added entry with the corresponding set records.
Subfield $w is proposed to be consistent with its use for to link to bibliographic records in the 7XX Linking entry fields in the bibliographic format.
2 Proposed Change
Add subfield $w for the series set record to the Bibliographic format fields listed below
$w - Bibliographic record control number for the series set record (R)
The number content would have the same structure as the record control numbers in the 035: the MARC organization code (in parentheses) followed immediately by the number, e.g., (CaBVaU)2835210335.
The fields for which the $w would be defined are the
following series added entry fields in the Bibliographic
format:
440 Series Statement/Added Entry— Title
800 Series Added Entry— Personal Name
810 Series Added Entry— Corporate Name
811 Series Added Entry— Meeting Name
830 Series Added Entry— Uniform Title
3 Examples
Examples:
800 1# $aNegt, Oskar$tSchriften$vBd. 2$w(DE-101b)967682460
810 2# $aAlbertina <Wien>$tAlbertina exhibition …$v410$w(DE-1a)98.011645.7
830 #0 $aAachen British and American studies$vVol. 7$w(DE-7)55174354-9
DATE: May 25, 2007
SUMMARY: This proposal adds a subfield to authority field 260 (Complex See Reference – Subject) for the authority record control number of any established heading that appears in the field.
KEYWORDS: Field 260 (AD)
1 Discussion
The established heading fields (except the 1XX) in the Authority format also need a subfield for the authority record control number. The 5XX and 7XX fields already have a subfield $0 for the authority record control number of the established heading in the field. However, field 260 (Complex See Reference – Subject) also contains an established heading therefore the record control number is needed in that field.
The German implementations will need the 260 field for a common situation in their subject heading files. SWD contains a special record type for non-established headings indicating that a term is equivalent to a combination of two or more established terms. This is due to the characteristic of the German language that combinations of single terms can equally be phrased as compound words. The German subject indexing rules RSWK (Regeln für den Schlagwortkatalog) stipulate that if both are in common use, the combination of single terms should be preferred to the compound term and references indicate this to the users.
Subfield $0 is proposed in line with the authority record linking in 2007-06/1.
2 Proposed Change
Define subfield $0 in Authority format field 260 as follows:
$0 - Authority record control number (R)
The number content would have the same structure as the record control numbers in the 035: the MARC organization code (in parentheses) followed immediately by the number, e.g., (CaBVaU)2835210335.
3 Examples
008 /09 b
150 ## $aProjektrechnung (project accounting)
260 ## $aProjekt$0(DE-101b)4115645-6 (project)
260 ##$aKostenrechnung$0(DE-101b)4032592-1 (accounting)
008 /09 b
150 ## $aKraftfahrzeugkennzeichen (vehicle registration plate)
260 ## $aKraftfahrzeug$0(DE-101b)4073757-3 (motor vehicle )
260 ## $aKennzeichen$0(DE-101b)4163574-7 (license plate)
DATE: May 25, 2007
SUMMARY: This proposal is for additional subfields in several bibliographic fields to carry normalized forms of part names and numbers, series numbers, and edition numbers. KEYWORDS: Field 245 (BD); Fields 8XX (BD); Field 250 (BD)
1 Discussion
There are three areas where the MAB community would like to have a subfield defined for sorting forms of numeric (primarily) data and some name data. These are fields where the number information is recorded traditionally in a transcribed form and normalization is required to sort them appropriately in ILS/OPAC displays for end users. The three areas are:
(1) numbers and names of part/section in field 245 $n and $p
(2) volume designations in 8XX Series entry fields, subfield $v
(3) edition designation in 250 $a
MAB currently provides a facility to encode this data in a normalized or machine sortable form. The normalization algorithms are not officially standardized, so different algorithms can apply (left orientation, right orientation with leading fill characters, numeric core with or without weighting, etc.). However, the German National Library has rules that function as a standard for German libraries. It is up to the system and its maintainers to decide whether the data they receive can be interpreted and is useful to them or whether they delete the information.
The content of $y would be according to the normalization rules and algorithms of the cataloging institution. For field 245, the volume designation will usually be associated with the 245$n, but when there is no $n, it may be associated with 245$p. For multiple levels with a sequence of repeated $n’s and $p’s the content of $y reflects the whole sequence of all $n’s and $p’s.
2 Proposed Changes
In the Bibliographic format, for the following field define a new subfield $y for the normalized data:
Field 245 <$y - Volume/sequential designation in normalized form (NR)>
Fields 800-830 <$y - Volume/sequential designation in normalized form (NR)>
Field 250 <$y - Edition number in normalized form (NR)>
3 Examples
Field 245:
245 00 $aModernisierungen$n1$y11
245 00 $aModernisierungen$n2$y12
245 00 $aModernisierungen$n3$y13
[...]
245 00 $aModernisierungen$n10$y210
245 00 $aKanton Zürich$nBd. 1$y11
245 00 $aVermessungstechnik$pMechanische Streckenmessung$nTeil 2.$ymes 12
245 00 $a*Die* Rechtsquellen des Kantons St. Gallen$nTeil 1.$p*Die* Rechtsquellen der Abtei St. Gallen$nReihe 2.$p*Die* Alte Landschaft$nBd. 3.$nHälfte 2.$p*Die* Rechtsquellen der Stadt Wil$cnach Vorarbeiten von Magdalen Bless-Grabher bearb. von Peter Erni und Martin Salzmann$y11 12 13 12
245 00 $aMusik Lexikon$pNachtr.$yna
Fields 8XX:
830 #0 $aKlassiker der Weltliteratur$v[Teil 1]$y11$w(DE-101b)97994967X
830 #0 $aKlassiker der Weltliteratur$v[Teil 2]$y12$w(DE-101b)97994967X
830 #0 $aKlassiker der Weltliteratur$v[Teil 3]$y13$w(DE-101b)97994967X
[...]
830 #0 $aKlassiker der Weltliteratur$v[Teil 10]$y210$w(DE-101b)97994967X
800 1# $aNegt, Oskar$tSchriften$vBd. 2$y12$w(DE-101b)967682460
810 2# $aAlbertina <Wien>$tAlbertina exhibition …$v410$y3410$w(DE-1a)98.011645.7
830 #0 $aAachen British and American studies$vVol. 16$y216$w(DE-7)55174354-9
Field 250:
250 ## $a1. Aufl.$y11
250 ## $a2., korrigierte Aufl.$y12
250 ## $a[3. Aufl.]$y13
250 ## $a4., vollst. überarb. Aufl.$y14
250 ## $a5., erw. Aufl.$y15
250 ## $a6., neu bearb. Aufl.$y16
250 ## $a7., überarb. und aktualisierte Aufl.$y17
250 ## $a8., durchges. Aufl.$y18
250 ## $a9., vollst. durchges. Aufl.$y19
250 ## $a10., unveränderte Aufl.$y210
250 ## $a1. - 10. Tsd.$y11
250 ## $aVersion 1.1.7$y11 11 17
250 ## $aOrig.-Ausg.$yor
250 ## $aUngekürzte Lizenzausg.$yunl
250 ## $aFrankfurter Ausg.$bhrsg. von Luzius Keller$yfra
250 ## $aNew rev. ed$ynere
DATE: May 25, 2007
SUMMARY: This proposal establishes codes to enable indicaton of the level of a multivolume record within its bibliographic hierarchy.
KEYWORDS: Leader/7 (BD); Leader/19 (BD)
1 Discussion
The German record encoding model also requires additional information concerning the exact level of records related to multivolume monographs and explicit indication of whether the volume title is weak or strong.
(1) The distinction between the set record for a multivolume work and a single volume record of a multivolume work is needed on the record level. The distinction enables efficiencies for activities that use the different types of records. The set record is mainly used in acquisition functions, while the single volume records are needed mainly for lending and interlibrary loan.
(2) The distinction between single volume records that contain strong titles and those with only a weak title (i.e., without a strong title) is needed at the record level. This information is used in a system for record level-based processing of the different types of records. A single volume with a strong title can be handled as any other one-part monograph. In contrast to that a single volume without a strong title which has a 245 title that is distinctive only by combining a $a and a $n and or $p in field 245.
The examination of the presence of $n and/or $p in order to distinguish between the cases is not sufficient, as information about a part of a serial is transported in $n and/or $p of 245, also. The presence of the 773 cannot be used for this distinction as the MARC field 773 is also used for the hosts for component parts in addition to using it for the physically separate volumes of multivolume monographs.
A coded position needs to be defined where the following values can be indicated:
Multivolume monograph sets are encoded as monographic in the Leader/7 bibliographic level – a single item monograph and a multivolume monograph are not distinguished and there is no 008 location appropriate for the distinction. The two item level designations are difficult to place in any of the coded data fields for monographs.
During discussions in January 2007, the suggestion was made to use Leader/19 (Linked record requirement) which currently has values # (related record not required) and r (related record required). That position is used to warn that another record may be needed to make a display since the title of a 7XX linked item is not in the bibliographic record field. This position has not been used very much (at all?) so it might be possible to extend it to cover this new title-related information. Since this is very irregular to redefine a position, its use was checked against the OCLC database and there are no occurrences of a non-blank value in Leader /19. If Leader/19 is not currently used then redefinition with non-overlapping values was considered an option.
It should be noted that the current data model for MARC 21 is to use Holdings records for each volume to handle circulation and loan. The multivolume monographs with weak titles are represented by only the set record in the bibliographic file.
2 Proposed Change
Redefine the Leader/19 in the Bibliographic format as follows:
Position 19 Multivolume monograph record level
# Not specified or not applicable
a Set record
b Volume record, independent title
c Volume record, dependent title
r Linked record requirement (OBSOLETE)
3 Examples
Set record:
LDR/7 m
LDR/19 a
100 1#$a Kierkegaard, Søren$4aut
243 1# $a Sammlung
245 00 $a Gesammelte Werke und Tagebücher$cSören Kierkegaard. Aus
dem Dän. übers. und mit wiss. Anm. vers. von Emanuel
Hirsch ...
Volume record for part with strong title:
LDR/7 m
LDR/19 b
100 1# $a Kierkegaard, Søren$4aut
243 1# $a Sammlung$ldt.
245 00 $a Philosophische Brocken
800 1# $a Kierkegaard, Søren$tGesammelte Werke und Tagebücher$vAbt.
10
Volume record, for part without strong title:
LDR/7 m
LDR/19 c
100 1# $a Kierkegaard, Søren$4aut
245 00 $a Gesammelte Werke und Tagebücher$cSören Kierkegaard. Aus dem Dän. übers. und mit wiss. Anm. vers. von Emanuel Hirsch ...$n Abt. 37.$p Registerband
773 18 $w 96773763X
DATE: May 25, 2007
SUMMARY: This proposal establishes a code for offprints in the 008/24-27, (Nature of Contents), of the 008 for Books.
KEYWORDS: Field 008/24-27 (BD)
1 Discussion
The MAB community uses codes for the nature of contents in a similar way as they are defined in MARC in field 008/24-27 (Nature of contents) for Books. One additional code is needed:
Offprint – a publication that originally was published as an article in a monograph or a serial and that is also issued separately and independently (Sonderdruck)
Consideration was given to using 008/23 (Form of item) for this code, but 008/23 is considered key for distinguishing microform from print from electronic. An offprint could be electronic, thus one distinction, offprint or electronic, would be lost depending on which is coded.
2 Proposed Change
Define for the 008/24-27 in the Books 008 in the Bibliographic format:
2 - Offprint
3 Examples
008/24 2
100 1# $aRöderer, Olaf$0(DE-101b)124857132$4aut
245 00 $aTarot$bSäulen der Einweihung ; Sonderdruck der Zeitschrift Radiaesthesie Nr. 2/2003$cOlaf Röderer
260 ## $aSt. Gallen$bVerl. RGS$c2003
008/24 2
100 1# $aSchäfer, Ulrich$0(DE-101b)12461048X$4aut
245 00 $aSplit- versus Vollorgan-Lebertransplantation bei erwachsenen Empfängern$beine retrospektive Fall-Kontroll-Studie$cvorgelegt von Ulrich Schäfer
300 ## $aS. 648 - 657$bgraph. Darst.$c28 cm
500 ## $aAus: The journal of the American College of Surgeons / Vol. 195. 2002. - Text engl.
502 ## $aHamburg, Univ., Diss., 2001
740 ## $aSplit liver transplantation and risk to the adult recipient
DATE: May 25, 2007
SUMMARY: This proposal establishes a subfield for cancelled or invalid National Bibliography Numbers in field 015 (National Bibliography Number) of the bibliographic format.
KEYWORDS: Field 015 (BD)
The German National library produces a National Bibliography and assigns a National Bibliography Number (NBN) to each item within the National Bibliography scope. That number is entered in the record for the item in field 015 (National Bibliography Number).
In two circumstances a previously assigned NBN may be made invalid, but it needs to continue to be carried in the MARC record marked as cancelled, similarly to the cancelled numbers in the $z subfield of 016 (National Bibliographic Agency Control Number), 020 (ISBN), 022 (ISSN), and 024 (Other Standard Identifier) fields.
(1) Upgrade. If a publication has gone through a CIP type of cataloging process for pre-publication. After the publication has arrived in the DNB, the record is upgraded and a new NBN is assigned and it is announced anew in one of the NBN publication series. The old number must be kept in the record as a former reference.
(2) Correction. In certain cases a publication that had been announced before has to be announced anew as during the cataloging process a new decision or change is made that has to be given to the public. In these cases the record has to be corrected or revised. During preparation for the second (or subsequent) announcement a new NBN is given to the record. The old NBN must be stored in the record as an invalid number. (Only one former NBN is kept by the DNB.)
A distinction between the two cases, upgrade and correction, is not needed.
2 Proposed Change
Define in field 015 (National Bibliography Number) in the Bibliographic format:
$z - Canceled/invalid national bibliography number (R)
The number content would have the same structure as in field 015$a.
3 Examples
015 ## $a06,A29,1122$z05,N51,1204$2dnb
015 ## $a06,A44,1607$z06,A28,2368$2dnb
015 ## $a06,A29,0382$z05,A21,0597$z04,N48,0463$2dnb
DATE: May 25, 2007
SUMMARY: This proposal defines an indicator in field 653 (Index term – Uncontrolled) to encode the type of keyword in the field.
KEYWORDS: Field 653 (BD, CI); Field 753 (CD)
1 Discussion
The MAB community distinguishes uncontrolled subject names and terms by type: topical, geographic, personal name, corporate name. By distinguishing the categories, more specific keyword indices can be built up, and the precision of searching can be improved.
The second indicator of field 653 (Index term – Uncontrolled) is proposed for this distinction. Current users of the field could continue leaving the second indicator blank (but now meaning “no information provided”), or group the keywords by type and use the second indicator for the type.
653 - INDEX TERM – UNCONTROLLED (R)
Indicators
First - Level of index term
# - No information provided
0 - No level specified
1 - Primary
2 - Secondary
Second - <Type of term or name>
# - <No information provided>
<0 - Topical>
<1 - Personal name>
<2 - Corporate name>
<3 - Meeting name>
<4 - Chronological term>
<5 - Geographic name>
<6 - Genre/form>
Subfield Codes
$a - Uncontrolled term (R)
$6 - Linkage (NR)
$8 - Field link and sequence number (R)
2 Proposed Change
Define the second indicator in field 653 (Index term – Uncontrolled) as indicated above in the Bibliographic (field 653), Classification (field 753), and Community Information (field 653) formats.
3 Examples
245 10 $aGesetz und Freiheit$beine Philosophie der Kunst$cHarald Fricke
653 #0 $aGesetz
653 #0 $aFreiheit
240 10 $aHere comes everybody$ldt.
245 10 $a*Ein* Mann in Dublin namens Joyce$cAnthony Burgess. [Übers. ins Dt.: Gisela u. Manfred Triesch]
653 #0 $aMann
653 #5 $aDublin
653 #1 $aJoyce
245 00 $aQuestions and answers on the needs of children and UNICEF
653 #0 $aChildren
653 #2 $aUNICEF
DATE: May 25, 2007
SUMMARY: This proposal defines a new field to carry information about a record that is replacing a deleted record. The field is used in the delete record.
KEYWORDS: Field 882 (BD)
1 Discussion
When a bibliographic record is deleted, in some cases the bibliographic records and holdings records related to this bibliographic record can entirely be redirected to another bibliographic record. This is especially needed in the context of the German Union Catalog of Serials (ZDB) which contains more than 1.2 million bibliographic and more than 6 million holdings records. To be able to manage this redirection process automatically the users of the bibliographic record update services need the number of the replacement bibliographic record as additional information in the deleted record.
A similar field is the Authority field 682 (Deleted Heading Information) which seems to be a suitable model for this purpose, with the addition of a subfield for the record control number of the replacement record. The new Bibliographic field would be structured like the Authority format field 682. The subfield $w for the control number of the replacement record would have the same content structure as the record control numbers in the 035: the MARC organization code (in parentheses) followed immediately by the number, e.g., (CaBVaU)2835210335.
2 Proposed Change
Define new field 882 as follows:
882 - REPLACEMENT RECORD INFORMATION (NR)
Indicators - Both indicators are undefined and contain blanks.
Subfield Codes
$a - Replacement title (R)
$i - Explanatory text (R)
$w - Replacement bibliographic record control number (R)
$6 - Linkage (NR)
$8 - Field link and sequence number (R)
Examples:
882 ## $aColonial-Post$w(DE-600)952932-9
882 ## $aUnited States: Statistical abstract of the United States$ibibliographic record deleted, to be replaced by:$w(DE-600)39-5
DATE: May 25, 2007
SUMMARY: This proposal defines a new subfield in the Authority format field 682 (Deleted Heading Information) to carry the record control number for an authority record that is replacing a deleted record.
KEYWORDS: Field 682 (AD)
1 Discussion
When an authority record has to be deleted, in many cases the bibliographic records related to this authority record can be redirected to another authority record. To be able to manage this redirection process automatically the users of the authority update services need the authority number of the replacement heading record in field 682 (Deleted Heading Information) in the deleted record, in addition to the heading itself, which is already accommodated in the 682$a.
The subfield $0 is proposed since the link is to an authority record. The revised field would be::
682 - DELETED HEADING INFORMATION (NR)
Indicators - Both indicators are undefined and contain blanks.
Subfield Codes
$a - Replacement heading (R)
$i - Explanatory text (R)
<$0 - Replacement authority record control number (R)>
$6 - Linkage (NR)
$8 - Field link and sequence number (R)
The subfield $0 for the control number of the replacement authority record would have the same content structure as the record control numbers in the 035: the MARC organization code (in parentheses) followed immediately by the number, e.g., (CaBVaU)2835210335.
2 Proposed Change
Define subfield $0 (Replacement authority record control number) as repeatable in field 682 of the Authority format.
3 Example
LDR/5-6 xz
016 7# $a108585077$2(DE-101b)
100 1# $aHohenberger, Werner Max
682 ## $aHohenberger, Werner $0(DE-101b)132213052
DATE: May 25, 2007
SUMMARY: This proposal defines a new field 751 in the Bibliographic format for a geographic name used as an added entry.
KEYWORDS: Field 751 (BD)
1 Discussion
The MAB community creates (non-subject) access points for a variety of place names: place of a publication, place of distribution, place of a university to which a dissertation is submitted, place of an event such as a conference. While this information may be present in other fields (e.g., 260 Publication, Distribution, etc., X11 conference name fields, or 502 Dissertation Note), it may not be in a form as it appears in the geographic name authority file and cannot be linked to the authority record. A field for the authorized form of these geographic names is needed along with codes to indicate the role of the place regarding the publication. A new field 751 is proposed.
Field 752 (Added Entry -- Hierarchical place name) was considered for this added entry. Its hierarchical approach was not deemed useful since place names in the German authority file are all only one level.
2 Proposed Change
Define new field 751 field as follows:
751 - ADDED ENTRY – GEOGRAPHIC NAME (R)
Indicators - Both indicators are undefined and contain blanks.
Subfield Codes
$a - Geographic name (NR)
$e - Relator term (R)
$0 - Authority record control number (R)
$2 - Source of heading or term (NR)
$3 - Materials specified (NR)
$4 - Relator code (R)
$6 - Linkage (NR)
$8 - Field link and sequence number (R)
For the usage of $4, new relator codes are needed. Suggested values:
evp - event place
pup - publication place
dbp - distribution place
uvp - university place
3 Examples
Examples (gkd used for source code and above proposed codes for relator codes):
245 00 $aDominanz der Kulturen und Interkulturalität$bDokumentation des VI. Internationalen Kongresses für Interkulturelle Philosophie = Dominance of cultures and interculturality$cRaúl Fornet-Betancourt (Hrsg.)
260 ## $aFrankfurt am Main$bIKO - Verl. für Interkulturelle Kommunikation$c2006
710 2# $aInternational Congress on Intercultural Philosophy <6, 2005, Senftenberg, Schwarze Elster>
751 ## $aSenftenberg <Schwarze Elster>$0(DE-101b)115478-3$2gkd4evp
245 00 $aMysteries of the world$cby Rainer Koethe. Ill. by Peter Klaucke and Frank Kliemt
260 ## $aNuremberg$bTessloff$c1998
751 ## $aNürnberg$0(DE-101b)2003349-7$2gkd$4pup
110 #2 $aPartito Comunista Italiano$bForeign Section$0(DE-101b)9506002-3
245 10 $aForeign bulletin of the Italian Communist Party$cpubl. periodically by the Foreign Section of the Central Committee of the I.C.P.
260 ## $aRome$bLibr. Rinascita$c1959
751 ## $aRoma$0(DE-101b)1030696-1$2gkd$4dbp
100 #1 $aPrömper, Hans$0(DE-101b)124605311
245 10 $aEmanzipatorische Männerbildung$bGrundlagen und Orientierungen zu einem geschlechtsspezifischen Handlungsfeld der Kirche$cHans Prömper
260 ## $aOstfildern$bSchwabenverl.$c2003
502 ## $aZugl.: Frankfurt (Main), Univ., Diss., 2002
751 ## $aFrankfurt <Main>$0(DE-101b)2028282-5$2gkd$4uvp
DATE: May 25, 2007
SUMMARY: This proposal defines a new subfield in Bibliographic format and Holdings format field 852 (Location) to carry information about a former call number or shelf location for a resource.
KEYWORDS: Field 852 (BD, HD)
1 Discussion
According to the German cataloging rules for author’s manuscripts and archives (Regeln für Nachlässe und Autographen, RNA) different call numbers/shelf numbers where a resource has been located before, in cases of a re-location or a reordering/reorganization of a collection as a whole, should be recorded in the bibliographic record.
This could be accommodated in a new subfield in field 852 (Location). Subfields $d, $o, $r, $u, $v, $w are currently unused in the 852 field.
Current subfields in field 852:
$a - Location (NR)
$b - Sublocation or collection (R)
$c - Shelving location (R)
$e - Address (R)
$f - Coded location qualifier (R)
$g - Non-coded location qualifier (R)
$h - Classification part (NR)
$i - Item part (R)
$j - Shelving control number (NR)
$k - Call number prefix (R)
$l - Shelving form of title (NR)
$m - Call number suffix (R)
$n - Country code (NR)
$p - Piece designation (NR)
$q - Piece physical condition (NR)
$s - Copyright article-fee code (R)
$t - Copy number (NR)
$u - Uniform Resource Identifier (R)
$x - Nonpublic note (R)
$z - Public note (R)
$2 - Source of classification or shelving scheme (NR)
$3 - Materials specified (NR)
$6 - Linkage (NR)
$8 - Sequence number (NR)
2 Proposed Change
Define a new subfield in field 852 (Location) in the Bibliographic and Holdings formats:
$d - Former shelving location
3 Example
852 8# $cN.Mus.ms. 2234$dMus.ms.pr. XII/911$d13.492
DATE: May 25, 2007
SUMMARY: This proposal defines a new field in the Bibliographic format for the normalized form of the date of publication and sequential designations for a serial title.
KEYWORDS: Field 363 (BD); Field 863 (HD); Field 362 (BD)
1 Discussion
German and Austrian systems include highly parsed start and end information for serials, in addition to the serial start and end information contained in field 362 (Dates of publication and/or sequential designation), which is in either formatted text or note form. It has mainly been introduced in order for machines to identify which serial record contains an article when serials change names and have split sequences of numbering across all of the records for the different titles. The highly parsed information helps identify which record is for the serial that contains the article and is used for ILL purposes. In the German systems there can be combinations and parallel designations. The same field tells whether information is for a run that has been completed or is ongoing, similar to data found in the 008/06, but here pertaining only to the “subrun” specified in the record/field. In addition, the granular form of the dates of publication and/or sequential designation can serve as a further identifier of the different records for the serial, thus improving matching algorithms.
Three options were discussed during the MARBI meeting in January 2007:
Field 362 with additional subfields
New field 363
Field 863
During discussions the 362 option was discarded. The other two options were recommended for exploration in the proposal.
2 Proposed Change
Option 1: New field 363
The new field 363 is aligned with the 863 field subfields and repeated for a starting and ending information (linked via $8). The indicators are used to indicate start and end fields and also to indicate whether the sequence is open or closed. One new subfield, $u (First level textual designation) is defined.
363 NORMALIZED DATE AND SEQUENTIAL DESIGNATION (R)
Indicator 1 - Start/End designator
Indicates whether the data in the field is the starting information for a sequence or the ending information. A start/end pair is linked via the $8 subfield. [Note that if indicator 1 is 1, then indicator 2 will always be set to 0.]
# - No information given
0 - Starting information
1 - Ending information
Indicator 2 - State of issuance
Indicates whether the data in this field is for a single item not issued sequentially or for a sequence that has terminated (value 0) or a sequence of issues that have not terminated (value 1). [Note that if indicator 2 is 0 in a starting field, and there is no ending field, the field specifies a single issue; if indicator 2 is 1 in a starting field there will be no ending field and the span is open; if the indicator 2 is 0 in a starting field, and there is an ending field, the field specifies the beginning of a closed span.]
# - Not specified
0 - Closed
1 - Open
Subfields:
$a - First level of enumeration (NR)
$b - Second level of enumeration (NR)
$c - Third level of enumeration (NR)
$g - Alternative numbering scheme, first level of enumeration (NR)
$i - First level of chronology (NR)
Year of issuance, or year of coverage.
$v - First level of chronology, issuance (NR)
Included if different from coverage.
$j - Second level of chronology (NR)
Usually month.
$k - Third level of chronology (NR)
Usually day.
$m - Alternative numbering scheme, chronology (NR)
$u - First level textual designation
$x - Nonpublic note (R)
Used for starting and ending notes.
$z - Public note (R)
$6 - Linkage(NR)
$8 - Field link and sequence number (NR)
Option 2: Use of 863
In MARC 21, field 863 has subfields for parsing of the serial designations, in even greater detail, since it can indicate gaps in publication and of enumeration and chronology through the sixth. Field 863 has not, however, been used for this purpose so a technique for designating starting and ending information would be needed. Also an indication that the information in the field is the publishing record of the serial, not any specific institution’s holdings would need to be added. For that reason the 863 has not been pursued here. It is illustrated in the Discussion Paper 2007-DP01.
3 Examples
Simple examples:
362 0# $aNachgewiesen 2004 -
363 01 $i 2004
362 0# $a15.2005,2 -
363 01 $a 15 $b 2 $i 2005
362 0# $a1949(1951); 1956(1959) nachgewiesen
363 00 $i 1949 $v 1951
363 00 $i 1956 $v 1959
More complex examples:
245 00 $aVolkszeitung$bsozialdemokratisches Organ für die Provinz Rheinhessen und die Mainspitze
362 0# $a15.1904,2.Apr. - 44.1933,29.Apr.; damit Ersch. eingest.
363 00 $a 15 $i 1904 $j Apr $k 2 $81
363 10 $a 44 $i 1933 $j Apr $k 29 $81
110 2# $aNordrhein-Westfalen$bLandtag$0(DE-101b)2029522-4
245 00 $aRegister zu den Verhandlungen des Landtags / Landtag Nordrhein-Westfalen$bin der ... Wahlperiode
362 0# $aWahlper. 2.1950/54(1955) - 11.1990/95(1996)
363 00 $u Wahlper. $a 2 $i 1950/54 $v 1955 $81
363 10 $a 11 $i 1990/95 $v 1996 $81
110 2# $aUnited Nations$0(DE-101b)333-5
245 00 $aUN monthly chronicle$cUnited Nations Office of Public Information
362 0# $a1.1964 - 19.1982,5
363 00 $a 1 $i 1964 $81
363 10 $a 19 $b 5 $i 1982 $81
Split sequence for Journal of Polymer Science examples:
245 00 $aJournal of polymer science$ced. board W. T. Astbury [u.a.]
785 00 $tJournal of polymer science / A$w(DE-600)221062-9
785 00 $tJournal of polymer science / B$w(DE-600)221073-3
362 0# $a1.1946 - 62.1962
363 00 $a 1 $i 1946 $81
363 10 $a 62 $i 1962 $81
130 ## $aJournal of polymer science / A
245 00 $aJournal of polymer science$nPart A,$pGeneral papers
780 00 $tJournal of polymer science$w(DE-600)3122-7
785 00 $tJournal of polymer science / A2$w(DE-600)221064-2
362 0# $a1.1963 - 3.1965
363 00 $a 1 $i 1963 $81
363 10 $a 3 $i 1965 $81
130 ## $aJournal of polymer science / A2
245 00 $aJournal of polymer science$nPart A 2, Polymer physics
780 00 $tJournal of polymer science / A$w(DE-600)221062-9
785 00 $tJournal of polymer science / Polymer physics edition$w(DE-600)220649-3
362 0# $a4.1966 - 10.1972,9
363 00 $a 4 $i 1966 $81
363 10$a 10 $b 9 $i 1972 $81
130 ## $aJournal of polymer science / Polymer physics edition
245 00 $aJournal of polymer science$nPolymer physics edition
780 00 $tJournal of polymer science / A 2$w(DE-600)221064-2
785 00 $tJournal of polymer science / B$w(DE-600)233082-9
362 0# $a10.1972,10 - 24.1986,1
363 00 $a 10 $b 10 $i 1972 $81
363 10$a 24 $b 1 $i 1986 $81
130 ## $aJournal of polymer science / B
245 00 $aJournal of polymer science$nB, Polymer physics
780 00 $tJournal of polymer science / Polymer physics edition$w(DE-600)220649-3
362 0# $a24.1986,2 -
363 01 $a 24 $b 2 $i 1986
HOME >> MARC Development >> Proposals List
| The Library of Congress >> Especially
for Librarians and Archivists >> Standards ( 07/13/2007 ) |
Contact Us |