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 21, 2012
REVISED:
NAME: Identifying Titles Related to the Entity Represented by the Authority Record in the MARC 21 Authority Format
SOURCE: Program for Cooperative Cataloging
SUMMARY: This paper proposes a new field in the MARC 21 Authority Format for making titles related to the entity represented by the authority record machine-actionable.
KEYWORDS: Relation of title to entity (AD); Field 670 (AD); Field 672 (AD)
RELATED: 2012-DP01
STATUS/COMMENTS:
05/21/12 – Made available to the MARC community for discussion.
06/23/12 – Results of MARC Advisory Committee discussion: Withdrawn. Confusion arose over the amount of detail and complexity of this field vs. the original intent (less complex). Discussion questioned whether the authors for name/titles needed to also be expressed and whether the titles and other elements needed to be parsed as they are in other fields. Straw votes indicated a slight majority did not see the additions of names (for name/titles) necessary. A straw vote favored simple coding to rich coding. A straw vote also strongly supported removing the subject aspect from the field. The initial discussion of the proposal raised considerations that the PCC representative felt were too many and too important to be dealt with at the meeting. He therefore decided to withdraw the proposal. However, the paper was discussed so as to provide guidance for the subsequent paper. Further suggestions for a reworked proposal: add $w (Bibliographic record control number); consider using two fields 672 and 673 to make clear the distinction between titles related to the entity and titles not related to the entity.
07/25/12 - Results of LC/LAC/BL review - Agreed with the MARBI decision.
Field 670 (Source Data Found) in the MARC 21 Authority Format contains citations of sources in which information related to the entity represented by the authority record was found. The 670 field contains two principal segments: an identification of the source (subfield $a), and information found in the source (subfield $b).
670 ## $a The art of the table, 1962.
670 ## $a Wines of the Graves, 1988: $b t.p. (Pamela Vandyke Price)
670 ## $a Hertel, J. M. Concerto for trumpet ... [SR] p1976 (a.e.) $b labels (Bo Nilsson, trumpet) container (b. 1940, Stockholm)
670 ## $a Optimization and regulation for computational inverse problems and applications, c2011: $b t.p. (Anatoly G. Yagola) t.p. verso (Prof. Dr. Anatoly G. Yagola, Dept. of Physics, Lomonosov Moscow State Univ.)
The 670 field was designed as a holder for the raw information used in the construction of the authority record or of potential use to future users of the record. In recent years, application programs have begun to mine information in the 670 field for other purposes. For example, a program loading authority records may attempt cautiously to reassign headings in bibliographic records based on a comparison of titles in bibliographic records to titles in subfield $a of the 670 field. While this is made difficult because subfield $a of the 670 field can contain many kinds of information in addition to a title (such as: an identification of the author, the format of the resource, and the date of publication of the resource and/or the date of consultation of the resource), these efforts have seen substantial success, and in general the technique can be described as valid.
Among the pieces of information that may be carried in subfield $b of the 670 field is a listing of additional titles for which the entity represented by the authority record is responsible in some manner.
670 ## $a Phone call to pub., 2/23/88 $b (Ronald Fernandez, also author of Social psychology through literature)
670 ## $a E-mail from Dr. Martin, 2 Sept. 2011 $b (confirms authorship of various reports emanating from ETSU, TRRL, Financial Times, Dept. of Energy; also authored doctoral thesis "The mechanical behaviour of carbon fibre composites at high rates of loading")
670 ## $a Phone call to M.Johnstone, Routledge, 12-10-99 $b (John Andrew Forth; also wrote Pathways through unemployment, Rents and work incentives)
In some cases, the 670 may conversely identify items for which an entity has no responsibility:
670 ## $a BL AL recd., 11 June 2010 $b (Christine Routledge, born 2 Sept. 1965; is not the author of Kaleidoscope)
This information would be of significant use to a program attempting to reassign headings in bibliographic records, but because it is buried within a free-text field it is not easily made machine-actionable. If this additional information were isolated and so made machine-actionable, a program attempting to judge the headings in bibliographic records should be able to perform its work to even greater effect.
A Task Group of the PCC established to look into the matter considered whether a more elaborate scheme for the subfield coding of the 670 field would allow for titles embedded within the 670 to be identified, without requiring redundant data entry. If for no other reason than the ongoing difficulties that seem to be encountered in the application of even the current simple scheme for the 670 field, the Task Group rejected that idea in favor of a request for a new field, to contain an identification of the titles of items related to the entity represented by the authority record.
This matter was previously made the subject of MARC discussion paper 2012-DP01, discussed at the ALA 2012 Midwinter Meeting in Dallas. The majority of participants agreed upon several points (some of these were clarified in a subsequent e-mail exchange):
The matter of including periodical citations was left unresolved; there was some discussion that DOI could fit into subfield $0. The input and maintenance of the field was controversial. It was hypothesized the catalogers would input the field manually with the help of their systems.
Define a new field in the MARC21 Format for Authority Data. The tag of 672 is suggested here, but another available tag in the 671-674 block may be chosen instead.
FIELD DEFINITION AND SCOPE
This field may be used to list titles that are related in some way to the entity represented by the authority record, and titles that are not related in some way to the entity represented by the authority record but whose status may not be clear. The term relationship used here is intended to be as broad as possible; for example, there is no implication that the authority 1XX field will appear in the 1XX field of a bibliographic record containing the title.
This field is designed to assist programs and operators in selecting from amongst a set of candidate headings, and not to provide the final answer to questions of authorship. For example, the authority record for the William Shakespeare who lived from 1564 to 1616 could easily contain a 672 field containing the title Sir John Oldcastle (a play included in the Third Folio, but not by Shakespeare); such a field would help a program determine the proper action when it encounters a bibliographic record for some version of that work with a heading of just "Shakespeare, William" and no dates.
This field is designed primarily to capture in machine-actionable form any information regarding associated titles that is discovered during the normal course of research regarding the entity represented by the authority record. When a resource consulted indicates that the entity represented by the authority record is, or is not, related to one or more titles, that information may be placed into the 672 field instead of (or in addition to) being included as part of subfield $b of the 670 field.
The list of titles provided in 672 fields is not intended to be exhaustive, but simply to reflect those titles encountered during the course of other research. No effort should be put into determining whether a given title represents a work, an expression or a manifestation; the 672 field should contain whatever title is given in the source of information. This field is not intended to be populated by automated mining of existing bibliographic data; titles cited in this field should be those for which some authority may reasonably be asserted.
GUIDELINES FOR APPLYING CONTENT DESIGNATION
• Indicators
First indicator - Relation of entity to title
This indicator shows whether the entity represented by the authority record is related to the title. If a more detailed specification of the relationship between the entity represented by the authority record and the title is wanted, codes representing the relationship may be added to one or more instances of subfield $4.
Second indicator - Nonfiling characters
Number of character positions associated with a definite or indefinite article (e.g., Le, An) at the beginning of a title that are disregarded in sorting and filing processes.
0 - No nonfiling characters
No initial article character positions are disregarded. Diacritical marks or special characters at the beginning of a title field that does not begin with an initial article are not counted as nonfiling characters. An initial definite or indefinite article may be deleted in the formulation of the title field. If the initial article is retained but is not to be disregarded in sorting filing processes, value 0 is used.1-9 - Number of nonfiling characters
Title begins with a definite or indefinite article that is disregarded in sorting and filing processes. Any diacritical mark, space or mark of punctuation associated with the article and any space or mark of punctuation preceding the first filing character after the article is included in the count of nonfiling characters. Any diacritic, however, associated with the first filing character is not included in the count of nonfiling characters.
• Subfield codes
$0 - Authority record control number
See description of this subfield in Appendix A: Control Subfields.
$6 - Linkage
See description of this subfield in Appendix A: Control Subfields.
$4 - Relator code
MARC code that specifies the relationship between the entity represented by the authority record and the title in the 672 field. More than one relator code may be used (each in its own instance of subfield $4) if the relationship between the entity represented by the authority record and the title has more than one aspect. Code from: MARC Code List for Relators.
100 1# $a Shakespeare, William, $d 1564-1616
672 10 $4 aut $t Sir John Oldcastle
$8 - Field link and sequence number
See description of this subfield in Appendix A: Control Subfields.
• Examples
670 ## $a BerkeleyResearch web site, April 14, 2012 $b (David Stern, emeritus professor of education, University of California, Berkeley; joined faculty in 1976; research focused on relationship between education and work, and resource allocation in schools)
672 10 $a International perspectives on the school-to-work transition $f 1999
672 10 $a Active learning for students and teachers $f 1997
672 10 $a School to work $b research on programs in the United States $f 1995
672 10 $a School-based enterprise $b productive learning in American high schools $f 1994
672 10 $a Career academies $b partnerships for reconstructing American high schools $f 1992
672 10 $a Market failure in training $f 1991
672 10 $a Adolescence and work $b influences of social structure, labor markets and culture $f 1989
[In this example, the source of the titles listed in the 672 fields (the web site) is not identified.]
670 ## $a Phone call to pub., 2/23/88 $b (Ronald Fernandez, also author of Social psychology through literature)
672 10 $a Social psychology through literature
[In this example, the 670 field shows the source of the 672 field.]
670 ## $a Phone call to M.Johnstone, Routledge, 12-10-99 $b (John Andrew Forth; also wrote Pathways through unemployment, Rents and work incentives)
672 10 $a Pathways through unemployment
672 10 $a Rents and work incentives
672 14 $a The business case for Equal Opportunities
672 10 $a Family-friendly working arrangements in Britain 1996
[In this example, the 670 field shows the source of some of the 672 fields.]
670 ## $a BL AL recd., 11 June 2010 $b (Christine Routledge, born 2 Sept. 1965; is not the author of Kaleidoscope)
672 10 $a Johnny
672 00 $a Kaleidoscope
[In this example, the 670 field shows the source of one of the 672 fields—a title not related to the entity represented by the authority record.]
100 1# $a Richardson, Frances, $b 1952-
670 ## $a Hanes - eglwysi Capel Curig, 2010: $b t.p. (Frances Richardson)
670 ## $a NLW AL, rec'd 3 Jan. 2012 $b (full name: Frances Ann Richardson, b. 19 May 1952 ; not the author of To nourish humanity or Sir Eglamour of Artois)
672 00 $a To nourish humanity
672 00 $a Sir Eglamour of Artois
100 1# $a Williams, Cathy, $d 1953-
670 ## $a Quality time analysis guide, year 2, 2009-2010, 2009: $b cover (Cathy Williams, Office of Innovation, Support, and Alternative Education, Okla. State Dept. of Education)
670 ## $a E-mail from author, Feb. 16, 2012: $b (Cathy J. Williams, b. July 1953; not author of Fifty years of caring and sharing; 99 easy-to-use speech and language activities; Mathcounts)
672 00 $a Fifty years of caring and sharing
672 00 $a 99 easy-to-use speech and language activities
672 00 $a Mathcounts
110 2# $a Students Publishing Company (Northwestern University)
670 ## $a Northwestern University video yearbook 1990-1991: $b credits (Students Publishing Company, Inc.)
670 ## $a Daily Northwestern web site, Mar. 29, 2012 $b (Students Publishing Company, publisher of the Daily Northwestern, the student newspaper of Northwestern University)
672 10 $a Daily Northwestern
HOME >> MARC Development >> Proposals List
| The Library of Congress >> Especially for Librarians and Archivists >> Standards ( 07/25/2012 ) |
Legal | External Link Disclaimer | Contact Us |