The Library of Congress >> Especially for Librarians and Archivists >> Standards

MARC Standards

HOME >> MARC Development >> Discussion Paper List


MARC DISCUSSION PAPER NO. 2007-DP01

DATE: December 15, 2006
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 Discussion Paper describes additions to MARC 21 that they would like to propose in order to support their existing data transfer activities.

KEYWORDS: MAB; Germany; Subfield $0 for record control numbers (BD, AD, CD, CI); Paper acidity (BD, HD); 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); Subject assignment code (BD); 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:

12/15/2006 - Made available to the MARC community for discussion.

01/21/2007 - Results of the MARC Advisory Committee discussion

Section 2.1 Bring back in proposal.
Section 2.2 Bring back in proposal.
Section 2.3 Bring back in proposal.
Section 2.4 Bring back in proposal.
Section 2.5 There was concern that this was coding for two entities: 1) Nature of title and 2) Hierarchical relationship. It was suggested that Leader/19 could be used. It was also suggested that more examples of both "strong" and "weak" titles should be added to the upcoming proposal.
Section 2.6 Many participants were concerned about the difficulties involved in adding new codes to field 007. In addition, there are problems in using it in bibliographic records since it needs to be applied at the copy level so that it is clearer in holdings. Likewise, some participants felt that a code could not show the mixed aspect of an item's acidity content.
Section 2.7 The group suggested that field 655 be coded instead of defining new codes in field 008/25-27, particularly because it overlaps with existing codes.
Section 2.8 The group suggested that field 655 be used instead of defining new codes in field 008/25-27.
Section 2.9 Bring back in proposal.
Section 2.10 The group did not support using either subfields $2 or $5 to identify assigning institution of subject headings.
Section 2.11 Several members of the group suggested that form/genre and chronological headings should be made accounted for, as well.
Section 2.12 Several members suggested that subfield $w be added to hold the record number of the new record, instead of subfield $0.
Section 2.13 Bring back in proposal.
Section 2.14 Several members suggested coding field 752 for this information. However, other participants suggested defining field 751 for Geographic added entry because it is a cleaner approach. This field was in the CAN/MARC format for a similar purpose, however, it was rarely, if ever used.
Section 2.15 Several participants favored coding former call numbers in field 852 subfield $z (Public note). However, the Germany community, along with a few members of the committee, favored defining a new subfield in field 852 (subfield $d was the preference) for former call number because its archival community will be using former call numbers during its studies.
Section 2.16 The group generally did not like the idea of coding field 362 for normalized form of data of publication. Therefore, the choices are adapting field 863 or defining a new field. The majority of the group wanted to define a new field for this information. The proposal should consider both options.

Discussion Paper 2007-DP01: Changes for the German and Austrian conversion to MARC 21

TABLE OF CONTENTS

Section 1 Background
Section 1.1 Introduction
Section 1.2 Multivolume work record model
Section 1.3 Use of record control numbers
Section 1.4 Conventions
   
Section 2 Additions to MARC 21
Section 2.1 Add subfield for authority record control number to entry fields
Section 2.2 Add subfield for bibliographic set record control numbers to series entry fields
Section 2.3 Add subfield for authority record control numbers in authority field 260
Section 2.4 Normalization of numbers and and names
Section 2.5 Codes for record levels of multivolume monographs and series
Section 2.6 Add indication of paper acidity
Section 2.7 Add new codes for nature of contents for books
Section 2.8 Add new codes for nature of contents for serials
Section 2.9 Add subfield for canceled or invalid National Bibliography Number in field 015
Section 2.10 Add subfield for specification of assigning institution for subject headings
Section 2.11 Add indicator for type of uncontrolled keywords in field 653
Section 2.12 Add field for replacement record information
Section 2.13 Record control numbers in field 682 deleted heading information
Section 2.14 Add a new field for geographic name added entry
Section 2.15 Add subfield for former call numbers
Section 2.16 Add field or subfield for normalized form of dates of publication and/or sequential designation

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 Expert Group Data Formats (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 Expert Group Data Formats.

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 Expert Group Data Formats 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.

Go to: Table of Contents

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.

In cases 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.

Go to: Table of Contents

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 heading 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 is some instances in volume bibliographic records.

Go to: Table of Contents

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.

Go to: Table of Contents


2 ADDITIONS TO MARC 21

2.1 Add subfield for authority record control number to entry fields (BD, CD (700-754), CI (1XX, 7XX))

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.

  $0 -- Authority record control number (R)

The new $0 subfield in these entry fields would be repeatable and the number content would have the same structure as the record control numbers in the 035: (MARC org code)1234567.

The only place that $0 has been used in any of the formats is for the Record control number for the headings in the 5XX (See also from tracing) and the 7XX (heading linking entry) fields in the Authority format.

The Bibliographic format fields for which the $0 would be defined are the following:

Main Entry Fields
100 - Main Entry–Personal Name (NR)
110 - Main Entry– Corporate Name (NR)
111 - Main Entry– Meeting Name (NR)
130 - Main Entry– Uniform Title (NR)
240 - Uniform Title (NR)

Subject Access Fields
600 - Subject Added Entry– Personal Name (R)
610 - Subject Added Entry– Corporate Name (R)
611 - Subject Added Entry– Meeting Name (R)
630 - Subject Added Entry– Uniform Title (R)
648 - Subject Added Entry– Chronological Term (R)
650 - Subject Added Entry– Topical Term (R)
651 - Subject Added Entry– Geographic Name (R)
654 - Subject Added Entry– Faceted Topical Terms (R)
655 - Index Term– Genre/form (R)
656 - Index Term– Occupation (R)
657 - Index Term– Function (R)
662 - Subject Added Entry– Hierarchical Place Name (R)

Added Entry Fields
700 - Added Entry–Personal Name (R)
710 - Added Entry–Corporate Name (R)
711 - Added Entry–Meeting Name (R)
730 - Added Entry–Uniform Title (R)
752 - Added Entry–Hierarchical Place Name (R)
754 - Added Entry–Taxonomic Identification (R)

Examples of the use of $0, converted from German records, are the following:

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$0(dlc)82000012
700 1# $aJoyce, James$0(dlc)958730

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

Go to: Table of Contents

2.2 Add subfield for bibliographic set record control numbers to series entry fields(BD)

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.

  $0 - Record control number for the bibliographic set record for the series (R)

The new $0 subfield in these entry fields would be repeatable and the number content would have the same structure as the record control numbers in the 035: (MARC org code)1234567.

The fields for which the $0 would be defined are the following series added entry fields:

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

Examples:

800 1# $aNegt, Oskar$tSchriften$vBd. 2$0(DE-101b)967682460
810 2# $aAlbertina <Wien>$tAlbertina exhibition …$v410$0(DE-1a)98.011645.7
830 #0 $aAachen British and American studies$vVol. 7$0(DE-7)55174354-9

Go to: Table of Contents

2.3 Add subfield for authority record control numbers in authority field 260 (AD)

The established heading fields (except the 1XX) in the Authority format also need a subfield for the 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.

  $0 - Authority record control number (R)

The new $0 subfield in field 260 would be repeatable and the number content would have the same structure as the record control numbers in the 5XX fields.

Examples:

008/09 b
150 ## $aProjektrechnung (project accounting)
260 ## $aProjekt$0(DE-101b)4115645-6$aKostenrechnung$0(DE-101b)4032592-1 (project + accounting)

008/09 b
150 ## $aKraftfahrzeugkennzeichen (vehicle registration plate)
260 ## $aKraftfahrzeug$0(DE-101b)4073757-3$aKennzeichen$0(DE-101b)4163574-7 (motor vehicle + license plate)

Go to: Table of Contents

2.4 Normalization of numbers and names (BD)

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 standardized, so different algorithms can apply (left orientation, right orientation with leading fill characters, numeric core with or without weighting, etc.). 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 erases the information.

In all three field groups, the suggestion is to 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)>

The content of $y would be according to the normalization rules and algorithms of the cataloging institution.

Examples:

245 00 $aKanton Zürich$nBd. 1$y11
245 00 $aMusik Lexikon$pNachtr.$yna
245 00 $aVermessungstechnik$pMechanische Streckenmessung$nTeil 2.$ymes 12
245 00 $aRegesten der Reichstadt Aachen$nBd. 4$p1366 - 1380$y00000004
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

800 1# $aNegt, Oskar$tSchriften$vBd. 2$y12$0(DE-101b)967682460
810 2# $aAlbertina <Wien>$tAlbertina exhibition …$v410$y0000000410$0(DE-1a)98.011645.7
830 #0 $aAachen British and American studies$vVol. 16$y########16$0(DE-7)55174354-9

250 ## $a1. Aufl.$y11
250 ## $a1. Aufl.$y00000001
250 ## $a1. - 10. Tsd.$y11
250 ## $aVersion 1.1.7$y11 11 17
250 ## $aOrig.-Ausg.$yor
250 ## $aOrig.-Ausg., vollst. Taschenbuchausg., 1. Aufl$y1
250 ## $aUngekürzte Lizenzausg.$yunl
250 ## $aFrankfurter Ausg.$bhrsg. von Luzius Keller$yfra
250 ## $aNew rev. ed$ynere
250 ## $aVersion November 2006$y42006 211
250 ## $aStand: 1. Oktober 2005$y2005-10-01

Go to: Table of Contents

2.5 Codes for record levels of multivolume monographs and series (BD)

The German record encoding model also requires additional information concerning the exact level of records related to multivolume works and explicit indication of whether the 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 used in acquisition functions, while the single volume records are needed 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 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 works.

A coded position needs to be defined where the following values can be indicated:

Monographic series set records are encoded as serial in bibliographic level and the accompanying Continuing Resource 008/21 has a code for identification of a monographic series. Multivolume monograph set records are encoded as monographic in the bibliographic level, and there is no 008 location appropriate for a type code. The other two designations are difficult to place in any of the coded data fields for monographs.

Go to: Table of Contents

2.6 Add indication of paper acidity (BD, HD)

The MAB community requests an explicit indication of the fact that a paper item is non-acid. This code can serve as a basis for preservation purposes. If the item is acid free, then the indication could be in an additional character position in the 007 fields (for physical items that could be on paper). If the item has been deacidified, or if it is planned to be deacidified, the information is copy specific, and the information can be specified in MARC field 583 (Action Note) in the MARC Bibliographic and MARC Holdings formats.

One issue is whether the copies of an item are universally acid free or partially, as some publishers print the first XX on acid free paper and the rest on acid paper. The publisher sometimes makes available both, with different ISBNs on the two versions. In both cases separate records are not made for the acid and the acid free version so acidity is often copy specific on the bibliographic record.

The materials that could be paper so would require the acidity indicator are (in 007 terms) maps, globes, tactile materials, nonprojected graphics, kits?, notated music, and texts. Text is perhaps the the most critical of these.

Use of 007:

The information might be encoded in the next free position of the relevant 007 fields: 007/08 for Maps, 007/10 for Tactile material, 007/06 for Nonprojected graphic, 007/02 for Kit, 007/02 for Notated music, and 007/02 for Text). If the 007 is included in the bibliographic record this would mean that all copies of the item are printed on acid free paper as the 007 cannot be made copy specific. If it were in a Holdings record, it could be made copy specific.

The coding in the new position "Paper acidity" would be:

  a Acid-free paper
  b Not acid-free paper
  n Not applicable
  u Unspecified
  | No attempt to code

Examples:

007 taa [Item is text, regular print, and acid-free]
007 aj#canbab
[Item is a map (in general and in detail), multicolored, paper, not a reproduction, a photocopy, with positive aspect, and not acid-free]

007 qua [Item is notated music, SMD is unknown, and acid-free]

Use of 583:

Indicate acidity status in 583 $l (Status). Field 583 (Action Note) could be used in either the Bibliographic or Holdings formats and would enable the designation to be copy specific.

583 ## $lalkaline paper$2stmanf$5xxx
583 ## $lacidic paper$2stmanf$5xxx
583 ## $amass deacifdified$2stmanf$5xxx
583 ## $awill mass deacifdify$2stmanf$5xxx
583 ## $ldeacifdified$5xxx

Use of 852:

Another option that enables copy specific specification and inclusion in both the Bibliographic and Holdings formats is the 852 $q (Piece physical condition). The 583 Action field would still be used for preservation action information.

852 ## $a[location information]$qalkaline paper
852 ## $a[location information]$qacidic paper

Go to: Table of Contents

2.7 Add new codes for nature of contents for books (BD)

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. Two additional codes are needed:

1 Progress report – typically a single volume publication about developments in
the technical or economical areas (Fortschrittsbericht)
2 Offprint – a publication that originally was published as an article in a book or a serial and that is also issued separately and independently (Sonderdruck)

Examples:

008/24 1
245 00 $aZweiter Fortschrittsbericht wirtschaftswissenschaftlicher Forschungsinstitute über die wirtschaftliche Entwicklung in Ostdeutschland$cDeutsches Institut für Wirtschaftsforschung (DIW) ...
260 ## $aKiel$bInst. für Weltwirtschaft an der Univ. Kiel$c2003
710 2# $aDeutsches Institut für Wirtschaftsforschung <Berlin>$0(DE-101b)37419-2

008/24 1
245 00 $aPerspectives for Germany$bour strategy for sustainable development ; progress report 2004$c[The Federal Government. Publ. by Press and Information Office of the Federal Government]
260 ## $aBerlin$bPress and Information Office of the Federal Government$c2005
260 ## $aRostock$bPubl.-Versand der Bundesregierung$c2005
710 2# $aDeutschland$bBundesregierung$0(DE-101b)2117038-1

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

Go to: Table of Contents

2.8 Add new codes for nature of contents for serials (BD)

The MAB community uses codes for the nature of contents in a similar way as they are defined in MARC in field 008/25-27 (Nature of contents) for Continuing Resources. Three additional codes that are used in the German Serials' Database (Zeitschriftendatenbank, ZDB) could not be identified in MARC.

The 3 new coded values would be (including statistical figures for unique serial titles in the ZDB):

3 Announcements – serial that announces laws and regulations of government bodies, or dates of local events such as meetings, auctions, and courses. This would include newspapers. (Anzeigenblatt) (2,237 in ZDB)

This value overlaps with the existing value 1 - legislation which includes “full or partial texts of legislative bodies or texts of rules and regulations issued by executive and administrative agencies”

4 Magazine – newsstand magazine that is usually published weekly or twice a month and whose scope in more or less entertaining (but excluding monographic series of , e.g., science fiction, romance, and western stories, etc.) (Magazin) (2,982 in ZDB)
5 Reports – a serialized publication of multiple scientific reports (Report-Serie) (2,319 in ZDB)

Examples:

008/25 3
245 00 $aAmtliches Anzeigenblatt für die Stadt Langenberg$cHrsg.: Bürgermeistereiamt
260 ## $aVelbert$c1923-1924
710 2# $aLangenberg <Wuppertal>$0(DE-101b)2001809-5

008/25 3
245 00 $aThe Sydney gazette and New South Wales advertiser
260 ## $aSydney$c1803-1840
710 #2 $aSydney

008/25 4
245 00 $aNewsweek
260 ## $aNew York, NY$bNewsweek$c1933

008/25 4
245 00 $aVogue$ced.-in-chief Grace Mirabella
260 ## $aBoulder, Colo.$bCondé-Nast Publ.$c1892 -

008/25 5
110 2# $aInstitut für Forsttechnik <Wien>
245 00 $aJahresbericht / Institut für Forsttechnik, Universität für Bodenkultur
260 $aWien$c1991 -

008/25 5
110 2# $aPacific Biological Station <Nanaimo, British Columbia>$0(DE-101b)140257-2
245 00 $aProgress reports of the Pacific Biological Station$cFisheries Research Board of Canada
260 ## $aPrince Rupert, BC$c1935-1962
710 2# $aPacific Fisheries Experimental Station <Prince Rupert, British Columbia>$0(DE-101b)5197476-9

Go to: Table of Contents

2.9 Add subfield for canceled or invalid National Bibliography Number in field 015 (BD)

The German National library produces a National Bibliography and assigns a National Bibliography Number (NBN) to each item. That number is entered in the record for the item in field 015 (National Bibliography Number).

In two circumstances a previously assigned NBN is canceled and made invalid, but they need to continue to be carried in the MARC record marked as cancelled, similarly to the cancelled or invalid numbers in the $z subfield of 016 (National Bibliographic Agency Control Number), 020 (ISBN), 022 (ISSN), and 024 (Other Standard Identifier) fields.

(1) 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) 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.)

For both cases a $z for a "Canceled/invalid national bibliography number" seems to be appropriate. A distinction between upgrade and correction is not needed.

  $z - Canceled/invalid number (R)

The new $z subfield in 015 would be repeatable and the number content would have the same structure as $a.

Examples:

015 ## $a06,A29,1122$z05,N51,1204
015 ## $a06,A44,1607$z06,A28,2368
015 ## $a06,A29,0382$z05,A21,0597$z04,N48,0463

Go to: Table of Contents

2.10 Add subfield for specification of assigning institution for subject headings (BD)

According to the German Rules for Subject Cataloging (Regeln für den Schlagwortkatalog, RSWK) subject headings are organized as sequences of subject terms and phrases. In the MARC 21 bibliographic record these terms and phrases are each carried in a separate subject field and then linked and sequenced using subfield $8 (Field link and sequence number) to form a subject heading. Notes and remarks on a subject headings can be given in multiple fields 500 (General note), linked to the appropriate heading parts by using $8 again.

Example:

650 07 $aBibliothek$0(DE-101b)4006439-6$2swd$5DE-101b$81.2
650 07 $aElektronische Publikation$0(DE-101b)4514269-5$2swd$5DE-101b$81.3
650 07 $aLangzeitarchivierung$0(DE-101b)4787040-0$2swd$5DE-101b$81.4
650 07 $aArchiv$0(DE-101b)4002859-8$2swd$5DE-101b$82.2
650 07 $aElektronische Publikation$0(DE-101b)4514269-5$2swd$5DE-101b$82.3
650 07 $aLangzeitarchivierung$0(DE-101b)4787040-0$2swd$5DE-101b$82.4
651 #7 $aDeutschland$0(DE-101b)4011882-4$2swd$5DE-101b$81.1
651 #7 $aDeutschland$0(DE-101b)4011882-4$2swd$5DE-101b$82.1
655 #7 $aZeitschrift$2swd$5DE-101b$81.5
655 #7 $aOnline-Publikation$2swd$5DE-101b$81.6
655 #7 $aZeitschrift$2swd$5DE-101b$82.5
655 #7 $aOnline-Publikation$2swd$5DE-101b$82.6

For subject headings:

Deutschland / Bibliothek / Elektronische Publikation / Langzeitarchivierung / Zeitschrift / Online-Publikation

Deutschland / Archiv / Elektronische Publikation / Langzeitarchivierung / Zeitschrift / Online-Publikation

There is a need for to designate that the DNB has applied a subject term or phrase to a record, and ideally which other institution might have applied a specific subject term or phrase. The proposal is to define subfield $5 "Institution to which field applies" in the fields of the 6XX range and adjust the description of the $5 to indicate the assigning institution. Subfield $5 at the moment is described thus: "contains the MARC code of the institution or organization that holds the copy to which the data in the field applies. Data in the field may not apply to the universal description of the item, or may apply universally to the item but be of interest to the location cited."

  $5 - Institution to which field applies (R)

Go to: Table of Contents

2.11 Add indicator for type of uncontrolled keywords in field 653 (BD)

The MAB community distinguishes uncontrolled subject names and terms by type: topical, geographic, personal name, corporate name. By distinguishing between the categories more specific keyword indices can be built up, and the precision of searching can be improved.

Since they will make a separate 653 for each term or name, the second indicator could be used for this distinction. Current users of the field could do the same, or 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 - Geographic name>
<2 - Personal name>
<3 - Corporate name>

Subfield Codes
$a - Uncontrolled term (R)
$6 - Linkage (NR)
$8 - Field link and sequence number (R)

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 #1 $aDublin
653 #2 $aJoyce

245 00 $aQuestions and answers on the needs of children and UNICEF
653 #0 $aChildren
653 #3 $aUNICEF

Go to: Table of Contents

2.12 Add field for replacement record information (BD)

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 882 would be non-repeatable and structured like the Authority format field 682. The subfield $0 would have the same content structure as the record control numbers field 035$a: (MARC org code)1234567.

882 - REPLACEMENT RECORD INFORMATION (NR)

Indicators - Both indicators are undefined and contain blanks.

Subfield Codes
$a - Replacement title (R)
$i - Explanatory text (R)
$0 - Replacement record control number (R)
$6 - Linkage (NR)
$8 - Field link and sequence number (R)

Examples:

882 ## $aColonial-Post$0(GyBeDBIZ)952932-9
882 ## $aUnited States: Statistical abstract of the United States$ibibliographic record deleted, to be replaced by:$0(GyBeDBIZ)39-5

Go to: Table of Contents

2.13 Record Control Numbers in field 682 Deleted Heading Information (AD)

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.

  $0 - Replacement Record Control Number (NR)

The new $0 subfield in field 682 would be repeatable and have the same content structure as the record control numbers field 035$a: (MARC org code)1234567.

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 record control number (R)>
$6 - Linkage (NR)
$8 - Field link and sequence number (R)

Example:

LDR/5-6 xz
016 7# $a108585077$2(DE-101b)
100 1# $aHohenberger, Werner Max
682 ## $aHohenberger, Werner$0(DE-101b)132213052

Go to: Table of Contents

2.14 Add a new field for geographic name added entry (BD)

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.

New 751 field:

One way to satisfy this need is to add a new field in the 7XX range parallel to the 651 field, with additional codes defined for the relator code.

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 - 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 for:

  evp - event place
  pup - publication place
  dbp - distribution place
  uvp - university place

Use of 752:

The field 752 (Added Entry -- Hierarchical place name) was reviewed but the German colleagues thought that its hierarchical approach does not seem to be useful for the one-level flat information of the German authority file. Consideration should be given to whether the use of the 752 with only one stage in the hierarchy would be acceptable, in which case it might be used, with the addition of the $e and $4 for relator codes, instead of defining a new field. The examples below give the information both ways.

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$2gkd$4evp
or
752 ## $dSenftenberg <Schwarze Elster>$0(DE-101b)115478-3$2gkd$4evp

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
or
752 ## $dNü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
or
752 ## $dRoma$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
or
752 ## $dFrankfurt <Main>$0(DE-101b)2028282-5$2gkd$4uvp

Go to: Table of Contents

2.15 Add subfield for former call numbers (BD, HD)

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 special note (or an appropriate existing note) or in a new subfield in either field 852 (Location) or 084 (Other Classification Number). Subfields $d, $o, $r, $u, $v, $w are currently unused in the 852 field.

Use of 852:

Example with $d defined as Former shelving location:

852 8# $cN.Mus.ms. 2234$dMus.ms.pr. XII/911$d13.492

Example with $x (Nonpublic note) for former shelving location:

852 8# $xFormer shelving location: Mus.ms.pr. XII/911
852 8# $xFormer shelving location: 13.492

Use of 084:

Example using 084 with $c defined for former shelving location:

084 ## $aN.Mus.ms. 2234$cMus.ms.pr. XII/911$c13.492

Go to: Table of Contents

2.16 Add field or subfield for normalized form of dates of publication and/or sequential designation (BD)

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, e.g. for ILL purposes. In the German systems it can have combinations and parallel designations and the same field tells whether a serial is still published (008/06 information). 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 match algorithms.

Use of 362 or NEW field:

Either a new field or new subfields for the existing 362 field would be needed. The data elements that are proposed are the following.

Indicator - State of issuance
This indicator is related to the hyphen in the 362. (This information is in 008/06 for the serial but here it needs to indicate when items are not issued in sequential groups but individually.)
# - Not specified
0 - Ceased
1 - Continuing

Subfield Codes:
Starting designation
$a - Parallel numbering
$b - Volume designation
$c - Volume number
$d - Issue number
$e - Year of issuance, or year of coverage
$f - Year of issuance (if different from coverage)
$g - Month
$h - Day
$i - Starting designation note

Ending designation
$k - Volume number
$l - Issue number
$m - Year of issuance, or year of coverage
$n - Year of issuance (if different from coverage)
$o - Month
$p - Day
$q - Ending designation note

Use of 863:

In MARC 21, field 863 has subfields for this type of parsing of the serial designations, in even greater detail than the examples below need. It can indicate gaps in publication and third and fourth levels of enumeration and chronology. Field 863 has not, however, been used for this purpose so a technique for designating starting and ending information would be needed. For illustrative purposes, in the following examples the $8 is used to link and sequence (start=.1, end=.2) the entries. Likewise the $x note field has been used to indicate that the information in the field the publishing record of the serial, not any specific institution’s holdings. Proper techniques would need to be worked out if the 863 is used.

Examples:

245 00 $aJournal of polymer science$ced. board W. T. Astbury [u.a.]
785 00 $tJournal of polymer science / A$w(GyBeDBIZ)221062-9
785 00 $tJournal of polymer science / B$w(GyBeDBIZ)221073-3
362 0# $a1.1946 - 62.1962
NEW 0# $c1$e1946$k62$m1962
or
863 #0$a1$i1946$81.1$xpublished
863 #0$a62$i1962$81.2$xpublished

130 ## $aJournal of polymer science / A
245 00 $aJournal of polymer science$nPart A,$pGeneral papers
780 00 $tJournal of polymer science$w(GyBeDBIZ)3122-7
785 00 $tJournal of polymer science / A2$w(GyBeDBIZ)221064-2
362 0# $a1.1963 - 3.1965
NEW 0# $c1$e1963$k3$m1965
or
863 #0$a1$i1963$81.1$xpublished
863 #0$a3$i1965$81.2$xpublished

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(GyBeDBIZ)221062-9
785 00 $tJournal of polymer science / Polymer physics edition$w(GyBeDBIZ)220649-3
362 0# $a4.1966 - 10.1972,9
NEW 0# $c4$e1966$k10$l9$m1972
or
863 #0$a4$b1$i1966$81.1$xpublished
863 #0$a10$b9$i1972$81.2$xpublished

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(GyBeDBIZ)221064-2
785 00 $tJournal of polymer science / B$w(GyBeDBIZ)233082-9
362 0# $a10.1972,10 - 24.1986,1
NEW 0# $c10$d10$e1972$k24$l1$m1986
or
863 #0$a10$b10$i1972$81.1$xpublished
863 #0$a24$b1$i1986$81.2$xpublished

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(GyBeDBIZ)220649-3
362 0# $a24.1986,2 -
NEW 1# $c24$d2$e1986
or
863 #0$a24$b2$i1986$81.1$xpublished

362 0# $aNachgewiesen 2004 -
NEW 1# $e2004
or
863 #0 $i2004$81.1$xpublished

362 0# $a15.2005,2 -
NEW 1# $c15$d2$e2005
or
863 #0 $a15$b2$i2005$81.1$xpublished

362 0# $a1949(1951); 1956(1959) nachgewiesen
NEW 0# $e1949$f1951 [ceased?]
NEW 0# $e1956$f1959 [ceased?]
or
863 #0 $i1949$v1951$81$xpublished
863 #0 $i1956$v1959$82$xpublished

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.
NEW 0# $c15$e1904$gApr$h2$k44$m1933$oApr$p29
or
863 #0 $a15$i1904$j04$k2$81.1$xpublished
863 #0 $a44$i2005$j04$k29$81.2$xpublished

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)
NEW 0# $bWahlper.$c2$e1950/54$f1955$k11$m1990/95$n1996
or
853 ##$aWahlper.$81$xpublished
863 #0 $a2$i1950/54$v1955$81.1$xpublished
863 #0 $a11$i1990/95$v1996$81.2$xpublished

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
NEW 0# $c1$e1964$k19$l5$m1982
or
863 #0 $a1$b1$i1964$81.1$xpublished
863 #0 $a19$b5$i1982$81.2$xpublished

Go to: Table of Contents


HOME >> MARC Development >> Discussion Paper List

The Library of Congress >> Especially for Librarians and Archivists >> Standards
( 12/21/2010 )
Legal | External Link Disclaimer Contact Us