Machine-Readable Bibliographic Information Committee
Saturday, 10 January 1998, a.m. and Sunday, 11 January 1998, p.m.

This report is in order of proposal number and then discussion paper number, followed by a business meeting report. For discussion order, see the agenda at There is lots of other information, as well as the full text of proposals and discussion papers, on the same site.

Proposal 98-1 addressed the use of field 210 for abbreviated titles other than the abbreviated key title. The proposal came from the National Library of Medicine. CONSER has no problems with the potential conflicts between 210 and 246 for variant titles. This field should be used for abbreviations for the purpose of indexing or identification, not necessarily for variant titles that happen to be abbreviations. The assumption is that title indexing will find the title in either field. The proposal was approved with a minor change in the definition.

Proposal 98-2 would define 541, 561 and 562 in the Holdings Format. These are note fields and used for notes that can be copy-specific. The linkage of such notes to specific copies is much clearer if the fields are in the holdings record(s). There was a general discussion of embedding description in holdings or of embedding holdings in bibliographic records. Defining the fields in the Holdings Format was approved. The proposal also addressed the definition of "h" as a $8 link code in the Bibliographic Format. This issue will perhaps come back as a proposal to make 541, 561 and 562 obsolete in Bib or to define "h" as a link code.

Proposal 98-3 expands the use of 028 for publisher numbers. It is currently used for sound recordings, videorecordings, and printed music. Publishers are using similar numbers on other music. The proposal was approved with minor changes in the definition and in the name of value 3 ("Other music number") in indicator 1. According to the representative from the Music Library Association, the inclusion of prefixes in numbers is based on cataloger judgment.

Proposal 98-4 would move the coded dates fixed fields in the Community Information Format from 004 to 046, with new subfields being defined for action date, purge date, beginning date of event or program, and ending date of event or program. This is being done to harmonize CIF with Bib. Discussion paper 106 also addressed expanding 046 but it was determined that this expansion would be approved for CIF and that further expansion would follow. As in DP 106, these dates might be used for exhibitions or conferences.

Proposal 98-5 defined further subfields for Universal Decimal Classification numbers. They will also be defined in the Community Information Format , and later extended to the Authorities Format. The proposal was approved.

Proposal 98-6 defined "s" in 008 character positions for electronic carriers. This will allow the main coding of the item to reflect the content but still allow for coding of the physical carrier (e.g. electronic atlases would be coded as cartographic material on a computer carrier). Since the 008s for various materials vary, there were several options for coding the "s" with option 1 representing the least disruption, as well as the most agreement between formats, and being approved. There was also some discussion of what "original" meant.

Discussion paper 104 would define an 007 for tactile materials (braille, etc.). More discussion needs to be undertaken about internationalization and multilinguality, but there was general support for the development of a tactile 007.

Discussion paper 105 presented solutions for dealing with interactive multimedia Reading Programs that relate to published reading materials. The MicroLIF Committee suggested a single note (526?) and LC counter-suggested that the information would fit more or less into established fields. MicroLIF would probably use a single note regardless and there was support for keeping the information together. This field could also be used for other related education materials (e.g. Janson slide sets). A proposal (or revised discussion paper) will be issued using one field for this data and generalizing it beyond Reading Programs.

Discussion paper 106 presented coding for incorrect publication dates, based on errors in the publication. Some of these are quite simple (typo in the publication or those published at the end of the year with the next year's date) and can be dealt with by a new code in the 008/06. Others are more complex (BCE dates, incorrect date ranges, and special calendars). Another discussion paper will be forthcoming on expansion of 046 to handle the complex examples. Other dates that might be used in expansions of the 008/06 or 046 include exhibition or conference dates that do not match the publication date.

Discussion paper 107 dealt with defining 856 in the Authorities Format. While there was much support for the sort of linking that this would allow, there was also considerable concern about the appropriateness. It would be a shortcut for making a Community Information Format record for the person or body in the heading. The URL is not authorized and is volatile. There are however lots of connections between electronic resources and authority records. As an example, a project at the Harvard Graduate School of Design was described; the project includes links from an image to the architect data to the building data, etc.

LC reported that the new bibliographic update has been published. The next bib update will be a new cumulated edition and will include USMARC/CanMARC harmonization. The MARC web has a status page. A new version of the relator codes has been published. A new version of the geographic area codes is underway. The GACs for the former Soviet Union are being revised. Preservation terms to be used in 583 are available on the web. A new version of the USMARC (aka NUC) codes will be available soon and it will be in a database on the web (Lexico is the software used). Guidelines for cataloging electronic resources and for distinguishing cartographic materials on computer file carriers are available. The conversion program for a MARC DTD has been completed. MARC Maker and Breaker are to be updated for easier use. Future MARBI documentation will be available only on the web and more internal numbering will be used to facilitate discussion. A new proposal or discussion paper on non-filing characters and authority records will be prepared for Annual 1998. The British Library is implementing a new integrated library system in 1999. UKMARC will be mounted as is but harmonization will commence after the new system has stabilized (e.g. blank rather than zero for indicators).

There are three task forces at work. The East Asian character set group is looking at conflicts between the USMARC character set and Unicode. The Unicode Task Force continues its work and will report at Annual. MARBI affiliates are being added to the CC:DA Task Force on Metadata (see the separate report).