CC:DA Meeting, Washington, DC
27 June 1998
The good news in this report is that we can now see avenues of approach and alignment for our two bibliographic galaxies, which have up until now been living in uneasy separation. Avenues, in other words, toward nothing less than a grand unification.
In the REUSE project, after clearing away a number of obstacles in the entries and headings departments, as reported by Monika Münnich, there was one remaining roadblock, and that was, and continues to be, the difference in how we handle multiparts of all kinds and whether or how we do analysis. It is a major roadblock, and it has far-reaching ramifications. Which is why OCLC supported a sequel to REUSE, and which is why we are here to talk about it.
I had a dream the other day, a day dream (though I suppose to some it would occur as a nightmare). In this dream, we wake up one morning in Germany to find that the Masters of the Bibliographic Universe have done a universal replacement in our utility databases, substituting every record with an AACR2/USMARC counterpart.
The interesting question is, after this intervention, what effects will we perceive, how will it affect our routine.
With regard to multiparts, leaving everything else aside, the effects are likely to be the following:
We will perceive a general deficit in bibliographic control. Volumes are less well controlled than they used to be. We will miss a considerable amount of bibliographic detail about volumes and parts, which means detail we used to have in our shared records, including persons related to volumes, edition details, dates, physical descriptions, series statements. As life goes on, we realize that this deficit has at least five major consequences in day-to-day work:
We can, however, and this is good news again from the REUSE project, dream a much nicer dream, and one that need not remain a dream. Rather than having our records replaced with existing USMARC records by intervention from above, we can convert our records without losing information into USMARC records. That's because all the options we need are provided for both in USMARC and AACR2. No new rules or format elements are required. The fathers and mothers of rules and format had the foresight to make provisions for everything we need. We only have to make use of record linking. And due to some changes we are now in the process of making in our shared databases, the linking technique can be kept very simple and yet apply for all situations where we see a need for it. To show you what it may look like, I have prepared a few examples. I present these examples as bare outlines only, woodcuts rather than etchings, to make the essentials visible. Full examples are in the demo database set up for the project and accessible on our Web server in Braunschweig. You get to these examples in a matter of three or four mouseclicks if you call up this URL
This is for the REUSE+ final report and links you on to the demo database. The PowerPoint slides are available from this address, too.
The examples are in three categories: (see the PowerPoint slides and demo database)
Sets - Multiparts - Containers.
Please keep in mind I am not an AACR cataloger, so you are bound to find mistakes with indicators or worse. Please look beyond this, look at the "big picture".
Looking at the example for sets, you are probably tempted to say it is overstepping the mark to provide subrecords for every volume when there is effectively very little information on the volume level. Our time-tested experience points to the contrary, for five reasons:
If you introduce links and subrecords (not exactly a small "if", but I repeat: it requires no new inventions in format or rules!) then you can finally reuse German data to their full extent to enhance your national (and subsequently local) bibliographic record, even for many American books, not just for German ones, for we did and we do create the subrecords for all the books we catalog. (In the Göttingen Pica database alone, we have 1.5 Million subrecords.) And you end up with a sum total of less work on the local level, and more effect. This is not a miracle, it is nothing more than an application of common sense, and in our country, it is reality. In some US local systems, bibliographic linking is also a reality today, and these could benefit more directly and sooner than others. It is certainly possible that one of the US local systems, or one of the vendors, go ahead with a project to merge our subrecords into their database and link them to existing collection records.
What you will find lacking in our records, and most of you will know it, is usable subject information. There is no commonly used classification in Germany, and our subject headings do not easily match with LC subject headings. The concepts captured in the headings are very often incongruent. Some work is under way now to construct concordances with LC classification and subject headings. If this work bears fruit, more benefits can be reaped on both sides because we could also make more complete use of MARC data than is possible now.
For this presentation, I chose to confront you with some sort of a vision - the unification of our separate bibliographic galaxies, rather than just the few nuts and bolts technicalities we found as possible, small improvements within the contraints of the status quo, which would mean minimal changes in USMARC practice - but also no measurable step toward unification. (We describe these nuts and bolts, like proposals for new indicators for the 505, in the final report. They are really not enough substance for a presentation on an occasion like this.)
Since the suggestions I presented conform with trends discussed last year at the Toronto Conference, and I may remind you of the IFLA paper on Functional Requirements for Bibliographic Records, and since the recent metadata initiatives, as exemplified by the Dublin Core movement, point into the same direction: namely the implementation of some kind of bibliographic linking technique, there is reason for hoping we can get our bibliographic galaxies finally linked up.