 |
 |
The real key to moving libraries away from MARC will probably be transformation of the sharing situation. Open linked data gives promise of being able to do this (if everyone was able to harvest whatever "triples" they needed for whatever they wanted to describe) -- but wouldn't there need to be "hubs" that provided reliable data and were available to harvest from, at scale, (or, something like "linked data torrents" perhaps)? And enough standardization of the data to support common library discovery and delivery functions? It isn't clear what the economic model to support this would be. Meanwhile... how does one "get hold of" ONIX? Laura (list newbie, plese be kind) Laura Akerman Technology and Metadata Librarian Room 128, Robert W. Woodruff Library Emory University, Atlanta, Ga. 30322 (404) 727-6888 [log in to unmask] -----Original Message----- From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Walter Lewis Sent: Wednesday, March 14, 2012 2:28 PM On 2012-03-14, at 2:11 PM, Bess Sadler wrote: > Q1. Is there an ILS that is not based on MaRC records? > > A1. No, not to my knowledge. Yes, marc cataloging can seem tedious and arcane, but we have lots of tools for working with it at this point. All commercial ILS vendors that I am aware of use it, and the open source ILS products I know of also use MaRC. Further note to this. a) All the commercial and non-commercial ILS systems used by more than one institution of which I am aware either added MARC processing or died. b) All of the systems for which I have seen the underpinnings have mapped the important values from the Marc record into various other SQL data structures. They may store the Marc on the side or assemble it on the fly at the point of demand. Marc enters and exits the system but may or may not drive the internals. Walter Lewis who would happily forget everything he learned about Marc; but honestly folks there are lots of things that make less sense in the world ________________________________ This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments).