Recent Posts
Recent Comments
Most Commented On
Archives
Blog
Link This | Email this | Blog This | Comments (1)
The Unused Complexity of MARCOctober 14, 2009 MAchine Readable Cataloging (MARC), a carrier standard for bibliographic information used along with rules described by the Anglo American Cataloging Rules, Second Edition (AACR2), has not (yet) died, despite my plea that it do so, nearly 7 years ago to this very day in the pages of Library Journal. Although that screed was not completely on the mark (do with that pun what you will), it helped to spark a conversation about our bibliographic standards and where we need to go in the future. For what it's worth, I corrected and expanded on the ideas in that less-than-800-word column in an award-winning journal article not long thereafter.I was reminded about this in recent days by two independent and yet related events. One was the NISO Webinar on Bibliographic Control. Among other presenters, Bill Moen of the University of North Texas reported on research he had conducted along with his colleague Shawne Miksa and their research assistants, on use patterns of MARC fields and subfields -- some excellent research that will serve to inform our way forward into new standards for bibliographic description. Another event was the release of data OCLC has extracted from the now 145 million record WorldCat database. As my OCLC Research colleague Thom Hickey reports, there have been several changes in the collective view of how we have used the MARC format over the years, probably mainly due to the massive influx of records from international sources. But one thing that remains true, and has now been reported by both Bill Moen and OCLC is that a number of fields and/or subfields of the MARC format are either completely unused or virtually so. At this point I want to remind everyone that MARC was developed by well-meaning people who have worked hard to create and maintain this standard over many years in an attempt to forsee our needs into the future. They deserve our praise and thanks. But needless complexity has made our systems needlessly complex, and therefore needlessly expensive and difficult. The issues begin with scripts to import data and don't end until we've figured out what to do with all 2,000 or so individual elements in a full record display. The costs are not insubstantial, and they can be multiplied across as many of our systems as come into contact with this complexity. Now we must decide where we need to go, and how. I think a big part of what we must do is to decide what must remain and what can go. We must be highly selective in what we choose to carry forward into the future. The good news is that we don't need to imagine which data elements might be used or not -- we have actual data. Now begins the work to figure out what to do about it. Posted by Roy Tennant on October 14, 2009 | Comments (1)
October 14, 2009
In response to: The Unused Complexity of MARC LibraryThingTim commented: "But needless complexity has made our systems needlessly complex, and therefore needlessly expensive and difficult."
Advertisement
|
Advertisements
|
|
|
|