San Antonio, Texas
January 20-22, 1996

MARBI and the USMARC Advisory Group met in three sessions during the ALA-Midwinter. Priscilla Caplan (Harvard University) chaired the sessions.

Several discussions were of interest to music librarians. The first approved use of a linking code to mark fields comes with the approval of Proposal 95-6. Proposal 96-4 presents another official use of the linking code. Discussion Paper No. 93 contains a list of fields that must be altered in order to have the CAN/MARC and USMARC formats in agreement. Several fields affected are in the music format. Proposals 96-2 and 96-3 are of interest as well: Proposal 96-2 because of the uniqueness of a "generic" author concept and Proposal 96-3 because of the number of systems and users affected by the change.

The Library of Congress reported that the authority and classification updates are now available, with changes through June 1995. The next bibliographic and community information updates will be out soon and will include changes through January 1996. Format integration is proceeding on schedule at the Library of Congress with implementation set for March 1. Catalogers will begin submitting records that utilize the final phase of format integration on March 15.

Proposals

95-4: Merger of the 27X Fields in the Community Information Format (Approved)

This paper proposed the merging of fields 271 (Additional Address) and 270 (Address Associated with Title) with field 270 (Primary Address) as well as the defining of two new subfields, $v Hours and $z Public note. In addition, the first indicator was proposed to indicate address level information and, as an amendment to the proposal, the second indicator was defined to indicate type of address. The proposal was approved as amended.

95-6: Linking C ode for Reproduction Information in the USMARC Bibliographic Format (Approved)

This proposal called for the use of a code to mark fields pertaining to a reproduction that are added to a record for an original when creating the record for the reproduction. Although lengthy discussion ensued regarding the desire of some to attach more than one reproduction to the record for the original, the challenges presented when attempting to communicate holdings information when multiple reproductions are attached to an original led the group to disallow the communication of more than one reproduction per record. The proposal was approved with one change, that being that there be no prescribed order of numeric subfields except for $6.

96-1: Changes t o Field 856 (Electronic Location and Access) in the USMARC Formats (Defeated)

The first of two proposed changes in this paper suggested the addition of first indicator (Access Method) value 8 for Other, to be used when a Uniform Resource Locator (URL) is recorded in subfield $u. The second change proposed was a redefinition of subfield $q (File transfer mode) to File format type. Both changes were viewed as unnecessary and the proposal was defeated.

96-2: Define a Generic Author Field in the Bibliographic, Authority, Classification, and Community Information Formats (Approved)

This paper proposed defining a new, repeatable field for names of authors not necessarily formulated according to cataloging rules or contained in an authority file or list. The group approved the new 720 field (Uncontrolled name) and the use of the first indicator (Type of name).

96-3: Changes t o Personal Name First Indicator Values in the Bibliographic, Authorities, Classification, and Community Information Formats (Approved)

In an effort to facilitate the sharing of authority records with the British Library under the cooperative NACO program, this paper proposed making obsolete value 2 (Multiple surname) in the first indicator (Type of personal name entry element) of the X00 (Personal Name) fields and renaming value 1 (Single Surname) to "Surname." The proposal was approved with the understanding that the Library of Congress will be able, by working with the utilities, to change all value 2 indicators for their entire authority file.

96-4: Defining a Constituent Unit Entry Field in the USMARC Bibliographic Format (Approved)

This paper proposed defining a constituent unit as a bibliographic item that is a part of another item and which may be physically separate from the parent item. The field tag approved was 774. In addition, a link code (c) was approved for use with subfield $8.

96-5: Enhanceme nt to Field 007 in the Community Information Format (Approved)

This proposal suggested defining a new character position (/10) for handicapped parking information in field 007. The proposal was approved as written with the stipulation that if heights defining "high clearance" are prescribed they be included in the character position's description.

96-6: Definitio n of Existing Bibliographic Data Elements in the Community Information Format (Approved)

This paper proposed defining field 658 (Index Term-Curriculum Objective) and field 856 (Electronic Location and Access). These fields were approved without discussion. Also approved was a new across-format adoption procedure for use in cases when no changes to the elements are required. The procedure involves a posting of the proposal on USMARC-L for a period of six weeks. If no indications of negative impact are received, the proposed change will move through the normal proposal process.

Discussion Papers

DP 91: Machine Generation Flag in USMARC Authority Records

This paper presented options for flagging USMARC authority records that were originally generated by machine. The group was unable to answer basic questions regarding this flag such as what function the flag would serve and whether this information needed to be communicated or if it was only needed locally. It will be referred back to the Cooperative Cataloging Council, its source, for clarification.

DP 92: Change in Definition of Computer File in Leader/06 (Type of record) in the USMARC Bibliographic Format

This paper presented issues on coding MARC records for computer files in Leader/06. Discussed was how Leader/06 is currently being used and whether or not it would be possible to define code "m" for executable software only. The concept of coding for content versus carrier was briefly touched upon. The discussion was to continue at the summer meeting.

DP 93: CAN/MARC Changes for MARC Format Alignment

This paper listed the changes that the CAN/MARC users have suggested be made to USMARC to facilitate the alignment of the bibliographic and authority formats. Utilities and local vendors have been asked to provide impact statements to the Library of Congress by April 15. Full alignment with CAN/MARC and UKMARC is expected to be completed by the end of 1998 with implementation of CAN/MARC alignment occurring first. Proposals addressing CAN/MARC alignment are expected at the July 1996 and January 1997 USMARC Advisory Group meetings.

DP 94: Proposed Changes to FTP Label Specifications for Electronic Files of USMARC Records

This paper discussed changes and additional fields deemed necessary for exchange of records in a variety of MARC formats. The deadline for discussion on this paper is the end of February. A proposal is expected at the July meeting.

Submitted by: Karen Little

Chair, Subcommittee on MARC Formats

February 2, 1996

Return to SMF MARBI Report Homepage
Return to Subcommittee on MARC Formats Homepage
Return to BCC 1996 Documents Menu
Return to BCC Historical Documents Menu
Return to BCC Home Page

Last updated February 10, 2000