<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"><channel><title>Disruptive Library Technology Jester &#187; AACR</title> <atom:link href="http://dltj.org/tag/aacr/feed/" rel="self" type="application/rss+xml" /><link>http://dltj.org</link> <description>We&#039;re Disrupted, We&#039;re Librarians, and We&#039;re Not Going to Take It Anymore</description> <lastBuildDate>Mon, 06 Feb 2012 20:04:22 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <cloud domain='dltj.org' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' /> <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/us/</creativeCommons:license> <item><title>Friday Followups: RDA Revolt and Cable TV vs. Internet Streaming</title><link>http://dltj.org/article/thursday-threads-2010w49/</link> <comments>http://dltj.org/article/thursday-threads-2010w49/#comments</comments> <pubDate>Fri, 10 Dec 2010 20:21:11 +0000</pubDate> <dc:creator>Peter Murray</dc:creator> <category><![CDATA[Thursday Threads]]></category> <category><![CDATA[AACR]]></category> <category><![CDATA[cable tv]]></category> <category><![CDATA[cataloging coup]]></category> <category><![CDATA[Comcast]]></category> <category><![CDATA[Level 3 Communications]]></category> <category><![CDATA[Netflix]]></category> <category><![CDATA[network neutrality]]></category> <category><![CDATA[Resource Description and Access]]></category><guid isPermaLink="false">http://dltj.org/?p=1888</guid> <description><![CDATA[Receive DLTJ Thursday Threads:&#8226;&#160;by&#160;E-mail&#8226;&#160;by&#160;RSS&#160;Delivered by FeedBurnerIt has been another busy week, and unfortunately Thursday has slipped into Friday. There have been a few updates to earlier Thursday Threads items, so I&#8217;m turning this into &#8220;Friday Followups&#8221; instead. We&#8217;ll attempt to &#8230; <a href="http://dltj.org/article/thursday-threads-2010w49/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<abbr class="unapi-id ignore noPrint" title="http://dltj.org/?p=1888"></abbr><div id="feedburner-thursday-threads-email-w49" class="wp-caption alignright" style="width: 230px;;  border: 1px solid #dddddd; background-color: #f3f3f3; padding-top: 4px; margin: 10px; text-align:center; float: right;"><form style="border:1px solid #ccc;padding:3px;margin:0;text-align:center;" action="http://feedburner.google.com/fb/a/mailverify" method="post" target="popupwindow" onsubmit="window.open('http://feedburner.google.com/fb/a/mailverify?uri=thursday-threads', 'popupwindow', 'scrollbars=yes,width=550,height=520');return true"><p>Receive <i><acronym title="Disruptive Library Technology Jester">DLTJ</acronym></i> Thursday Threads:</p><p>&bull;&nbsp;by&nbsp;<a href="http://feedburner.google.com/fb/a/mailverify?uri=thursday-threads&#038;loc=en_US" title="D.L.T.J. Thursday Threads Email Subscription">E-mail</a><br /><input type="text" style="width:140px" name="email" value="Your e-mail address" onFocus="if (this.defaultValue==this.value) this.value = ''"/><input type="hidden" value="thursday-threads" name="uri"/><input type="hidden" name="loc" value="en_US"/><input type="submit" value="Subscribe" /></p><p>&bull;&nbsp;by&nbsp;<a href="http://feeds.dltj.org/thursday-threads/" title="D.L.T.J. Thursday Threads RSS Feed">RSS</a>&nbsp;<a href="http://feeds.dltj.org/thursday-threads/" title="D.L.T.J. Thursday Threads RSS Feed"><img src="http://cdn.dltj.org/wp-content/uploads/2010/12/feed-icon32x321.png" alt="RSS Icon" width="12" height="12" /></a></p><p style="font-size: 80%">Delivered by <a href="http://feedburner.google.com" target="_blank" title="Google Feedburner Service">FeedBurner</a></p></form></div><p>It has been another busy week, and unfortunately Thursday has slipped into Friday.  There have been a few updates to earlier Thursday Threads items, so I&#8217;m turning this into &#8220;Friday Followups&#8221; instead.  We&#8217;ll attempt to get back new items next Thursday, but in the meantime take a look at these updates.</p><p><h2><a name="rda_revolt">&#8220;RDA Revolt&#8221; Continues</a></h2><br />A month ago I <a href="http://dltj.org/article/thursday-threads-2010w44/">mentioned</a> that there was a <a href="http://www.ipetitions.com/petition/norda/" title="Memorandum Against RDA Test">revolt of sorts</a> against RDA in general and the <a href="http://www.loc.gov/bibliographic-future/rda/index.html" title="Testing Resource Description and Access (RDA) - Working Group on the Future of Bibliographic Control (Library of Congress)">U.S. national test of RDA</a> in particular.  Although &#8220;RDA Revolt&#8221; hasn&#8217;t taken off in the vernacular as I&#8217;d hoped when I coined the phrase, &#8220;<a href="http://search.twitter.com/search?q=%22catalogingcoup%22" title="Twitter search for &#038;039;cataloging coup&#038;039'">cataloging coup</a>&#8221; has.  The primary venues are the OCLC-CAT and RDA-L mailing lists.  The former requires one to register and subscribe to the mailing list, but the latter has an <a href="http://www.mail-archive.com/rda-l@listserv.lac-bac.gc.ca/" title="rda-l mailing list archive">open web archive</a>.  As near as I can tell, the primary concerns relate to how authority records are added to OCLC:  should new RDA-based authority records be created when an existing AACR2 record exists (causing duplication in the authority file) and should RDA-based authority records be added to the authority file at all (because they cause problems for the vast majority of AACR2-based library systems).  The <a href="http://article.gmane.org/gmane.education.libraries.autocat/35809" title="US RDA Test Coordinating Committee response to the community">official answer from the RDA test office</a> is &#8220;no (duplicate records should not be created)&#8221; and &#8220;yes (that&#8217;s the point of the test)&#8221;. <a href="http://www.catalogingfutures.com/catalogingfutures/2010/12/rda-test-oclc-and-the-opposing-petition.html" title="Cataloging Futures: RDA test, OCLC, and the opposing petition">Candi Schwartz</a> and <a href="http://melissainstephenville.blogspot.com/2010/12/you-say-you-want-revolution.html" title="&#038;039;You say you want a revolution&#038;039;">Melissa Cookson</a> have more details about the controversy.</p><p><h2><a name="netflix_comcast">Netflix Battling with Comcast Over Payments to Stream Content</a></h2><br />There was an Thursday Threads entry two weeks ago that <a href="http://dltj.org/article/thursday-threads-2010w47/#cable_tv">mentioned the story about how fewer Americans are paying for cable TV service</a> and the correlation to how users can get content from the web.  That same report included mention of how <a href="http://www.nytimes.com/2010/11/23/technology/23netflix.html" title="A Cheaper Plan at Netflix Offers Films for Online Only | New York Times">Netflix was now offering a &#8220;streaming only&#8221; subscription plan</a>.  Now comes news that cable TV and consumer internet service provider Comcast is battling with Netflix&#8217;s content distribution network (Level 3) over the cost of the extra streaming usage that Netflix is dumping onto Comcast&#8217;s network.  Steve Schultze writing in Freedom to Tinker has a <a href="http://www.freedom-to-tinker.com/blog/sjs/trying-make-sense-comcast-level-3-dispute" title="Trying to Make Sense of the Comcast / Level 3 Dispute | Freedom-to-Tinker">good summary of the dispute</a> followed by two stories by Timothy Lee on the same blog that frames the dispute from the perspective of <a href="http://www.freedom-to-tinker.com/blog/tblee/two-stories-about-comcastlevel-3-dispute-part-1" title="Two Stories about the Comcast/Level 3 Dispute (Part 1) | Freedom to Tinker">Level 3</a> and <a href="http://www.freedom-to-tinker.com/blog/tblee/two-stories-about-comcastlevel-3-dispute-part-2" title="Two Stories about the Comcast/Level 3 Dispute (Part 2) | Freedom-to-Tinker">Comcast</a>.  I continue to think that there are issues here to watch for libraries because we want to be aware of how information from some sources might be given preferential treatment over others based on money flowing between companies.  In this respect it is related to the controversy of how drug manufacturers are paying ghostwriters to create articles that prominent doctors submit to prestigious journals.  How the information flows to us and our users may influence how reliable and trustworthy we think that information is.  How content is (or is not) being transmitted across the major internet backbones is a similar concern.</p>]]></content:encoded> <wfw:commentRss>http://dltj.org/article/thursday-threads-2010w49/feed/</wfw:commentRss> <slash:comments>3</slash:comments> </item> <item><title>MARC isn&#8217;t Dead, but it is a Dead End</title><link>http://dltj.org/article/marc-as-dead-end/</link> <comments>http://dltj.org/article/marc-as-dead-end/#comments</comments> <pubDate>Fri, 29 Oct 2010 16:29:02 +0000</pubDate> <dc:creator>Peter Murray</dc:creator> <category><![CDATA[L/IS Profession]]></category> <category><![CDATA[AACR]]></category> <category><![CDATA[American Library Association]]></category> <category><![CDATA[Functional Requirements for Bibliographic Records]]></category> <category><![CDATA[Karen Coyle]]></category> <category><![CDATA[linked data]]></category> <category><![CDATA[MARC]]></category> <category><![CDATA[metadata]]></category> <category><![CDATA[Resource Description and Access]]></category> <category><![CDATA[semantic web]]></category><guid isPermaLink="false">http://dltj.org/?p=1823</guid> <description><![CDATA[This week I sat in on the first of the three &#8220;Using RDA: Moving into the Metadata Future&#8221; webinars being hosted by ALA. This one was hosted by Karen Coyle with the title New Models of Metadata where she talked &#8230; <a href="http://dltj.org/article/marc-as-dead-end/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<abbr class="unapi-id ignore noPrint" title="http://dltj.org/?p=1823"></abbr><p>This week I sat in on the first of the three &#8220;<a href="http://www.alastore.ala.org/detail.aspx?ID=3125" title="Using RDA: Moving into the Metadata Future (A Three-part ALA TechSource Workshop)">Using RDA: Moving into the Metadata Future</a>&#8221; webinars being hosted by <acronym title="American Library Association">ALA</acronym>.  This one was hosted by <a href="http://kcoyle.net/" title="Karen Coyle's home page" rel="homepage">Karen Coyle</a> with the title <a href="http://www.alatechsource.org/blog/2010/10/continuing-the-conversation-new-models-of-metadata.html" title="Continuing the Conversation: New Models of Metadata | ALA TechSource">New Models of Metadata</a> where she talked about library-specific efforts such as<acronym title="Resource Description and Access"><a href="http://www.rdatoolkit.org/" title="RDA Toolkit">RDA</a></acronym> and <acronym title="Functional Requirement for Bibliographic Records"><a href="http://www.ifla.org/en/publications/functional-requirements-for-bibliographic-records" title="Functional Requirements for Bibliographic Records | IFLA">FRBR</a></acronym> as well as the <a href="http://linkeddata.org/" title="Linked Data - Connect Distributed Data across the Web">linked data</a> effort in the wider world of information.  There was a great deal of concern expressed in the chat window by participants about the future of cataloging, of cataloguers, and of <acronym title="MAchine-Readable Cataloging"><a href="http://www.loc.gov/marc/" title="MARC STANDARDS (Network Development and MARC Standards Office, Library of Congress)">MARC</a></acronym>.  The latter brought up memories of <a href="http://roytennant.com/professional.html" title="Roy Tennant: Professional Life">Roy Tennant</a>&#8216;s &#8220;<a href="http://www.libraryjournal.com/article/CA250046.html" title="MARC Must Die | Library Journal">MARC Must Die</a>&#8221; declaration.  My take away, though, isn&#8217;t that MARC is dead as much as MARC is a dead end.<br /><span id="more-1823"></span><br /><div id="attachment_1824" class="wp-caption alignright" style="width: 190px;  border: 1px solid #dddddd; background-color: #f3f3f3; padding-top: 4px; margin: 10px; text-align:center; float: right;"><a href="http://www.wfhowes.co.uk/catalogue/titles.php?&amp;t=4401" title="W. F. Howes Ltd (UK) - Audio Book &amp;amp; Large Print Publishers"><img src="http://cdn.dltj.org/wp-content/uploads/2010/10/Library-of-the-Dead-cover-art-180x300.jpg" alt="" title="&#039;Library of the Dead&#039; cover art" width="180" height="300" class="size-medium wp-image-1824" /></a><p style=' padding: 0 4px 5px; margin: 0;'  class="wp-caption-text">Cover art from 'Library of the Dead' audio book</p></div><br /><h2>MARC, not dead yet?</h2><br />We know that MARC isn&#8217;t dead; the communications format, along with its <acronym title="Anglo-American Cataloguing Rules, Second Edition"><a href="http://www.aacr2.org/" title="AACR2">AACR2</a></acronym> companion rules for describing bibliographic resources, are deeply and daily ingrained in our systems and processes.  For the same reasons, I think it is fair to say that MARC isn&#8217;t dying.  (The fate of AACR2 with respect to RDA may be a little closer to the edge.)  What I propose, though, is that MARC is a dead end.  Karen makes a comment &#8212; <a href="http://www.alatechsource.org/blog/2010/10/continuing-the-conversation-new-models-of-metadata.html#comment-2803" title="Continuing the Conversation: New Models of Metadata | ALA TechSource">On the brokenness of MARC</a> &#8212; that starts to enumerate some of the basic issues with the MARC format.  (Karen&#8217;s <a href="http://www.kcoyle.net/marcdead.html" title="Is MARC Dead? by Karen Coyle">writings from 10 years ago</a> lists even more details.)  Also, as Karen pointed out in her presentation (and many others have done before her), MARC is a format that is only used in the library community.  As a communications format, it is cumbersome &#8212; requiring those outside the library community to use custom code toolkits to read and write the format.  That is a pretty high barrier for the wider world to want to use library bibliographic data encoded in MARC.</p><p>What trips up our community even more, I think, is that we have a tendency to equate this communications format with mental model of how we describe things from a bibliographic point of view.  We think of discrete records that describe these things rather than a network (or, more accurately, a <a href="http://en.wikipedia.org/wiki/Graph_theory" title="Graph theory - Wikipedia">graph</a>) of interrelated nodes.  This forces us to focus on the textual content of fields and not on the relationships between things.  And in doing so, we are not making the best use of our limited efforts to describe the things in our curatorial care.</p><p>MARC may not be dead, but it is a dead end.</p>]]></content:encoded> <wfw:commentRss>http://dltj.org/article/marc-as-dead-end/feed/</wfw:commentRss> <slash:comments>20</slash:comments> </item> <item><title>Who Said You Couldn&#8217;t Catalog the Internet?</title><link>http://dltj.org/article/who-said-you-couldnt-catalog-the-internet/</link> <comments>http://dltj.org/article/who-said-you-couldnt-catalog-the-internet/#comments</comments> <pubDate>Tue, 06 Jun 2006 13:42:00 +0000</pubDate> <dc:creator>Peter Murray</dc:creator> <category><![CDATA[Disruption in Libraries]]></category> <category><![CDATA[AACR]]></category> <category><![CDATA[folksonomy]]></category> <category><![CDATA[Library of Congress Subject Headings]]></category> <category><![CDATA[tagging]]></category><guid isPermaLink="false">http://dltj.org/2006/06/who-said-you-couldnt-catalog-the-internet/</guid> <description><![CDATA[I seem to remember, in the early heady days of the internet, there was a cry from the library profession to &#8220;Catalog the Internet&#8221; &#8212; to create descriptive records and controlled vocabularies for every resource out there deemed useful. The &#8230; <a href="http://dltj.org/article/who-said-you-couldnt-catalog-the-internet/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<abbr class="unapi-id ignore noPrint" title="http://dltj.org/2006/06/who-said-you-couldnt-catalog-the-internet/"></abbr><p>I seem to remember, in the early heady days of the internet, there was a cry from the library profession to &#8220;Catalog the Internet&#8221; &#8212; to create descriptive records and controlled vocabularies for every resource out there deemed useful.  The <a href="http://web.archive.org/web/19961017235908/http://www2.yahoo.com/" title="Yahoo!">early Yahoo!</a>, with a librarian on the staff, was going to help by putting everything in a neat, orderly classification system.  The rest of us were going to catalog sites like mad and put them all into WorldCat (and keep them up-to-date).  A nice dream.</p><p>Looking back, we can probably guess the reasons why this dream isn&#8217;t reality today:  ill-suited classification schemes, sites that defy classification, etc.  I think the real killer, though, was that we thought we could do it ourselves.  But you know what?  There is too many of &#8220;them&#8221; creating content on the internet and not enough of &#8220;us&#8221; to keep up.</p><p>I was reminded of this history as a I read a &#8220;HOWTO&#8221; called &#8220;<a href="http://www.techsoup.org/learningcenter/webbuilding/page5508.cfm" title="Thirteen Tips for Effective Tagging">Thirteen Tips for Effective Tagging</a>: How to mark sites so you and others can find them&#8221; found via <a href="http://lisnews.org/node/18783" title="http://lisnews.org/article.pl?sid=06/06/05/125239">an LISnews posting</a>.   Written by non-librarians (presumably) for a non-librarian audience, it describes a &#8220;collaboratively generated, open-ended labeling system that enables Internet users to categorize content such as Web pages, online photographs, and Web links.&#8221;  Sounds reasonable enough, yes?  After all, as a profession we just need to step in and give them <a href="http://en.wikipedia.org/wiki/Library_of_Congress_Subject_Headings" title="Tools for Authority Control--Subject Headings">LCSH</a> <sup><a href="http://dltj.org/article/who-said-you-couldnt-catalog-the-internet/#footnote_0_64" id="identifier_0_64" class="footnote-link footnote-identifier-link" title="I couldn&amp;#8217;t help but laugh when I read the big news for the 2006 edition of LCSH:  &amp;#8220;BONUS! Includes Free-floating Subdivisions as a separate section in Volume I.&amp;#8221;  Hurray!">1</a></sup> as a &#8220;open-ended labeling system&#8221;, right?</p><p>Nope, the next sentence of the article reads:  &#8220;Tagging lets you categorize information online <i>your</i> way.&#8221;</p><p>What?!?  Their way?  No way!  We&#8217;ve got things like MARC, AACR, Dewey, and LCSH that have taken us decades to build.  We know how to do this better than anyone else, so y&#8217;all just sit back and let us do our jobs. <sup><a href="http://dltj.org/article/who-said-you-couldnt-catalog-the-internet/#footnote_1_64" id="identifier_1_64" class="footnote-link footnote-identifier-link" title="In the words of Michael Gorman, &amp;#8220;I have spent a lot of my long professional life working on aspects of the noble aim of Universal Bibliographic Control&mdash;a mechanism by which all the world&amp;#8217;s recorded knowledge would be known, and available, to the people of the world.&amp;#8221;  I offer that this excerpt resonates with many in the library profession today, and that we think we can still build a system of Universal Bibliographic Control that will be so good everyone else will obviously adopt it.">2</a></sup></p><p>But in the grand tradition of the history of the internet, collectively its users routed around failure. <sup><a href="http://dltj.org/article/who-said-you-couldnt-catalog-the-internet/#footnote_2_64" id="identifier_2_64" class="footnote-link footnote-identifier-link" title="One of the strengths of the internet is its capacity to &amp;#8220;route around&amp;#8221; failure, as explained in this piece from &amp;#8220;NCSA&amp;#8217;s Looking Back On Three Decades Of Internet History&amp;#8220;:But in the early 1960&amp;#8242;s, researchers began to realize that a computer network would be much less vulnerable to failure if it was more widely spread out &amp;#8212; less like the air travel system than like the network of back roads weaving together every municipality in the country. Each point is connected to its nearest neighbors by several redundant paths. If a connecting node between A and B fails, it is easy to find an alternative route.">3</a></sup> And here it is done in grand fashion with 13 recommendations for user-supplied, globally recognized tagging:</p><ol><li>Be a lemming.</li><li>Follow the herd.</li><li>Avoid camels.</li><li>Like nature, del.icio.us abhors a vacuum.</li><li>Punctuate with care.</li><li>Independence is a virtue.</li><li>Hang out at crossroads.</li><li>Co-ordinate your efforts.</li><li>Tags are written in pencil.</li><li>Bonus tip for Mac users: the Cocoalicious client.</li><li>On del.icio.us, everyone knows you&#8217;re a dog.</li><li>Shh! This one&#8217;s for:you.</li><li>Spread the word.</li></ol><p>Is it a perfect system?  No &#8212; and one could pick at the many faults.</p><p>Does it work?  Arguably, well, yes.</p><p>Update (20080404T2147) : Update link to &#8220;Thirteen Tips&#8230;&#8221;<p style="padding:0;margin:0;font-style:italic;">The text was modified to update a link from http://www.loc.gov/cds/lcsh.html to http://en.wikipedia.org/wiki/Library_of_Congress_Subject_Headings on November 17th, 2010.</p><p style="padding:0;margin:0;font-style:italic;">The text was modified to update a link from http://lisnews.org/article.pl?sid=06/06/05/125239 to http://lisnews.org/node/18783 on January 13th, 2011.</p><h2>Footnotes</h2><ol class="footnotes"><li id="footnote_0_64" class="footnote">I couldn&#8217;t help but laugh when I read the big news for the 2006 edition of LCSH:  &#8220;BONUS! Includes Free-floating Subdivisions as a separate section in Volume I.&#8221;  Hurray!</li><li id="footnote_1_64" class="footnote">In the <a href="http://www.libraryjournal.com/article/CA502009.html?display=BackTalkNews&#038;industry=BackTalk&#038;industryid=3767&#038;verticalid=151&#038;&#038;" title="http://www.libraryjournal.com/article/CA502009.html?display=BackTalkNews&#038;industry=BackTalk&#038;industryid=3767&#038;verticalid=151&#038;&#038;">words of Michael Gorman</a>, &#8220;I have spent a lot of my long professional life working on aspects of the noble aim of Universal Bibliographic Control—a mechanism by which all the world&#8217;s recorded knowledge would be known, and available, to the people of the world.&#8221;  I offer that this excerpt resonates with many in the library profession today, and that we think we can still build a system of Universal Bibliographic Control that will be so good everyone else will obviously adopt it.</li><li id="footnote_2_64" class="footnote">One of the strengths of the internet is its capacity to &#8220;route around&#8221; failure, as explained in this piece from &#8220;<a href="http://www.ncsa.uiuc.edu/News/datalink/9911/HPCwire4.html" title="http://www.ncsa.uiuc.edu/News/datalink/9911/HPCwire4.html">NCSA&#8217;s Looking Back On Three Decades Of Internet History</a>&#8220;:<br /><blockquote>But in the early 1960&#8242;s, researchers began to realize that a computer network would be much less vulnerable to failure if it was more widely spread out &#8212; less like the air travel system than like the network of back roads weaving together every municipality in the country. Each point is connected to its nearest neighbors by several redundant paths. If a connecting node between A and B fails, it is easy to find an alternative route.</p></blockquote><p></li></ol>]]></content:encoded> <wfw:commentRss>http://dltj.org/article/who-said-you-couldnt-catalog-the-internet/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>The Problem with MARC and AACR: the World Doesn&#8217;t Disco Anymore</title><link>http://dltj.org/article/the-problem-with-marc-and-aacr/</link> <comments>http://dltj.org/article/the-problem-with-marc-and-aacr/#comments</comments> <pubDate>Tue, 16 May 2006 13:21:17 +0000</pubDate> <dc:creator>Peter Murray</dc:creator> <category><![CDATA[Disruption in Libraries]]></category> <category><![CDATA[AACR]]></category> <category><![CDATA[MARC]]></category><guid isPermaLink="false">http://dltj.org/2006/05/the-problem-with-marc-and-aacr-the-world-doesnt-know-disco/</guid> <description><![CDATA[My undergraduate background is in computer science, and from that perspective I have a great deal of admiration for MARC and AACR as well as their creators and proponents: Henriette Avram and Michael Gorman. At their creation, MARC and AACR &#8230; <a href="http://dltj.org/article/the-problem-with-marc-and-aacr/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<abbr class="unapi-id ignore noPrint" title="http://dltj.org/2006/05/the-problem-with-marc-and-aacr-the-world-doesnt-know-disco/"></abbr><p>My undergraduate background is in computer science, and from that perspective I have a great deal of admiration for MARC and AACR as well as their creators and proponents: Henriette Avram and Michael Gorman.  At their creation, MARC and AACR propelled library services to new heights of efficiency and usefulness.  Here&#8217;s my problem, though: we no longer live in the 1970s, and the fundamental tools of our trade should not be based in nearly 40-year-old technology.</p><p>This post started out as a comment to <a href="http://lisnews.org/node/26973" title="Gorman and Fischerspooner | LISNews:">an LISnews thread</a> by <a href="http://librarian.lishost.org/" title="Librarian">Kathleen</a> <a href="http://unionlibrarian.blogspot.com/" title="Union Librarian">de</a> <a href="http://justicelibraries.blogspot.com/" title="Librarians for Human Rights">la</a> <a href="http://justicelibraries.blogspot.com/" title="Librarians for Human Rights">Peña</a> <a href="http://librarianoutreach.blogspot.com/" title="A LIBRARIAN AT THE KITCHEN TABLE">McCook</a> that pointed back to a posting with the title <a href="http://librarian.lishost.org/?p=382" title="Michael Gorman, Fischerspooner, Amnesty International and Hamlet.  No.5.13.2006-61. &amp;laquo;  Librarian">Michael Gorman, Fischerspooner, Amnesty International and Hamlet</a>.  The more I thought about it, though, the more the comment went beyond a criticism of my perception of <a href="http://mg.csufresno.edu/" title="Michael Gorman">Michael Gorman&#8217;s</a> <a href="http://www.libraryjournal.com/article/CA502009.html" title="BackTalk: Revenge of the Blog People!</p><p>Manage Newsletter Subscription<br />&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;</p><p>Library Journal</p><p> if (cookies_enabled){		serveAds('0','1','/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04%3D%15%01LJLeaderboard728x90%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013e6y2tn700%08%01883299%02%04%02%04','&amp;lt;iframe src = &amp;quot;/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04%3D%15%01LJLeaderboard728x90%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013e6y2tn700%08%01883299%02%04%02%04&amp;amp;noscript=1&amp;quot;  height=&amp;quot;90px&amp;quot;  width=&amp;quot;728px&amp;quot;  frameborder=&amp;quot;0&amp;quot; scrolling=&amp;quot;no&amp;quot; vspace=&amp;quot;0&amp;quot; style=&amp;quot;left: -1pt; position: relative; top: -2pt;&amp;quot; marginwidth=&amp;quot;0&amp;quot; marginheight=&amp;quot;0&amp;quot; hspace=&amp;quot;0&amp;quot; allowtransparency=&amp;quot;true&amp;quot; &amp;gt;&amp;lt;/iframe&amp;gt;','LJLeaderboard728x90','61');	}</p><p> Home</p><p> LJ in Print</p><p> Current Issue</p><p> Archive</p><p> Library by Design<br /> Movers and Shakers<br /> netConnect<br /> Reference Supplement</p><p> Subscribe</p><p> Newsletters</p><p> BookSmack</p><p> Library Hotline</p><p> LJ Academic Newswire<br /> LJ Review Alert<br /> LJXpress<br /> Sign Up</p><p> Libraries &amp;amp; Librarians</p><p> Academic Libraries<br /> ALA Conference</p><p> Building &amp;amp; Facilities<br /> Copyright/Fair Use<br /> Funding<br /> Intellectual Freedom</p><p> Legislation<br /> Library Culture<br /> Library Education<br /> Managing Libraries<br /> Opinion<br /> People</p><p> PLA National Conference<br /> Public  Services</p><p> Reviews</p><p> Spanish-Language Authors &amp;amp; Book Reviews<br /> Book<br /> Genre Fiction</p><p> Graphic Novels</p><p> Reference<br /> Professional Media<br /> Magazine/Zine<br /> Music<br /> Video/DVD</p><p> Audio<br /> Gaming<br /> Xpress Reviews</p><p>Collection Development</p><p> Best Books<br /> Books News/Interviews<br /> Collection Development</p><p> Collection Development Calendar<br /> Prepub Alerts</p><p> Technology</p><p> News &amp;amp; Features<br /> Library 2.0<br /> Products/Vendors<br /> Casey/Stephens: The Transparent Library<br /> Tennant: Digital Libraries<br /> Tenopir: Online DB</p><p> Careers</p><p> News &amp;amp; Features</p><p> Education/ Training<br /> Job Zone</p><p> New Librarians<br /> Salaries</p><p> Blogs</p><p> Bubble Room<br /> Annoyed Librarian</p><p> Digital Libraries<br /> E-Views</p><p> Games, Gamers, &amp;amp; Gaming</p><p> In the Bookroom<br /> LJ Insider<br /> PrePub Alert</p><p> ShelfRenewal<br /> All Blogs</p><p> Tools</p><p> Annual Articles &amp;amp; Awards</p><p> Webcast<br /> ebook Summit</p><p> Submit to LJ</p><p> Articles<br /> News, Photos, Feedback<br /> Architectural Issue<br /> Awards<br /> Movers &amp;amp; Shakers</p><p> Titles for Review<br /> Review for LJ</p><p>Any time<br />Past 24 hours<br />Past week<br />Past 2 weeks<br />Past month<br />Past 2 months<br />Past 6 months<br />Past year<br />Past 2 years<br />Past 5 years<br />Past 10 years</p><p> try {<br /> var qdr = /[?&amp;]as_qdr=([^&amp;]*)/<br /> .exec(window.location.search)[1];<br /> var opts = document<br /> .getElementsByName(&quot;as_qdr&quot;)[0]<br /> .getElementsByTagName(&quot;option&quot;);<br /> for (var i = 0; i &lt; opts.length; i++)<br /> opts[i].selected = (opts[i].value == qdr);<br /> } catch (e) {}</p><p> if (cookies_enabled){		serveAds('0','1','/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04A%15%01LJSearchButton88x31%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013e6y2tn700%08%01883299%02%04%02%04','&amp;lt;iframe src = &amp;quot;/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04A%15%01LJSearchButton88x31%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013e6y2tn700%08%01883299%02%04%02%04&amp;amp;noscript=1&amp;quot;  height=&amp;quot;31px&amp;quot;  width=&amp;quot;88px&amp;quot;  frameborder=&amp;quot;0&amp;quot; scrolling=&amp;quot;no&amp;quot; vspace=&amp;quot;0&amp;quot; style=&amp;quot;left: -1pt; position: relative; top: -2pt;&amp;quot; marginwidth=&amp;quot;0&amp;quot; marginheight=&amp;quot;0&amp;quot; hspace=&amp;quot;0&amp;quot; allowtransparency=&amp;quot;true&amp;quot; &amp;gt;&amp;lt;/iframe&amp;gt;','LJSearchButton88x31','65');	}</p><p> if (cookies_enabled){		serveAds('0','1','/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04C%12%01LJTickerAd983x25%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013e6y2tn700%08%01883299%02%04%02%04','&amp;lt;iframe src = &amp;quot;/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04C%12%01LJTickerAd983x25%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013e6y2tn700%08%01883299%02%04%02%04&amp;amp;noscript=1&amp;quot;  height=&amp;quot;25px&amp;quot;  width=&amp;quot;983px&amp;quot;  frameborder=&amp;quot;0&amp;quot; scrolling=&amp;quot;no&amp;quot; vspace=&amp;quot;0&amp;quot; style=&amp;quot;left: -1pt; position: relative; top: -2pt;&amp;quot; marginwidth=&amp;quot;0&amp;quot; marginheight=&amp;quot;0&amp;quot; hspace=&amp;quot;0&amp;quot; allowtransparency=&amp;quot;true&amp;quot; &amp;gt;&amp;lt;/iframe&amp;gt;','LJTickerAd983x25','67');	}</p><p> function doLog(logStatement){}</p><p> var cookies_enabled = false;<br /> function dti_ad_area_HTMLDecode(textToDecode)<br /> {<br /> var result = textToDecode</p><p> if (result &amp;&amp; result != '')<br /> {<br /> var amp = '&amp;';<br /> var gt = '&gt;';<br /> var lt = ' 0)<br /> {<br /> t=setTimeout(&quot;serveAds(&quot;+ refreshAdRate + &quot;, &quot; + numSlots + &quot;, '&quot; + encodedURL + &quot;', '&quot; + noScriptContents + &quot;', '&quot;+ areaName + &quot;', '&quot; + theId + &quot;')&quot;, refreshAdRate * 1000);<br /> }<br /> }</p><p> function doLog(logStatement){}</p><p>var gaJsHost =<sup><a href="http://dltj.org/article/the-problem-with-marc-and-aacr/#footnote_0_58" id="identifier_0_58" class="footnote-link footnote-identifier-link" title="&amp;quot;https:&amp;quot; == document.location.protocol) ? &amp;quot;https://ssl.&amp;quot; : &amp;quot;http://www.&amp;quot;);document.write(unescape(&amp;quot;%3Cscript src=&#039;&amp;quot; + gaJsHost + &amp;quot;google-analytics.com/ga.js&#039; type=&#039;text/javascript&#039;%3E%3C/script%3E&amp;quot;">1</a></sup>;</p><p>try {<br />var pageTracker = _gat._getTracker(&quot;UA-16323142-1&quot;);<br />pageTracker._setDomainName(&quot;.libraryjournal.com&quot;);</p><p>pageTracker._trackPageview();<br />} catch(err) {}</p><p>GS_googleAddAdSenseService(&quot;ca-pub-1872221973353849&quot;);<br />GS_googleEnableAllServices();</p><p>GA_googleAddSlot(&quot;ca-pub-1872221973353849&quot;, &quot;LJ_160x160_B&quot;);</p><p>GA_googleFetchAds();</p><p>Articles">world view</a>.  I must admit that I was also influenced by the <a href="http://www.i-am-bored.com/bored_link.cfm?link_id=17295" title="Evolution of Dance | I Am Bored">Evolution of Dance</a> video that is making the rounds on the net (thanks, Thomas!) &mdash; hence the byline to this post.  So I&#8217;ve edited the comment and posted it here (with comments and trackbacks open, I might add) for posterity.</p><p>I noted this statement in the <a href="http://www.libraryjournal.com/article/CA6331810.html" title="MARC Creator Henriette Avram Dies at 86</p><p>Manage Newsletter Subscription<br />&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;</p><p>Library Journal</p><p> if (cookies_enabled){		serveAds('0','1','/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04%3D%15%01LJLeaderboard728x90%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013chf2ush00%08%01866226%02%04%02%04','&amp;lt;iframe src = &amp;quot;/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04%3D%15%01LJLeaderboard728x90%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013chf2ush00%08%01866226%02%04%02%04&amp;amp;noscript=1&amp;quot;  height=&amp;quot;90px&amp;quot;  width=&amp;quot;728px&amp;quot;  frameborder=&amp;quot;0&amp;quot; scrolling=&amp;quot;no&amp;quot; vspace=&amp;quot;0&amp;quot; style=&amp;quot;left: -1pt; position: relative; top: -2pt;&amp;quot; marginwidth=&amp;quot;0&amp;quot; marginheight=&amp;quot;0&amp;quot; hspace=&amp;quot;0&amp;quot; allowtransparency=&amp;quot;true&amp;quot; &amp;gt;&amp;lt;/iframe&amp;gt;','LJLeaderboard728x90','61');	}</p><p> Home</p><p> LJ in Print</p><p> Current Issue</p><p> Archive</p><p> Library by Design<br /> Movers and Shakers<br /> netConnect<br /> Reference Supplement</p><p> Subscribe</p><p> Newsletters</p><p> BookSmack</p><p> Library Hotline</p><p> LJ Academic Newswire<br /> LJ Review Alert<br /> LJXpress<br /> Sign Up</p><p> Libraries &amp;amp; Librarians</p><p> Academic Libraries<br /> ALA Conference</p><p> Building &amp;amp; Facilities<br /> Copyright/Fair Use<br /> Funding<br /> Intellectual Freedom</p><p> Legislation<br /> Library Culture<br /> Library Education<br /> Managing Libraries<br /> Opinion<br /> People</p><p> PLA National Conference<br /> Public  Services</p><p> Reviews</p><p> Spanish-Language Authors &amp;amp; Book Reviews<br /> Book<br /> Genre Fiction</p><p> Graphic Novels</p><p> Reference<br /> Professional Media<br /> Magazine/Zine<br /> Music<br /> Video/DVD</p><p> Audio<br /> Gaming<br /> Xpress Reviews</p><p>Collection Development</p><p> Best Books<br /> Books News/Interviews<br /> Collection Development</p><p> Collection Development Calendar<br /> Prepub Alerts</p><p> Technology</p><p> News &amp;amp; Features<br /> Library 2.0<br /> Products/Vendors<br /> Casey/Stephens: The Transparent Library<br /> Tennant: Digital Libraries<br /> Tenopir: Online DB</p><p> Careers</p><p> News &amp;amp; Features</p><p> Education/ Training<br /> Job Zone</p><p> New Librarians<br /> Salaries</p><p> Blogs</p><p> Bubble Room<br /> Annoyed Librarian</p><p> Digital Libraries<br /> E-Views</p><p> Games, Gamers, &amp;amp; Gaming</p><p> In the Bookroom<br /> LJ Insider<br /> PrePub Alert</p><p> ShelfRenewal<br /> All Blogs</p><p> Tools</p><p> Annual Articles &amp;amp; Awards</p><p> Webcast<br /> ebook Summit</p><p> Submit to LJ</p><p> Articles<br /> News, Photos, Feedback<br /> Architectural Issue<br /> Awards<br /> Movers &amp;amp; Shakers</p><p> Titles for Review<br /> Review for LJ</p><p>Any time<br />Past 24 hours<br />Past week<br />Past 2 weeks<br />Past month<br />Past 2 months<br />Past 6 months<br />Past year<br />Past 2 years<br />Past 5 years<br />Past 10 years</p><p> try {<br /> var qdr = /[?&amp;]as_qdr=([^&amp;]*)/<br /> .exec(window.location.search)[1];<br /> var opts = document<br /> .getElementsByName(&quot;as_qdr&quot;)[0]<br /> .getElementsByTagName(&quot;option&quot;);<br /> for (var i = 0; i &lt; opts.length; i++)<br /> opts[i].selected = (opts[i].value == qdr);<br /> } catch (e) {}</p><p> if (cookies_enabled){		serveAds('0','1','/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04A%15%01LJSearchButton88x31%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013chf2ush00%08%01866226%02%04%02%04','&amp;lt;iframe src = &amp;quot;/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04A%15%01LJSearchButton88x31%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013chf2ush00%08%01866226%02%04%02%04&amp;amp;noscript=1&amp;quot;  height=&amp;quot;31px&amp;quot;  width=&amp;quot;88px&amp;quot;  frameborder=&amp;quot;0&amp;quot; scrolling=&amp;quot;no&amp;quot; vspace=&amp;quot;0&amp;quot; style=&amp;quot;left: -1pt; position: relative; top: -2pt;&amp;quot; marginwidth=&amp;quot;0&amp;quot; marginheight=&amp;quot;0&amp;quot; hspace=&amp;quot;0&amp;quot; allowtransparency=&amp;quot;true&amp;quot; &amp;gt;&amp;lt;/iframe&amp;gt;','LJSearchButton88x31','65');	}</p><p> if (cookies_enabled){		serveAds('0','1','/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04C%12%01LJTickerAd983x25%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013chf2ush00%08%01866226%02%04%02%04','&amp;lt;iframe src = &amp;quot;/csp/cms/sites/LJ/Reviews/Book/dt.cms.ad.page.GetAdArea.cls?params=%03%04C%12%01LJTickerAd983x25%04%01LJ%06%01Book%08%01mobile%03%04%01%02%04%0C%013chf2ush00%08%01866226%02%04%02%04&amp;amp;noscript=1&amp;quot;  height=&amp;quot;25px&amp;quot;  width=&amp;quot;983px&amp;quot;  frameborder=&amp;quot;0&amp;quot; scrolling=&amp;quot;no&amp;quot; vspace=&amp;quot;0&amp;quot; style=&amp;quot;left: -1pt; position: relative; top: -2pt;&amp;quot; marginwidth=&amp;quot;0&amp;quot; marginheight=&amp;quot;0&amp;quot; hspace=&amp;quot;0&amp;quot; allowtransparency=&amp;quot;true&amp;quot; &amp;gt;&amp;lt;/iframe&amp;gt;','LJTickerAd983x25','67');	}</p><p> function doLog(logStatement){}</p><p> var cookies_enabled = false;<br /> function dti_ad_area_HTMLDecode(textToDecode)<br /> {<br /> var result = textToDecode</p><p> if (result &amp;&amp; result != '')<br /> {<br /> var amp = '&amp;';<br /> var gt = '&gt;';<br /> var lt = ' 0)<br /> {<br /> t=setTimeout(&quot;serveAds(&quot;+ refreshAdRate + &quot;, &quot; + numSlots + &quot;, '&quot; + encodedURL + &quot;', '&quot; + noScriptContents + &quot;', '&quot;+ areaName + &quot;', '&quot; + theId + &quot;')&quot;, refreshAdRate * 1000);<br /> }<br /> }</p><p> function doLog(logStatement){}</p><p>var gaJsHost =<sup><a href="http://dltj.org/article/the-problem-with-marc-and-aacr/#footnote_0_58" id="identifier_1_58" class="footnote-link footnote-identifier-link" title="&amp;quot;https:&amp;quot; == document.location.protocol) ? &amp;quot;https://ssl.&amp;quot; : &amp;quot;http://www.&amp;quot;);document.write(unescape(&amp;quot;%3Cscript src=&#039;&amp;quot; + gaJsHost + &amp;quot;google-analytics.com/ga.js&#039; type=&#039;text/javascript&#039;%3E%3C/script%3E&amp;quot;">1</a></sup>;</p><p>try {<br />var pageTracker = _gat._getTracker(&quot;UA-16323142-1&quot;);<br />pageTracker._setDomainName(&quot;.libraryjournal.com&quot;);</p><p>pageTracker._trackPageview();<br />} catch(err) {}</p><p>GS_googleAddAdSenseService(&quot;ca-pub-1872221973353849&quot;);<br />GS_googleEnableAllServices();</p><p>GA_googleAddSlot(&quot;ca-pub-1872221973353849&quot;, &quot;LJ_160x160_B&quot;);</p><p>GA_googleFetchAds();</p><p>Articles">announcement of Henriette Avram passing</a>: &#8220;Though Avram was a systems analyst by training, not a librarian, her work &#8230; revolutionized access to library materials.&#8221;  Right on the mark.  With that background in computer science I&#8217;d like to think I have a somewhat unique (or at least minority) perspective on Avram&#8217;s and Gorman&#8217;s work.  They did what they did in a world with the twin challenges of expensive computing cycles and scarce storage.  MARC and AACR were created when punch cards and 9-track tapes ruled the world and computers took up rooms.  (Wanted one for your desk? Hah!)</p><p>Fast forward to today.  Computer cycles are so cheap that we stack CPUs in huge racks to collectively work on solving a problem. Storage is so cheap that we consider a verbose, ASCII-based markup language (a.k.a. &#8220;XML&#8221;) as the state of the art in the transmission of data. Compare the information density of 1000 characters of MARC versus 1000 characters of XML. And more to the point, let&#8217;s not forget AACR where every colon, period, and dash carries meaning versus the explicit description of attributes in XML. Example? Look at</p><div style="margin-left: 2em; font-family: monospace;">300&nbsp;&nbsp;&nbsp;&nbsp;|a1 v. (unpaged) : |bill. (some col.) ;|c26 cm.</div><p>versus</p><div style="margin-left: 2em; font-family: monospace;">&lt;datafield tag=&#8221;300&#8243; ind1=&#8221; &#8221; ind2=&#8221; &#8220;&gt;<br />&nbsp;&nbsp;&lt;subfield code=&#8221;a&#8221;&gt;1 v. (unpaged) :&lt;/subfield&gt;<br />&nbsp;&nbsp;&lt;subfield code=&#8221;b&#8221;&gt;ill. (some col.) ;&lt;/subfield&gt;<br />&nbsp;&nbsp;&lt;subfield code=&#8221;c&#8221;&gt;26 cm.&lt;/subfield&gt;<br />&lt;/datafield&gt;</div><p>See what I mean? The first is 51 characters, more or less, and the second is 185 characters. Now I&#8217;d argue that the second is not much more expressive than the first. (The second is MARCXML &#8212; a raw translation of the MARC record format to XML.) But take a look at this more mainstream XML format (from MODS):</p><div style="margin-left: 2em; font-family: monospace;">&lt;subject authority=&#8221;lcsh&#8221;&gt;<br />&nbsp;&nbsp;&lt;geographic&gt;United States&lt;/geographic&gt;<br />&nbsp;&nbsp;&lt;topic&gt;Politics and government&lt;/topic&gt;<br />&nbsp;&nbsp;&lt;temporal&gt;20th century.&lt;/temporal&gt;<br />&lt;/subject&gt;</div><p>A human can read and understand that as well as being parsable by a computer.</p><p>Now anyone that would have proposed the second or third of these examples in the 1960s or 1970s would have been laughed out of the machine room and told never to come back. Sure, you could write a computer program back then to read and write those XML-based formats, but it would have been so computationally- and storage-expensive that it would never have been taken seriously, much less actually contribute to the spread of machine-based cataloging tools.</p><p>So back to this decade, when storage is cheap and computer processing power even cheaper. Interoperability with other systems outside the library domain is more and more important. There is a computer on every desk&#8230;and one in your pocket. The user is empowered with a combination of better human/machine interfaces (we&#8217;ve exchanged punch cards for keyboards, mice and graphical user interfaces) and inexpensive communication mechanisms (that make machine-aided tagging and recommendation engines possible).</p><p>I&#8217;ve never met Ms. Avram, nor have I followed her work (and in fact I didn&#8217;t know of her connection to MARC until this announcement), but I wonder what she would think of the MARC/AACR combination now.  Given her training in systems analysis, would she say we are making the best use of computing technology today?</p><p>Is this the death knell for the librarian? Not necessarily. If the profession continues to train and promote the librarian of the 1960s, 70s and 80s, then yes. If that librarian is one that recognizes the shift to user-empowered technology in the past decade, nebulously characterized as &#8220;Library 2.0&#8243;, then we have a valuable value-added role to play in the information-seeking and -use activities of citizens in this new world.  Are our users disco dancing?  If not, we&#8217;d better figure out how they are dancing now&#8230;<p style="padding:0;margin:0;font-style:italic;">The text was modified to update a link from http://lisnews.org/article.pl?sid=06/05/13/1719246 to http://lisnews.org/node/26973 on January 13th, 2011.</p><h2>Footnotes</h2><ol class="footnotes"><li id="footnote_0_58" class="footnote">&quot;https:&quot; == document.location.protocol) ? &quot;https://ssl.&quot; : &quot;http://www.&quot;);<br />document.write(unescape(&quot;%3Cscript src='&quot; + gaJsHost + &quot;google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E&quot;</li></ol>]]></content:encoded> <wfw:commentRss>http://dltj.org/article/the-problem-with-marc-and-aacr/feed/</wfw:commentRss> <slash:comments>7</slash:comments> </item> </channel> </rss>
<!-- Served from: dltj.org @ 2012-02-11 08:55:37 by W3 Total Cache -->
