« Anti-Cataloger Statements - My Rebuttal | Main | Update on the LC Working Group on the Future of Bibliographic Control »

Wednesday, October 17, 2007


Feed You can follow this conversation by subscribing to the comment feed for this post.

Joseph Shubitowski

I am not sure I quite understand the comment about "We do not work directly on MARC now, why would we have to work directly with XML in the future?". If I look at the Voyager cataloging client (and others I have seen recently), it sure looks like real/raw MARC to me. A template comes up with a bare bones record in it, with all the tags, indicators, and subfields ready for input. Catalogers must know MARC to know what subfields are legal, what order they go in etc.

To me that is knowing and working on/with MARC. Does anyone or any mainstream vendor provided ILS "hide" the complexity of the MARC record in the cataloging client? Do catalogers deal with this? Most catalogers I know revel in the details of knowing the ins and outs of MARC tagging, indicators, subfielding, etc.


Kevin S. Clarke

Joe: I believe that is in reference to the parts of the MARC record we don't see (and that it has been reformatted around MARC's field/subfield structure to make editing easier). For instance, we don't see the leader or MARC directory in MARC editors. Some leader info, though, is broken out into a separate display that often appears above the MARC fields. I have a slide from a 2002 presentation that illustrates: http://elane.stanford.edu/laneauth/ksc-access2002/img4.html

Chris Schwartz

Joe and Kevin, Thanks for the comments. Joe, along with Kevin's example, you might want to take a look at the post I quoted from. Carlos provides two examples that illustrate the difference.

Tim Knight

Hi Joe,
I agree that we 'revel in the details', but we're working in an ILS cataloguing module not directly in the 'raw' MARC (see below). So by the same token I think we won't be working directly in the XML tagged data but will be at a higher level which may look very much like the ILS interfaces we are currently using.

01374cam 22003254a 4500001001300000003000400013005001700017008004100034010001700075020002500092020002200117040005100139043001200190049001000202050002200212055002800234082001700262100003200279245008700311260005400398300002600452440003300478504006600511505022600577650006300803856008200866949006100948980003101009981000801040 2006039512DLC20071001101204.0061127s2007 enk b 001 0 eng  a 2006039512 a9781845680442 (pbk.) a1845680448 (pbk.) aDLCcDLCdBAKERdBTCTAdUKMdYDXCPdC#PdOCLCA ae-uk--- aCOTYL00aKD1554b.M58 2007 8aKF801b.M58 20072kfmod00a346.41022221 aMitchell, Catherine,d1966-10aInterpretation of contracts :bcurrent controversies in law /cCatherine Mitchell. aLondon ;aNew York :bRoutledge-Cavendish,c2007. axii, 160 p. ;c22 cm. 0aCurrent controversies in law aIncludes bibliographical references (p. [149]-155) and index.0 aThe nature and scope of contractual interpretation -- Contract interpretation and the rise of contextualism -- Contextual interpretation : methods and disputes -- Formalism in interpretation -- Controlling interpretation. 0aContractszGreat BritainxInterpretation and construction.413Table of contents onlyuhttp://www.loc.gov/catdir/toc/ecip075/2006039512.html aKF 801 M58 2007i39007047963293lLAWmYORK-LAWtLAW-BOOK a070928b2695e2210f235947 cLAW

The comments to this entry are closed.

Scope of blog

  • The focus of this blog is the future of cataloging and metadata in libraries.

Enter your email address:

Delivered by FeedBurner

Twitter Updates

    follow me on Twitter

    July 2014

    Sun Mon Tue Wed Thu Fri Sat
        1 2 3 4 5
    6 7 8 9 10 11 12
    13 14 15 16 17 18 19
    20 21 22 23 24 25 26
    27 28 29 30 31    


    Future of Cataloging: Key Resources (to May 2008)

    Blog powered by Typepad
    Member since 04/2007