<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Metalogue</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/" />
    <link rel="self" type="application/atom+xml" href="http://community.oclc.org/metalogue/atom.xml" />
    <id>tag:community.oclc.org,2008-06-05:/metalogue/1</id>
    <updated>2009-05-01T21:08:02Z</updated>
    <subtitle>new directions in cataloguing and metadata from around the world</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.23-en</generator>

<entry>
    <title>Remixing Data at ELAG</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2009/05/remixing-data-at-elag.html" />
    <id>tag:community.oclc.org,2009:/metalogue//1.37</id>

    <published>2009-05-01T20:22:50Z</published>
    <updated>2009-05-01T21:08:02Z</updated>

    <summary><![CDATA[ ELAG&nbsp; 2009 - Metadata highlights, by Janifer Gatenby &nbsp; This year's ELAG (European Library Automation Group) was held at the culturally and historically important University Library in Bratislava, Slovak Republic, located in the heart of old Bratislava.&nbsp; The title...]]></summary>
    <author>
        <name>Karen Calhoun</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[<span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: NL; mso-bidi-language: AR-SA"><font color="#000000">
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><b style="mso-bidi-font-weight: normal"><span style="FONT-FAMILY: Calibri; mso-ansi-language: EN-US; mso-bidi-font-size: 11.0pt">ELAG<span style="mso-spacerun: yes">&nbsp; </span>2009 - Metadata highlights</span></b><span style="FONT-FAMILY: Calibri; mso-ansi-language: EN-US; mso-bidi-font-size: 11.0pt">, <i style="mso-bidi-font-style: normal">by Janifer Gatenby<o:p></o:p></i></span></p>
<p>&nbsp;</p>
<p>This year's ELAG (<a href="http://www.elag.org/">European Library Automation Group</a>) <span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: NL; mso-bidi-language: AR-SA">was held at the culturally and historically important University Library in Bratislava, Slovak Republic, located in the heart of old Bratislava.<span style="mso-spacerun: yes">&nbsp; </span>The title of ELAG's 33<sup>rd</sup> seminar was "<b style="mso-bidi-font-weight: normal">New Tools of the Trade"</b> and the conference was full of stimulating and relevant content, with a focus on re-mixing data.</span></p>
<p><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">Map metadata is going to get much easier to create and much richer.<span style="mso-spacerun: yes">&nbsp; </span>Petr Zabicka and Petr Pridal from the Moravian Library in Bruno, Czech Republic,<span style="mso-spacerun: yes">&nbsp; </span>introducted us to their web site <a href="http://www.oldmapsonline.org/">oldmapsonline</a>&nbsp;<span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">where there are open source tools for the scanning, metadata creation and adding geo references to maps.<span style="mso-spacerun: yes">&nbsp; </span>Their open source <a href="http://www.maptiler.org/">Map tiler</a>&nbsp;<span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">provides an easy interface for assigning a geo bounding box that makes the map compatible with Google maps so that maps can be overlaid, e.g. for "then and now" comparisons. Geo coordinates are more important than traditional access points for searching maps.<span style="mso-spacerun: yes">&nbsp; </span>They also recommend<span style="mso-spacerun: yes">&nbsp; </span><a href="http://www.zoomify.com/">zoomify</a>&nbsp;which zooms any image.</span></span></span></span></p>
<p><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">To open the main theme of the conference, Karen Coombs gave a rich key note address and animated the mash up work shop. Check her <a href="http://www.slideshare.net/librarywebchic/elag-mashing-up-and-remixing-the-library-website-1333496">presentation</a>&nbsp;and her <a href="http://sites.google.com/site/elag09mashupworkshop/">workshop notes</a>, both of which are full of useful examples and tips. </span></span></span></span></span></p>
<p><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">Table of content metadata is being harvested and made available for reuse.<span style="mso-spacerun: yes">&nbsp; </span>This was reported by Lisa Rogers from Heriot-Watt University in the UK with her <a href="http://indico.ulib.sk/MaKaC/contributionDisplay.py?contribId=21&amp;confId=5">overview of TicTocs and Golddust</a>. <a href="http://www.tictocs.ac.uk/">TicTocs </a><span lang="NL" style="FONT-FAMILY: Calibri; mso-bidi-font-size: 11.0pt">aggregates RSS feeds from more than 12,000 journals and then makes a data set available for mash up.<span style="mso-spacerun: yes">&nbsp;<a href="http://internal.ulib.sk/indico/elag/prezentacie/van_boheemenl.pdf"> </a></span><a href="http://internal.ulib.sk/indico/elag/prezentacie/van_boheemenl.pdf">Peter </a></span><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><a href="http://internal.ulib.sk/indico/elag/prezentacie/van_boheemenl.pdf">Van Bohemen </a><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">from Wageningen University has made very rapid use of this service to display the contents of the lastest issue of a journal when a full record display of a serial is requested in the Wageningen union catalogue. <span style="mso-spacerun: yes">&nbsp;</span>Gold dust is an SDI service using Tictocs and user profiles.<span style="mso-spacerun: yes">&nbsp; </span></span></span></span></span></span></span></span></span></p>
<p><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="mso-spacerun: yes"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">There were two reports on systems with a new approach to the generation of recommender data.<span style="mso-spacerun: yes">&nbsp; </span>Marcus Spiering of the University of Karlsruhe reported on <a href="http://indico.ulib.sk/MaKaC/contributionDisplay.py?contribId=18&amp;confId=5">Bibtip</a>, <span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">which is a recommender system based on evidence from an anonymous session based cookie that looks for "co-inspections" (full record views).&nbsp; This metadata is harvested from the usage information collected from a library's online catalogue and thus it works for all material represented in the catalogue.<span style="mso-spacerun: yes">&nbsp; </span>This contrasts with recommender systems based on circulation based usage which only look at the physical collection and systems based on resolver usage which only look at electronic material.<span style="mso-spacerun: yes">&nbsp; </span>Tamar Sadeh from ExLibris announced <a href="http://internal.ulib.sk/indico/elag/prezentacie/sadeh.pdf">bX</a>, a journal article recommender system based on traffic from harvested logs from SFX resolvers. <span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">It also looks for "co-inspections" within a session and is based on research from Herbert van de Sompel's Los Alamos lab.<span style="mso-spacerun: yes">&nbsp; </span>ExLibris will be running this as a chargeable web service. </span></span></span></span></span></span></span></span></span></span></span></span></p>
<p><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="mso-spacerun: yes"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">Thom Hickey and I gave a presentation entitled <a href="http://indico.ulib.sk/MaKaC/contributionDisplay.py?contribId=27&amp;confId=5">"Opening Library Data for Web </a></span><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><a href="http://indico.ulib.sk/MaKaC/contributionDisplay.py?contribId=27&amp;confId=5">Scale and Re-mixing" </a>. <span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">Tom talked about our data resources and how OCLC is both growing and enriching them, with examples from WorldCat Identities and VIAF.<span style="mso-spacerun: yes">&nbsp; </span>I stressed the importance of identifiers in re-mixing data, alluding to GLIMIR (Global Library Manifestation Identifier:<span style="mso-spacerun: yes">&nbsp; </span>see <a href="http://community.oclc.org/metalogue/archives/2008/08/the-importance-of-identifiers.html">my post in January 2009 on the importance of identifiers</a>) <span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">and presented an outline of OCLC's identifier services and data APIs.<span style="mso-spacerun: yes">&nbsp; </span>From <span style="COLOR: black">the discussion that ensued, we gathered that work identifier services are in demand. Increasingly, metadata specialists are recognizing the importance of manifestation level identifiers as well.<span style="mso-spacerun: yes">&nbsp; </span>See, for example, the <a href="http://bibwild.wordpress.com/2009/04/28/oclc-numbers-as-manifestation-identifiers/">post this week by Jonathan Rochkind</a>.</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></p>
<p><span style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="mso-spacerun: yes"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="COLOR: black"><span lang="NL" style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri; LETTER-SPACING: 0.2pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Arial; mso-ansi-language: NL; mso-fareast-language: NL; mso-bidi-language: AR-SA">I've given here an overview of just some of the presentations that are particularly relevant to metadata.<span style="mso-spacerun: yes">&nbsp; </span>There were other excellent contributions which can be found on the <a href="http://indico.ulib.sk/MaKaC/conferenceTimeTable.py?confId=5">seminar web site.</a></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></font></span></p>]]>
        
    </content>
</entry>

<entry>
    <title>Special Delivery</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2009/04/special-delivery.html" />
    <id>tag:community.oclc.org,2009:/metalogue//1.36</id>

    <published>2009-04-23T02:38:39Z</published>
    <updated>2009-04-23T19:01:05Z</updated>

    <summary>The catalog-centric model of library use is pretty straightforward. A user consults a shelf list (most likely through a topic, author, or title index), takes note of a shelf location, and then goes physically to that location to find the...</summary>
    <author>
        <name>John Chapman</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[The catalog-centric model of library use is pretty straightforward. A user consults a shelf list (most likely through a topic, author, or title index), takes note of a shelf location, and then goes physically to that location to find the resource. The networked world has changed certain dynamics of this model, most notably the depth and accessibility of the indexes, but the model of delivery - the last step described above - has really fundamentally changed only very recently. One of OCLC's strategic moves has been to collect and provide holdings data, so that libraries can share in the strength of a unified catalog while still providing local utility to users seeking a physical resource.<br /><br />However, in research, or where known-item searching is not the norm, there is one step remaining. Once the user has access to the contents of the resource, there is an evaluation process: "Will this suit my needs, or should I look for something else?" In full-text environments, this rapid compression of the time required for the delivery and evaluation phases is substantial. Accordingly, the delays to the evaluation phase in the traditional library delivery model are increasingly unacceptable to our users. <br /><br />A newly available study on WorldCat data quality, OCLC's "Online Catalogs: What Users and Librarians Want" [<a href="http://www.oclc.org/us/en/reports/onlinecatalogs/default.htm">http://www.oclc.org/us/en/reports/onlinecatalogs/default.htm</a>] suggests that the user seeks above all not rich bibliographic information but rich availability data and evaluative information. Libraries have not traditionally provided evaluative materials to their users in systematic ways; however, they have maintained such aids (book review indexes, etc.) for expert users and for collection development purposes. <br /><br />The newest mode of providing evaluative content is a game-changer: the provision of full text.&nbsp; Aggressive moves by for-profit companies in the digitized full-text market are no secret. They bear none of the costs or scarcities of delivering physical books, instead delivering texts. From the user side, the entire process of determining suitability-of use is extremely foreshortened. <br /><br />As the research and evaluation process is further influenced by the availability of full text, libraries will need to pay attention to the most user-friendly and popular methods of accessing these texts and provide helpful links to them from their discovery tools. (Libraries have some relevant experience with this in the area of referring users to licensed content through link resolution.) The successful integration and synthesis of multiple types of evaluative information is a central challenge.<br /><br />Popular alternative discovery platforms for information resources (Amazon, tagged personal collections, etc), in addition to using simple holdings and/or sales data, tables of content, and reviews, have approached the evaluation problem in new ways.&nbsp; One is subcollections - either curated actively or casually through tagging. Another is leveraging user-behavior data such as browsing behavior or "fulfillment" - circulation or purchase. OCLC's new record display in worldcat.org (and WorldCat Local) uses a variety of tools, including user reviews and behavior data, to provide evaluative information. For an example, see <a href="http://www.worldcat.org/oclc/61479616">http://www.worldcat.org/oclc/61479616</a> . <br /><br />OCLC will continue to develop and leverage internal systems and to seek out external providers of licensed content to enhance the evaluative richness of WorldCat. We invite you to share your thoughts on the new record display.<br /><br /> ]]>
        
    </content>
</entry>

<entry>
    <title>Online Catalogs: What Users and Librarians Want</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2009/04/online-catalogs-what-users-and.html" />
    <id>tag:community.oclc.org,2009:/metalogue//1.35</id>

    <published>2009-04-21T21:31:51Z</published>
    <updated>2009-04-21T21:37:04Z</updated>

    <summary>In my November 24, 2008 post to this blog, I alluded to a research project examining what is most important about WorldCat metadata to a range of audiences, both end users and librarians. My research team and I have now...</summary>
    <author>
        <name>Karen Calhoun</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[In my <a href="http://community.oclc.org/metalogue/archives/2008/11/a-multilayered-view-of-quality.html">November 24, 2008 post </a>to this blog, I alluded to a research project examining what is most important about WorldCat metadata to a range of audiences, both end users and librarians. My research team and I have now published the findings that are likely to be relevant to library catalogs in general. Our report, <em>Online Catalogs: What Users and Librarians Want</em>, is available as a freely downloadable PDF from <a href="http://www.oclc.org/us/en/reports/default.htm">http://www.oclc.org/us/en/reports/default.htm</a>.&nbsp; There is also an executive summary. Your comments are welcome.]]>
        
    </content>
</entry>

<entry>
    <title>More on the Expert Community Experiment</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2009/03/more-on-the-expert-community-e.html" />
    <id>tag:community.oclc.org,2009:/metalogue//1.34</id>

    <published>2009-03-19T21:33:33Z</published>
    <updated>2009-03-19T22:46:44Z</updated>

    <summary><![CDATA[In a Feb. 12 entry on this blog, we announced OCLC's Expert Community Experiment, which creates a wiki-like environment around WorldCat cataloging records so that anyone with an OCLC&nbsp;full cataloging authorization can participate in making records better. The experiment began...]]></summary>
    <author>
        <name>Karen Calhoun</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[<p>In a Feb. 12 entry on this blog, we announced OCLC's Expert Community Experiment, which creates a wiki-like environment around WorldCat cataloging records so that anyone with an OCLC&nbsp;full cataloging authorization can participate in making records better. The experiment began the week of February 16; it will&nbsp;continue for 6 months. To participate, you need nothing besides your OCLC full level cataloging authorization. More information is available on the <a href="http://www.oclc.org/us/en/worldcat/catalog/quality/expert/default.htm">Expert Community Web pages.</a></p>
<p>A month into the experiment, I thought there might be intereest in&nbsp;an update on participation.&nbsp; Registration for the Expert Community Webinars is breaking OCLC records for participation in our webinars--more than 900 sites participated in the four sessions offered in February.&nbsp;If you missed these, there is <a href="https://www3.oclc.org/app/request/bin/request.asp?specialCode=ECE09Mar24">another&nbsp;Webinar on March 24 </a>for which you can register.&nbsp;Alternatively, you can visit the Expert Community Web pages and click on the <a href="http://www.oclc.org/us/en/worldcat/catalog/quality/expert/default.htm">Webinar recording </a>available in the right frame. &nbsp;</p>
<p>Here are some statistics that suggest that the OCLC cataloging community is becoming more engaged in collectively&nbsp;improving WorldCat.&nbsp;The statistics compare master record improvements during the first four weeks of Expert Community Experiment activity with&nbsp;improvements made one year ago (March 2008).</p>
<p>
<span class="mt-enclosure mt-enclosure-image" style="DISPLAY: inline">&nbsp;</span>
<span class="mt-enclosure mt-enclosure-image" style="DISPLAY: inline"><img class="mt-image-none" height="178" alt="Expert Community Stats March 2009.jpg" src="http://community.oclc.org/metalogue/Expert%20Community%20Stats%20March%202009.jpg" width="411" /></span>&nbsp;</p>
<p>Besides the brand new Expert Community updates to master records, it seems possible that the experiment is yielding&nbsp;an uplift in database enrichments and minimal-level upgrades as well.&nbsp;</p>
<p>&nbsp;</p>]]>
        
    </content>
</entry>

<entry>
    <title>The Macroscopic View</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2009/03/the-macroscopic-view.html" />
    <id>tag:community.oclc.org,2009:/metalogue//1.33</id>

    <published>2009-03-17T13:54:30Z</published>
    <updated>2009-03-17T13:57:47Z</updated>

    <summary><![CDATA[Macros are an important part of the toolkit for those that work on large datasets. The size and scope of the WorldCat database has encouraged the development of a number of scripts designed to normalize, translate, and transform.&nbsp; Some of...]]></summary>
    <author>
        <name>John Chapman</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[Macros are an important part of the toolkit for those that work on large datasets. The size and scope of the WorldCat database has encouraged the development of a number of scripts designed to normalize, translate, and transform.&nbsp; Some of these tools are used internally by OCLC staff to clean up errors; others are shared among the cooperative and the cataloging world.<br /><br />Robert Bremer is one of the OCLC staff that makes extensive use of macros. He showed me one of the more complex ones that cleans up common errors in the bibliographic data that gets uploaded to WorldCat. One of the most common types of errors that he must deal with is that of text that the cataloger types in "freehand" in fields like the 504 ‡a (bibliography note, i.e. "Includes bibliographic references.") The logical thing here would be for the cataloger to have a macro to insert this text (and to use it) every time the situation arises; but the use and utility of macros among the cataloging population is uneven.<br /><br />Although OCLC can and will continue to correct a wide range of errors arising from multiple sources, some macros are most beneficial at the local level. The OCLC cooperative has long benefited from the work of individuals who have sought to share their macro insights. Joel Hahn's "Better Living through Macros" should be of interest to those looking for an introduction: http://www.hahnlibrary.net/libraries/oml/index.html.&nbsp; A more advanced perspective is at Harvey E. Hahn's "OML Macros" page (<a href="http://www.ahml.info/oml/">http://www.ahml.info/oml/</a>). <br />Walt Nickerson maintains a collection of macros at <a href="http://docushare.lib.rochester.edu/docushare/dsweb/View/Collection-2556">http://docushare.lib.rochester.edu/docushare/dsweb/View/Collection-2556</a>.<br /><br />The main Connexion macros page (<a href="http://www.oclc.org/connexion/support/macros.htm">http://www.oclc.org/connexion/support/macros.htm</a>) has links to these resources and a few more, including lessons for learning how to create and use macros. <br /><br />I urge you to look at what is available, see if it makes sense for your organization, and to let us know how we can help the cataloging community in creating new macro resources.<br /><br /><br /> ]]>
        
    </content>
</entry>

<entry>
    <title>The Expert Community Experiment - and Finding Community Experts</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2009/02/the-expert-community---and-fin.html" />
    <id>tag:community.oclc.org,2009:/metalogue//1.32</id>

    <published>2009-02-12T18:00:00Z</published>
    <updated>2009-02-12T03:19:45Z</updated>

    <summary><![CDATA[Yesterday, Mary Ann Laun, chair of OCLC's Members Council Cataloging &amp; Metadata Service Group, led their session as part of OCLC's February virtual meeting of Members Council [http://www.oclc.org/us/en/memberscouncil/meetings/2009/february/2009februaryagenda.pdf].&nbsp; The session covered two topics: OCLC's Expert Community Experiment, and the results...]]></summary>
    <author>
        <name>John Chapman</name>
        
    </author>
    
    <category term="expertcommunity" label="Expert Community" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="memberscouncil" label="Members Council" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[Yesterday, Mary Ann Laun, chair of OCLC's Members Council Cataloging &amp; Metadata Service Group, led their session as part of OCLC's February virtual meeting of Members Council [http://www.oclc.org/us/en/memberscouncil/meetings/2009/february/2009februaryagenda.pdf].&nbsp; The session covered two topics: OCLC's Expert Community Experiment, and the results of a survey of technical services staff.&nbsp; I thought both topics would be of keen interest to Metalogue readers. <br /><br />OCLC's Expert Community Experiment creates a wiki-like environment around WorldCat cataloging records so that anyone with a full cataloging authorization can participate in making records better. The experiment will begin the week of February 16, and will continue for 6 months. No change or signup is required at the institution end - if you have a full cataloging authorization, you will see these changes automatically. We encourage you to discuss and ask questions on the OCLC-CAT listserv [<a href="https://www3.oclc.org/app/listserv/">https://www3.oclc.org/app/listserv/</a>] and OCLC staff will be monitoring ASKQC@oclc.org if you want to ask a private question. More information, including a schedule for upcoming webinars, can be found at the Expert Community page: <a href="http://www.oclc.org/us/en/worldcat/catalog/quality/expert/default.htm">http://www.oclc.org/us/en/worldcat/catalog/quality/expert/default.htm</a>. <br /><br />Last fall, the OCLC Members Council Cataloging and Metadata Service Group conducted a survey of Members Council delegates and OCLC-CAT listserv readers about issues facing technical services departments. Here are the top three issues selected by respondents to the survey:<br /><br /><ol><li>training in Next Generation concepts </li><li>creating new skills sets (what are they and how do we build them)</li><li>transitioning from traditional duties to new ones</li></ol><br />Yesterday, OCLC staff were asked how they might assist the technical services community in addressing these issues.&nbsp; We would like to begin our exploration of ways in which OCLC might partner with other appropriate individuals and groups by asking readers of Metalogue to answer a couple of questions.&nbsp; Please make your comments on this blog post; they will be most appreciated. Thanks in advance for your thoughts.<br /><br /><ul><li><font style="font-size: 1.25em;"><b>What do "Next Generation concepts" mean to you? Which of these are particularly relevant to technical services staff?</b></font></li></ul><ul><li><font style="font-size: 1.25em;"><b>What groups or individuals do you know of in the technical services community who are supplying this sort of training, assessment, and transition assistance?</b></font></li></ul><br /> ]]>
        
    </content>
</entry>

<entry>
    <title>How to Communicate with the OCLC Review Board on the Principles of Shared Data Creation and Stewardship</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2009/02/how-to-communicate-with-the-oc.html" />
    <id>tag:community.oclc.org,2009:/metalogue//1.31</id>

    <published>2009-02-11T20:02:51Z</published>
    <updated>2009-02-11T20:08:17Z</updated>

    <summary><![CDATA[Just a quick note to let readers know how to track the progress of and submit feedback to the newly announced Review Board on the Principles of Shared Data Creation and Stewardship. URL of Review Board page: http://www.oclc.org/us/en/worldcat/catalog/policy/board/default.htm &nbsp; Online...]]></summary>
    <author>
        <name>Karen Calhoun</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[<p>Just a quick note to let readers know how to track the progress of and submit feedback to the <a href="http://www.oclc.org/us/en/news/releases/200910.htm">newly announced Review Board on the Principles of Shared Data Creation and Stewardship</a>.</p>
<div><span class="185574519-11022009"><font face="Arial" color="#0000ff" size="2">URL of Review Board page: <a title="blocked::http://www.oclc.org/us/en/worldcat/catalog/policy/board/default.htm" href="http://www.oclc.org/us/en/worldcat/catalog/policy/board/default.htm">http://www.oclc.org/us/en/worldcat/catalog/policy/board/default.htm</a></font></span></div>
<div dir="ltr" align="left"><span class="185574519-11022009"><font face="Arial" color="#0000ff" size="2"></font></span>&nbsp;</div>
<div dir="ltr" align="left"><span class="185574519-11022009"><font face="Arial" color="#0000ff" size="2">Online feedback forum (blog): <a title="blocked::http://community.oclc.org/reviewboard/" href="http://community.oclc.org/reviewboard/">http://community.oclc.org/reviewboard/</a></font></span></div>
<div dir="ltr" align="left"><span class="185574519-11022009"></span><span class="185574519-11022009"><font face="Arial" color="#0000ff" size="2"></font></span>&nbsp;</div>
<div dir="ltr" align="left"><span class="185574519-11022009"><font face="Arial" color="#0000ff" size="2">Email:&nbsp; <a title="blocked::mailto:reviewboard@oclc.org" href="mailto:reviewboard@oclc.org">reviewboard@oclc.org</a></font></span></div>
<div><font face="Arial" color="#0000ff" size="2"></font>&nbsp;</div>
<div>The group is chaired by Jennifer Younger, university librarian at the University of Notre Dame and an OCLC Members Council delegate.</div>
<div>&nbsp;</div>
<p>&nbsp;</p>]]>
        
    </content>
</entry>

<entry>
    <title>Guardian Posts Corrections to Article on OCLC and Record Use Policy</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2009/01/guardian-posts-corrections-to.html" />
    <id>tag:community.oclc.org,2009:/metalogue//1.30</id>

    <published>2009-01-31T13:34:29Z</published>
    <updated>2009-01-31T14:30:04Z</updated>

    <summary>The Guardian, a prominent UK newspaper, has published corrections to its article of January 22 in response to objections that OCLC communicated to the Guardian last week. The Guardian&apos;s corrections were published today and may be viewed in its &quot;Corrections...</summary>
    <author>
        <name>Karen Calhoun</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[<p>The Guardian, a prominent UK newspaper, has published corrections to its article of January 22 in response to objections that OCLC communicated to the Guardian last week. The <a href="http://www.guardian.co.uk/theguardian/2009/jan/31/corrections">Guardian's corrections </a>were published today and may be viewed in its "Corrections and Clarifications" page or at the beginning of&nbsp;the original article. </p>
<p>The January 22 article in the Guardian is built around what OCLC regards as a false premise (that OCLC reduces libraries' visibility on the Web). It states that OCLC shares "only 3 million" records with Google Books. This is not the case. OCLC shares nearly all of the database with Google Books and Google Scholar, with the exception being a relatively small amount of data that OCLC is contractually prohibited from sharing. This allows the "find in a library" links to be placed in those services, which drives traffic back to thousands of OCLC member libraries through WorldCat.org.&nbsp; </p>
<p>It is true that Google indexes only a subset of WorldCat records in the main index. This arrangement is based on advice from Google and is constantly reviewed. Based on recent exchanges we will move to a much more extensive crawl of the WorldCat database soon (while honoring the restrictions on some data sets that OCLC licenses from third parties).</p>
<p>What does not come across clearly in the article is that OCLC has for some time made&nbsp;WorldCat.org, the largest database&nbsp;in the world that represents library collections, freely available for searching on the Web, and that this allows people everywhere to do research and be connected to libraries.&nbsp;</p>
<p>As has been discussed on this blog and elsewhere, we know that WorldCat.org can be substantially improved, and OCLC is working hard to improve the links and make&nbsp;more libraries' collections visible. </p>
<p>The statement issued by the Guardian today addresses&nbsp;some other ways in which the article misrepresents OCLC and its&nbsp;revised record use policy. </p>
<p>As you may know,&nbsp;OCLC Members Council and the OCLC Board of Trustees have&nbsp;jointly convened a <a href="http://www.oclc.org/news/releases/20092.htm">Review Board of Shared Data Creation and Stewardship </a>to represent the membership and inform OCLC on the principles and best practices for sharing library data. The group will discuss the revised record use policy with OCLC members and other key stakeholders.&nbsp;Please watch for announcements of how to provide your input.&nbsp;&nbsp;In the meantime, comments and questions are&nbsp;invited at <a href="mailto:recorduse@oclc.org">recorduse@oclc.org</a>. &nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>]]>
        
    </content>
</entry>

<entry>
    <title>Data Sharing, Libraries, and the Landscape of the Web</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2009/01/data-sharing-libraries-and-the.html" />
    <id>tag:community.oclc.org,2009:/metalogue//1.29</id>

    <published>2009-01-28T01:41:30Z</published>
    <updated>2009-01-28T18:03:57Z</updated>

    <summary><![CDATA[On Monday I had the opportunity to speak in Denver at the ALCTS Forum "Creating and Sustaining Communities around Shared Library Data."&nbsp; LJ's Norman Oder provides a&nbsp;substantive, fair summary of the 2-hour session.&nbsp; For those with an interest I've made...]]></summary>
    <author>
        <name>Karen Calhoun</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[<p><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">On Monday I had the opportunity to speak in <st1:City w:st="on"><st1:place w:st="on">Denver</st1:place></st1:City> at the ALCTS Forum "Creating and Sustaining Communities around Shared Library Data."<span style="mso-spacerun: yes">&nbsp; LJ's Norman Oder provides a&nbsp;substantive, fair <a href="http://www.libraryjournal.com/article/CA6632413.html?desc=topstory">summary</a> of the 2-hour session.&nbsp; For those with an interest I've made <a href="http://www.slideshare.net/amarintha/creating-and-sustaining-communities-around-shared-data-the-case-of-oclc-presentation">my slides </a>available on SlideShare.&nbsp;&nbsp;</span></span></p>
<p><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA"><span style="mso-spacerun: yes"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">I found the panel presentations and discussion with attendees constructive and helpful. I took quite a few notes so there is much to ponder. Besides sharing the URL of the slides, I thought I would also&nbsp;offer some thoughts about one of the topics that occupied the speakers and audience briefly, the role and significance of <a href="http://worldcat.org/">WorldCat.org</a>.</span></span></span></p><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA"><span style="mso-spacerun: yes"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">
<p style="BACKGROUND: white"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times">One speaker at the Forum wondered about the need for WorldCat.org as an aggregation of information about library collections.<span style="mso-spacerun: yes">&nbsp; </span>From a different source this past week, I have heard OCLC's commitment to&nbsp;comprehensiveness&nbsp;in&nbsp;WorldCat.org misrepresented as an aspiration to monopoly standing in the library world. </span><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times">While the OCLC database is the largest of its type and in some way serves&nbsp;around 69,000 libraries in 112 countries, considering the number of libraries in the world and&nbsp;the number&nbsp;of&nbsp;cooperative services/catalogs they use, such a notion&nbsp;about OCLC's purpose for WorldCat ranges from the&nbsp;misinformed (in <st1:place w:st="on">North America)</st1:place> to laughable in most other places in the world.* Instead the purpose of growing WorldCat.org is to begin attracting more attention to the world's library collections on the Web by providing a <a href="http://efoundations.typepad.com/efoundations/2009/01/why-cant-i-find-a-library-book-in-my-search-engine.html">"point of concentration" </a>to collect and drive traffic to local libraries or consortia. </span></p>
<p style="BACKGROUND: white"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times"></span><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">I would argue that WorldCat.org is a good thing for OCLC member libraries already, and it has the potential to become a great thing. It brings eyeballs to library collections both collectively and individually--attention that otherwise will remain monopolized by the most successful Websites.&nbsp;For an interesting perspective on the landscape of the Web, see the<a href="http://informationarchitects.jp/trendmap3-countdown-sneak-peak/"> map</a> <span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">that Information Architects Japan has created.&nbsp;&nbsp;IA's map overlays influential Web sites on the Tokyo-area train map.<span style="mso-spacerun: yes">&nbsp; </span></span></span></p>
<p><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA"><span style="mso-spacerun: yes"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">What IA's map tells us about libraries on the Web is not new. The loss of information seekers' attention to traditional libraries became painfully obvious four years ago when the <em><a href="http://www.oclc.org/reports/pdfs/Percept_pt1.pdf">Perceptions of Libraries </a></em><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">survey report was released, revealing how much more likely respondents were to begin a search for information with a search engine (84%) than on a local library Web site (1%) (see page 17 of 34).</span></span></span></span></span></p><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA"><span style="mso-spacerun: yes"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">
<p style="BACKGROUND: white"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times">WorldCat.org, introduced in 2006, is a response to brick-and-mortar libraries' loss of attention in the Web landscape. The strategy is to make library collections everywhere much more visible in the main stations on the Web. Today, WorldCat.org is a destination on the Web, yes. More importantly it's a "switch," driving traffic from popular Web sites like Google Book Search to 10,000 OCLC member libraries' collections.** Very recently, a switching mechanism from the Web to many OCLC member libraries has begun to work from mobile phones, as described&nbsp;in the announcement of the <a href="http://www.oclc.org/news/releases/20095.htm">WorldCat Mobile pilot</a>.<span style="mso-spacerun: yes">&nbsp; </span><o:p></o:p></span></p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">While there is plenty of work remaining to be done to consistently and reliably connect searchers from popular sites to library collections via WorldCat.org, the first hard steps have been taken, and OCLC is committed to making WorldCat.org work better for more libraries. The switching mechanism does&nbsp;work: a few months ago, a <a href="http://weblogs.hitwise.com/us-heather-hopkins/2008/10/google_books_drives_visits_to_1.html">Hitwise commentator</a>, <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">reporting on downstream websites from Google Book Search, noted that 22% of visits from Google Book Search go to an Education website, with WorldCat.org the #1 Education website. There is reason for optimism that the connections to library catalogs&nbsp;from the Google search engine via WorldCat.org will improve, based on recent exchanges between Google and OCLC.</span></span></p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">
<p style="BACKGROUND: white"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times">Going forward, for WorldCat.org to be an effective switch to libraries, it needs to be<i style="mso-bidi-font-style: normal"> </i>more <i style="mso-bidi-font-style: normal">comprehensive and connected.<span style="mso-spacerun: yes">&nbsp; </span></i>To achieve its potential to help libraries, it needs to be a "point of concentration"--a large store of information about the content and whereabouts of library collections around the world. Its links need to be embedded and more visible on more of the Web's busiest sites. In these ways, WorldCat.org can help online travelers pass through the main stations of the Web and disembark at their local libraries, wherever those libraries are, from <st1:State w:st="on">Ohio</st1:State> to <st1:City w:st="on">Oslo</st1:City> to <st1:place w:st="on">Okinawa</st1:place>. </span></p>
<p style="BACKGROUND: white"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times"></span>&nbsp;</p>
<p style="BACKGROUND: white"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times">---------------------<br />*Outsell's 2008 report estimates there are 484,990 libraries worldwide--109,795 in North America. </span></p>
<p style="BACKGROUND: white"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times"></span><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times">**<span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA">To try it out, go to Google Books and search "everything is miscellaneous," then click "find this book in a library" on the book description page. </span><br /></p></span></span></span></span></span></span></span></span>
<p><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-fareast-language: EN-US; mso-ansi-language: EN-US; mso-bidi-language: AR-SA"><span style="mso-spacerun: yes"></span></span></span></span></span></span>&nbsp;</p>]]>
        
    </content>
</entry>

<entry>
    <title>XC Report: New Directions</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2009/01/xc-report-new-directions.html" />
    <id>tag:community.oclc.org,2009:/metalogue//1.28</id>

    <published>2009-01-09T21:43:22Z</published>
    <updated>2009-01-09T21:46:24Z</updated>

    <summary><![CDATA[Jennifer Bowen and her team at the University of Rochester have published&nbsp; a white paper describing their metadata work for the eXtensible Catalog (XC) project. It is an exciting project that will reward your attention. Some of the future directions...]]></summary>
    <author>
        <name>John Chapman</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[Jennifer Bowen and her team at the University of Rochester have published&nbsp; a <a href="http://www.extensiblecatalog.org/blog/2009/01/08/new-xc-white-paper-on-metadata-now-available">white paper </a>describing their metadata work for the eXtensible Catalog (XC) project. It is an exciting project that will reward your attention. <br /><br />Some of the future directions of the project are very intriguing, and I am particularly interested to see how the XC Authority Control and Aggregation services develop. <br /><br />What is encouraging about the project is that it shows a middle way between demonization and deification of the MARC format. The project seeks to use the richness of the MARC records and put it in a context which will ease reuse and repurposing. It comes across as a measured and thoughtful reaction to the possibilities and challenges of RDA, linked data, and the new world of bibliographic metadata.&nbsp; ]]>
        
    </content>
</entry>

<entry>
    <title>Author View</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2008/12/author-view.html" />
    <id>tag:community.oclc.org,2008:/metalogue//1.27</id>

    <published>2008-12-14T20:58:55Z</published>
    <updated>2008-12-14T22:10:21Z</updated>

    <summary><![CDATA[By Janifer Gatenby &nbsp; This entry was contributed by my colleague&nbsp;Janifer Gatenby, who works at the OCLC Leiden office. In her OCLC role, Janifer--a frequent speaker and standards specialist--identifies trends and opportunities for Web data services and system interoperation. If...]]></summary>
    <author>
        <name>Karen Calhoun</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[<p><strong>By Janifer Gatenby</strong></p>
<p><strong></strong>&nbsp;</p>
<p><em><font size="2">This entry was contributed by my colleague&nbsp;<ST1:PERSONNAME w:st="on">Janifer Gatenby</ST1:PERSONNAME>, who works at the OCLC <ST1:CITY w:st="on"><ST1:PLACE w:st="on">Leiden</ST1:PLACE></ST1:CITY> office. In her OCLC role, Janifer--a frequent speaker and standards specialist--identifies trends and opportunities for Web data services and system interoperation. </font></em></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><span style="FONT-SIZE: 10pt; mso-ansi-language: EN-US"><font color="#000000">If I like a novel of one author, I look to see what else he or she has written.<span style="mso-spacerun: yes">&nbsp; </span>The same is true if I find somebody who writes well on topics that interest me, so I would like to find all he or she has written in any form - whether book, article or blog.<span style="mso-spacerun: yes">&nbsp; </span>The importance of grouping the works of authors together is clearly important to me; titles give me an idea about subject whereas authors give me an idea about quality and pertinence.<span style="mso-spacerun: yes">&nbsp; </span>Yet traditional library catalogues, though enriched with authority control of names, place the main emphasis on titles.</font></span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><span style="FONT-SIZE: 10pt; mso-ansi-language: EN-US"><font color="#000000"></font></span>&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><span style="FONT-SIZE: 10pt; mso-ansi-language: EN-US"><font color="#000000"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">When the <a href="http://www.austlit.edu.au/">AustLit </a><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">was first released in 2001 it drew lots of attention because it presented the literature primarily from the point of view of the author, with title of work as a secondary access and was also an early adopter of the <a href="http://www.frbr.org/">FRBR model</a>. <span style="FONT-SIZE: 10pt; mso-ansi-language: EN-US">The author details in AustLit go far beyond the traditional details in library name authority records, including things in the author's life that had a significant influence on the author's creativity, such as literary schools, peers, places lived and education.<span style="mso-spacerun: yes">&nbsp; </span>Prizes awarded are also included.<span style="mso-spacerun: yes">&nbsp; </span>AustLit was also before its time in that the data had been hand crafted, not by librarians, but by literary scholarly experts who signed the entries, thus being a forerunner to databases founded on user contribution such as Wikipedia. <o:p></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><span style="FONT-SIZE: 10pt; mso-ansi-language: EN-US"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">AustLit was one of the inspirations for <a href="http://orlabs.oclc.org/identities/">WorldCat identities</a>, <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">which creates a web page for each author within the WorldCat database, not by hand crafting some 600,000 records, but by data mining 110+ million bibliographic records to reveal new information about authors within WorldCat.<span style="mso-spacerun: yes">&nbsp; </span>Like AustLit, this new rich information includes works by and about the author.<span style="mso-spacerun: yes">&nbsp; </span>It also includes a time-line for the publication of the works and it provides external links to further author information, namely to the Virtual International Authority File <a href="http://www.viaf.org/">(VIAF</a>) <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">and Wikipedia.<span style="mso-spacerun: yes">&nbsp; </span>WorldCat identities, incorporated within <a href="http://www.worldcat.org/">worldcat.org</a>, is&nbsp;<span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">accessible from the details display of a manifestation. In the figure below, the entry for Ernest Hemingway is accessible from&nbsp;a record for&nbsp;<a href="http://www.worldcat.org/oclc/9583168">The Old Man and the Sea</a>.</span></span></span></span>&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="mso-spacerun: yes"></span></span></span></span></span>&nbsp;</p>
<p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="mso-spacerun: yes">
<span class="mt-enclosure mt-enclosure-image" style="DISPLAY: inline">&nbsp;</span>
<span class="mt-enclosure mt-enclosure-image" style="DISPLAY: inline"><img class="mt-image-center" style="DISPLAY: block; MARGIN: 0px auto 20px; TEXT-ALIGN: center" height="336" alt="ernest_hemingway compressed.JPG" src="http://community.oclc.org/metalogue/ernest_hemingway%20compressed.JPG" width="448" /></span>
<span class="mt-enclosure mt-enclosure-image" style="DISPLAY: inline"><span style="FONT-SIZE: 10pt; mso-ansi-language: EN-US">National libraries continue to place emphasis on rich name authority records. The VIAF initiative links the records of the Library of Congress, Deutsche Nationalbibliothek and the Bibliothèque Nationale de France.<span style="mso-spacerun: yes">&nbsp; </span>Linking these three files results in a rich list of alternative name forms, all linked. <span style="mso-spacerun: yes">&nbsp;&nbsp;</span>More institutions are expected to contribute to VIAF in 2009.<o:p></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><span style="FONT-SIZE: 10pt; mso-ansi-language: EN-US"><o:p>&nbsp;</o:p></span><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">Currently library resources are not treated equally by name authority records.<span style="mso-spacerun: yes">&nbsp; </span><a href="http://orweblog.oclc.org/archives/001699.html">Lorcan Dempsey </a><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">pointed to a clear need to expand the scope of authority control to include authors of articles, papers and presentations in journals, institutional repositories and other sources.<span style="mso-spacerun: yes">&nbsp; </span>This is not an easy task for a large database such as WorldCat with 110+ million records with some name authority control and 57 million recently added article records with no name authority control.<span style="mso-spacerun: yes">&nbsp; </span>For scalability it will require some clever data mining to produce richer information in authority records including affiliations and co-authors that can be used to match and distinguish names and hence correctly group their works.<span style="mso-spacerun: yes">&nbsp; </span>There is also some valuable information that could potentially be inherited from the trade such <a href="http://www.isihighlycited.com/">Thomson ISI's highly cited database</a>&nbsp;<span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">and <a href="http://info.scopus.com/news/press/pr_060613.asp">Scopus Author Identifier</a>. </span></span></span></p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"></span></span></span></span>&nbsp;</p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">Elsewhere, information created by the publishing sector is being brought into library databases systems as base data for selection, ordering and cataloguing.<span style="mso-spacerun: yes">&nbsp; </span>Much more could be adopted from the publishing sector in the way of author information.<span style="mso-spacerun: yes">&nbsp; </span>The various sectors in the publishing industry realise the potential benefits of sharing author information and this had led to the creation of a new standard identifier, the International Standard Name Identifier (<a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=44292">ISNI</a>). <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">Participating in the creation of this standard are representatives from industry institutions which control authors' rights and royalties, led by CISAC, the International Confederation of Composers and Authors Societies.<span style="mso-spacerun: yes">&nbsp; </span>Significantly, the working group also includes library representatives from the Bibliothèque Nationale de France, the British Library and OCLC.<span style="mso-spacerun: yes">&nbsp; </span>ISNI promises to provide a central database of disambiguated authors and contributors with a facility to connect to enriched data in external databases.<span style="mso-spacerun: yes">&nbsp; </span>The ISNI database has potential for libraries to access authoritative data created by organisations with direct connections with their authors and contributors.<span style="mso-spacerun: yes">&nbsp; </span>Libraries have been invited to the table and will be encouraged to contribute information on authors and contributors of works in the "long tail"; works of no commercial or marginal commercial value.</span>&nbsp;</span></span></span></span></p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">Dorothea Salo, in an article soon to be published in <em><a href="http://catalogingandclassificationquarterly.com/">Cataloging and Classification Quarterly</a>, </em><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">laments that retrieval from institutional repositories is severely limited by lack of authority control. "Once name variants creep into an institutional repository they are phenomenally difficult to extirpate". One notable exception is in the <st1:country-region w:st="on"><st1:place w:st="on">Netherlands</st1:place></st1:country-region>, where all university researchers receive a unique authority number in the form of a Digital Author Identifier <a href="http://www.surffoundation.nl/smartsite.dws?ch=eng&amp;id=13480">(DAI</a>) that i<span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">s registered in the authority file of the national union catalogue.<span style="mso-spacerun: yes">&nbsp; </span>The aim is to use these identifiers in all repositories, research databases and library catalogues.<span style="mso-spacerun: yes">&nbsp; </span>Publishers too, are sending ONIX records to the Dutch national union catalogue as part of national deposit and also aim to use the Dutch national name authority file in the creation of the ONIX creator data.<span style="mso-spacerun: yes">&nbsp; </span>Systematic use of the DAI identifier ensures an enviable tidiness in the way that the works of authors appear in catalogues and repositories of the <st1:country-region w:st="on"><st1:place w:st="on">Netherlands</st1:place></st1:country-region>.<span style="mso-spacerun: yes">&nbsp;&nbsp;</span><st1:country-region w:st="on"><st1:place w:st="on">Germany</st1:place></st1:country-region> too provides a good example where contributions to the national authority file are made in real time from systems in libraries and networks using the <a href="http://www.loc.gov/standards/sru/record-update/"><st1:PersonName w:st="on">SRU</st1:PersonName> record update protocol</a>.&nbsp;&nbsp;</span>&nbsp;</span></span></span></span></span></span></p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA">With the Dutch DAI as a potential model, libraries have an opportunity to respond to the challenge to produce author views of a variety of resources.<span style="mso-spacerun: yes">&nbsp; </span><span style="mso-spacerun: yes">&nbsp;</span>It will be interesting to see who will take up this opportunity. For success on a large scale, multiple initiatives are necessary, including data mining, employment of commercial data, at least some manual input, and enrichment via contribution from the public at large.<span style="mso-spacerun: yes">&nbsp; </span>The challenge is to create environments with enough web-scale and authority to attract public input via appeals and intriguing campaigns, even competitions.<span style="mso-spacerun: yes">&nbsp; </span>For example, "Create a publications list in a citation format of your choice for your curriculum vitae". Grouping the works of authors together at web-scale provides new opportunities to re-invent and redeploy traditional name authority control methods to create fresh new services for both end-users and authors. </span></span></span></span></span></span></span></p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><em></em></span></span></span></span></form></span></span></span></span></span>&nbsp;</p>
<p><em></em></p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; LETTER-SPACING: 0.2pt; mso-ansi-language: EN-US; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: NL; mso-bidi-language: AR-SA"><span style="mso-spacerun: yes">
<span class="mt-enclosure mt-enclosure-image" style="DISPLAY: inline"><a href="http://www.isihighlycited.com/">&nbsp;</a></span></span></span></span></span></span></span></span></font></span></p>]]>
        
    </content>
</entry>

<entry>
    <title>From Cataloguing to Metadata: An Invitation</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2008/11/from-cataloguing-to-metadata-a.html" />
    <id>tag:community.oclc.org,2008:/metalogue//1.26</id>

    <published>2008-11-30T19:38:19Z</published>
    <updated>2008-11-30T20:02:38Z</updated>

    <summary>In recent talks for library cataloguers on &quot;the new world of metadata,&quot; I am often challenged for real evidence of a shift from traditional cataloguing tasks to more broadly defined metadata activities--and what kinds of activities are we talking about...</summary>
    <author>
        <name>Karen Calhoun</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[<p>In recent talks for library cataloguers on "the new world of metadata," I am often challenged for real evidence of a shift from traditional cataloguing tasks to more broadly defined metadata activities--and what kinds of activities are we talking about anyway?&nbsp; In other words, I have a sense&nbsp;that at least some of my audience members are from Missouri (the "show me" state).&nbsp; </p>
<p><strong>Some Evidence </strong></p>
<p>This post provides some&nbsp;evidence that the transition from cataloguing to metadata work is well underway and invites your collaboration in providing more.&nbsp; I'm not aware of any systematic studies of the transition that have been conducted&nbsp;in North America on this topic (are you?--if yes please share).&nbsp; However, an excellent study from down under--<a href="http://www.nla.gov.au/lis/stndrds/grps/acoc/documents/Warren2007.doc">Directors Views on the Future of Cataloguing in Australia and New Zealand, 2007: A Survey</a>, by Jenny Warren of Monash University--speaks to the topic at hand.&nbsp; Warren's respondents are split on the question whether cataloguers have already transferred their skills to metadata work. Fifty-four percent&nbsp;of the respondents to the Warren survey believe the shift to metadata work is underway in their libraries;&nbsp;forty-six percent believe the shift has not begun (see question 12a of the survey). </p>
<p><strong>Some Activities </strong></p>
<p>Those respondents who believe the shift from cataloguing to metadata is already happening in their libraries were asked to provide examples of the transition (question 12b). A sampling of their answers follows:</p>
<p>o&nbsp;Participation in or leadership of institutional repository, federated search, or image database development<br />o&nbsp;Maintenance of non-MARC databases<br />o&nbsp;Advising on the creation, structure and metadata for other library databases or information systems<br />o&nbsp;Working with thesauri (beyond the traditional library ones)<br />o&nbsp;Implementing and maintaining Dublin Core or EAD<br />o&nbsp;Tagging projects<br />o&nbsp;Indexing projects<br />o&nbsp;Developing and maintaining crosswalks and metadata conversions<br />o&nbsp;Becoming the metadata guru for websites</p>
<p>This seems a familiar list to me, based on what I have observed in North American libraries in transition.&nbsp; Other significant areas of activity that I'm aware for cataloguing/metadata units in transition include help with learning management systems' metadata and information access services.&nbsp; One related example includes the significant contribution of the MIT library's Cataloging and Metadata Services (CAMS) department to <a href="http://ocw.mit.edu/OcwWeb/HowTo/tech-metadata.htm">MIT's OpenCourseWare Project</a>.&nbsp; In fact, <a href="http://libstaff.mit.edu/cams/">MIT's CAMS mission statement </a>seems to me an exemplar for&nbsp;a department in transition, and <a href="http://libraries.mit.edu/metadata/">the MIT approach to offering for-fee metadata services </a>is typical of the direction that I have observed several university libraries taking.</p>
<p><strong>An Invitation</strong></p>
<p>I would like to begin an informal, occasional series on this period of transition from cataloguing to metadata in libraries. Would you be willing to share your success stories and hard-earned lessons on this blog? I believe&nbsp;your shared experiences&nbsp;could be quite useful to those working through transitional issues in their own libraries.&nbsp; If you have a story that you think could help others better define their own path forward, please comment briefly on this post, and I'll be in touch about next steps.&nbsp; Thanks for considering this opportunity to share your experiences and help colleagues in other libraries.<br /><br /></p>]]>
        
    </content>
</entry>

<entry>
    <title>A Multilayered View of Quality</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2008/11/a-multilayered-view-of-quality.html" />
    <id>tag:community.oclc.org,2008:/metalogue//1.25</id>

    <published>2008-11-24T14:30:55Z</published>
    <updated>2008-11-24T14:59:59Z</updated>

    <summary>Students of the quality movement can tell you that the definition of &apos;quality&apos; has over the past decades shifted from one based on conformance to requirements or rules (the classical definition founded in quality control of a product or process)...</summary>
    <author>
        <name>Karen Calhoun</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[<p class="MsoNormal" style="MARGIN: 0in 0in 0pt 0.15in"><span lang="EN-GB" style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-bidi-font-style: italic"><font color="#000000">Students of the quality movement can tell you that the definition of 'quality' has over the past decades shifted from one based on <i>conformance to requirements or rules</i> (the classical definition founded in quality control of a product or process) to one based on <i>fitness for use</i> (a perspective based on how well the product or service meets people's needs). In a practical sense, however, any organization delivering a product or service--like a bibliographic database--has to pay attention to both aspects of quality.<o:p></o:p></font></span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt 0.15in"><span lang="EN-GB" style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-bidi-font-style: italic"><o:p><font color="#000000">&nbsp;</font></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt 0.15in"><span lang="EN-GB" style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-bidi-font-style: italic"><font color="#000000">In recent months my colleagues Janet Hawk, Joanne Cantrell and I have been examining what is most important about WorldCat metadata to a range of audiences; learning where WorldCat metadata falls short of meeting the needs of its users; and planning a course of action to sustain and enhance the value of WorldCat metadata to its varied constituencies.<span style="mso-spacerun: yes">&nbsp; </span><o:p></o:p></font></span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt 0.15in"><span lang="EN-GB" style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-bidi-font-style: italic"><o:p><font color="#000000">&nbsp;</font></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt 0.15in"><span lang="EN-GB" style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-bidi-font-style: italic"><font color="#000000">Our forthcoming recommendations are based on information gathered from several surveys of different OCLC constituencies--faculty and graduate students, undergraduates, and casual Internet users on the one hand, and collection development, technical services, resource sharing, and public services librarians on the other. Each of these constituencies defines WorldCat metadata 'quality' in its own way.<span style="mso-spacerun: yes">&nbsp; </span>Quality means having the 'right' data, but the 'right' data varies across constituencies.<o:p></o:p></font></span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt 0.15in"><span lang="EN-GB" style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-bidi-font-style: italic"><o:p><font color="#000000">&nbsp;</font></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt 0.15in"><span lang="EN-GB" style="FONT-SIZE: 10pt; mso-bidi-font-size: 12.0pt; mso-bidi-font-style: italic"><font color="#000000">Many of our findings are relevant not just to WorldCat as viewed through its different interfaces or access methods (WorldCat.org, WorldCat on FirstSearch, Connexion ...) but to library catalogs and discovery interfaces in general.<span style="mso-spacerun: yes">&nbsp; </span>At the <a href="http://www.katina.info/conference/">Charleston Conference</a>, Janet Hawk and I made our first presentation on these generalizable findings.<span style="mso-spacerun: yes">&nbsp; </span>At some point the presentation will be available on the conference web site; in the meantime, I have uploaded it for <a href="http://www.slideshare.net/amarintha">viewing on SlideShare</a>. Your comments are welcome. <o:p></o:p></font></span></p>]]>
        
    </content>
</entry>

<entry>
    <title>WorldCat Metadata and Zotero</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2008/11/worldcat-metadata-and-zotero.html" />
    <id>tag:community.oclc.org,2008:/metalogue//1.24</id>

    <published>2008-11-21T23:34:32Z</published>
    <updated>2008-11-21T23:38:19Z</updated>

    <summary><![CDATA[Some of you have asked questions about using WorldCat.org to download citations with Zotero.&nbsp; For further information, please see my colleague's post "COinS Helps You Build Citations" on the WorldCat blog....]]></summary>
    <author>
        <name>Karen Calhoun</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[Some of you have asked questions about using WorldCat.org to download citations with Zotero.&nbsp; For further information, please see my colleague's post "<a href="http://worldcat.org/blogs/archives/2008/11/coins-in-worldcat.htm">COinS Helps You Build Citations" </a>on the WorldCat blog. <br />]]>
        
    </content>
</entry>

<entry>
    <title>Notes on OCLC&apos;s Updated Record Use Policy</title>
    <link rel="alternate" type="text/html" href="http://community.oclc.org/metalogue/archives/2008/11/notes-on-oclcs-updated-record.html" />
    <id>tag:community.oclc.org,2008:/metalogue//1.23</id>

    <published>2008-11-04T19:55:03Z</published>
    <updated>2008-12-03T16:07:58Z</updated>

    <summary><![CDATA[There has been much discussion around OCLC's effort to update its record use guidelines. We have listened to the feedback and, as a result, have&nbsp;adjusted both the updated policy and the FAQ. We have modified our approach to&nbsp;WorldCat attribution (field...]]></summary>
    <author>
        <name>Karen Calhoun</name>
        
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://community.oclc.org/metalogue/">
        <![CDATA[<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><font color="#000000">There has been much discussion around OCLC's effort to update its record use guidelines. We have listened to the feedback and, as a result, have&nbsp;adjusted both the <a href="http://www.oclc.org/us/en/worldcat/catalog/policy/policy.htm">updated policy </a>and the <a href="http://www.oclc.org/us/en/worldcat/catalog/policy/questions/default.htm">FAQ</a>. <span style="mso-spacerun: yes">We have modified our approach to&nbsp;WorldCat attribution (field 996). If libraries do not wish to retain the 996 field in downloaded WorldCat records, they are free to remove it.&nbsp;In addition, libraries are free to either add the 996 field to existing records they transfer to&nbsp;others, or not, at their discretion.&nbsp;</span></font></span></p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><font color="#000000"><span style="mso-spacerun: yes"></span>In this process, and in connection with my role on OCLC's Record Use Study Group, I've been asked more than once <b style="mso-bidi-font-weight: normal">why OCLC felt the need to update its policy</b> and <b style="mso-bidi-font-weight: normal">why member libraries should support the updated policy</b>. This post is an attempt to answer those questions.</font></span></p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">
<p class="MsoNormal" style="MARGIN: 0pt"><b style="mso-bidi-font-weight: normal"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><font color="#000000">Time for a change<o:p></o:p></font></span></b></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p><font color="#000000">&nbsp;</font></o:p></span></p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><font color="#000000">In Web years, the <i style="mso-bidi-font-style: normal"><a href="http://www.oclc.org/support/documentation/worldcat/records/guidelines/default.htm">Guidelines for Use and Transfer of OCLC-Derived Records</a></i>, last updated in 1987, are not just 21, but as old as Methuselah.<span style="mso-spacerun: yes">&nbsp; </span>While the principles underlying the <i style="mso-bidi-font-style: normal">Guidelines </i>have held up well with respect to sharing among libraries, the language and 1980s context of the document have made the <i style="mso-bidi-font-style: normal">Guidelines</i> increasingly hard to understand and apply.<span style="mso-spacerun: yes">&nbsp; </span>The <i style="mso-bidi-font-style: normal">Guidelines</i> have also been frequently faulted for their ambiguity about WorldCat data sharing rights and conditions.</font></span></p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">
<p class="MsoNormal" style="MARGIN: 0pt"><b style="mso-bidi-font-weight: normal"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><font color="#000000">What's the Web got to do with it?<o:p></o:p></font></span></b></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p><font color="#000000">&nbsp;</font></o:p></span></p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><font color="#000000">The disruption that the Web would bring to libraries became painfully obvious when the <i style="mso-bidi-font-style: normal"><a href="http://www.oclc.org/reports/pdfs/Percept_pt1.pdf">Perceptions of Libraries</a></i> survey report was released, revealing how much more likely respondents were to begin a search for information with a search engine (84%) than on a library Web site (1%) (see page 17 of 34).<span style="mso-spacerun: yes">&nbsp; </span>In our "attention economy," that's bad.<span style="mso-spacerun: yes">&nbsp; </span>OCLC's response to libraries' loss of attention in Web space, slow at first and quickening over the last couple of years, has been to start building Web scale for libraries (see&nbsp;Dempsey and Lavoie 2008).</font></span></p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><font color="#000000">OCLC's actions since I rejoined OCLC 18 months ago, as well as the passionate commitment of its leadership and staff, have been focused on placing library collections prominently on the main boulevards of the Web, right there with the Googles, Yahoos, Facebooks, and Amazons.<span style="mso-spacerun: yes"> </span><a href="http://www.worldcat.org/">WorldCat.org's</a> purpose is not so much destination Web site as "switch," driving traffic from popular Web sites like Google Book Search to libraries' collections.<span style="mso-spacerun: yes">&nbsp; </span>The switching mechanism is beginning to work: in one recent five month period, 87% of the referrals to WorldCat.org came from search engines and other Web sites; less than 13% came from a typed or bookmarked URL to WorldCat.org itself. This week, a <a href="http://weblogs.hitwise.com/us-heather-hopkins/2008/10/google_books_drives_visits_to_1.html">Hitwise commentator</a>, reporting on downstream websites from Google Book Search, noted that 22% of visits from Google Book Search go to an Education website, with WorldCat.org the #1 Education website.</font></span></span></p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><font color="#000000">There is plenty of work remaining to be done to make the present cloud of disparate library systems, loosely tied together with WorldCat in the middle, attracting Web scale traffic from the Amazoogles, function reliably enough to deserve the name "Web scale for libraries," but the first hard steps are behind us.</font></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><font color="#000000"></font></span>&nbsp;</p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><font color="#000000">To play the role it is now playing on behalf of libraries, OCLC needs to be a player on the Web, and not just any player, but an influential one. It therefore needs to be a Web company, with data sharing policies and practices appropriate to the Web. </font></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><font color="#000000"></font></span>&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><font color="#000000">OCLC has been severely criticized for its WorldCat data sharing policies and practices. Some of these criticisms have come from people or organizations that would benefit economically if they could freely replicate WorldCat. Other criticisms have come from a genuine commitment to openly sharing data on the Web in ways that will help libraries continue to thrive.<span style="mso-spacerun: yes">&nbsp; </span>Whatever the criticisms' motivation, the overarching point has been that the 1987 <i style="mso-bidi-font-style: normal">Guidelines </i>overly limit WorldCat data sharing for new, Web scale uses of WorldCat data. At least some, if not many&nbsp;of these uses would be consistent with OCLC's chartered purposes and in the interests of the OCLC membership--especially those that will expose member library collections on high traffic Web sites.<o:p></o:p></font></span></p>
<p class="MsoNormal" style="MARGIN: 0pt">&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0pt"><b style="mso-bidi-font-weight: normal"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><font color="#000000">Attribution and linking to the policy<o:p></o:p></font></span></b></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p><font color="#000000">&nbsp;</font></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><font color="#000000"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">An objection to linking to the policy goes something like "OCLC has no right to tell my library what it can do with its records."<span style="mso-spacerun: yes">&nbsp; </span>This is to overlook the 21+ year history of the <i style="mso-bidi-font-style: normal">Guidelines</i>, which <b style="mso-bidi-font-weight: normal">have </b>governed what libraries can do with OCLC-derived records, albeit not always unambiguously. See for yourself by taking a good look at the <i style="mso-bidi-font-style: normal">Guidelines.</i><span style="mso-spacerun: yes">&nbsp; </span>Their stated rationale for imposing conditions on libraries' record sharing is that "</span><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA; mso-bidi-font-family: 'Times New Roman'">member libraries have made a major investment in the OCLC Online Union Catalog and expect other member libraries, member networks and OCLC to take appropriate steps to protect the database."<span style="mso-spacerun: yes">&nbsp; </span>To that end, under the <i style="mso-bidi-font-style: normal">Guidelines</i>, non-commercial record sharing between libraries is ok, commercial sharing is not, at least not without a separate agreement with OCLC. Sound familiar? The principles of the <i style="mso-bidi-font-style: normal">Guidelines</i> match those underlying the updated policy--promote as much sharing as possible while protecting members' investment in WorldCat. </span></font></p>
<p class="MsoNormal" style="MARGIN: 0pt"><font color="#000000"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA; mso-bidi-font-family: 'Times New Roman'"></span></font>&nbsp;</p><font color="#000000"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA; mso-bidi-font-family: 'Times New Roman'">
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The difference is not in the principles, then, but the environment in which the principles are applied.<span style="mso-spacerun: yes">&nbsp; </span>The <i style="mso-bidi-font-style: normal">Guidelines</i> came from the limited data sharing environment of the 1980s.<span style="mso-spacerun: yes">&nbsp; </span>The updated policy's landscape is the Web and the incredibly dynamic data sharing environment it represents.<span style="mso-spacerun: yes">&nbsp; </span>You couldn't tell from recent traffic on library listservs and blogs, but attribution of the source of data that is reused in another context is standard practice on the Web. Have a look at the license pertaining to Wikipedia, the <i style="mso-bidi-font-style: normal"><a href="http://en.wikipedia.org/wiki/Wikipedia:Text_of_the_GNU_Free_Documentation_License">GNU Free Documentation License</a></i>, for example:<o:p></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt 0pt 0pt 36pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">"</span><span lang="EN" style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-ansi-language: EN; mso-bidi-font-family: 'Times New Roman'">You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License." </span><span lang="FR" style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-ansi-language: FR; mso-bidi-font-family: 'Times New Roman'">(Section 2)<o:p></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt">&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The perception of some bloggers and posters is that, unlike an article contributed to Wikipedia, the OCLC cooperative has no claim on WorldCat records that a library has copied for local use; but attribution is <b style="mso-bidi-font-weight: normal">not </b>a condition of Use as defined in the updated policy (Section C).<span style="mso-spacerun: yes">&nbsp; </span>Attribution is a condition (and now an optional one) of Transfer--that is, the updated policy asks for a link to the policy to be carried in a copy that moves <i style="mso-bidi-font-style: normal">downstream</i> from the library that is using that record.<span style="mso-spacerun: yes">&nbsp; </span>In this way the link is serving exactly the same purpose as the link to the GNU license covering the copying of Wikipedia articles--providing provenance and information about the rights and conditions associated with this piece of information floating around the Web.</span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></span>&nbsp;</p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">We think the request to link back to the policy (using the 996 field) is reasonable and will actually facilitate and reduce the costs of downstream WorldCat data sharing on the Web, where metadata is constantly exchanged, remixed, and mashed up. Notwithstanding what we think, it is clear that some of our members strongly oppose or at best, do not understand OCLC's reasoning. And so, the burden is on us to step back, explain, and do our best to gain support for this change in the community we serve. That is the course we have chosen. <span style="mso-spacerun: yes">&nbsp;</span><span style="mso-spacerun: yes">&nbsp;</span><o:p></o:p></span></p><o:p></o:p></span>
<p class="MsoNormal" style="MARGIN: 0pt">&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">OCLC will go ahead with implementing the 996 field in mid-February, because we feel it is the right thing to do and in the long-term interests of the cooperative. However, if libraries do not wish to retain the 996 field in downloaded WorldCat records, they are free to remove it. In addition, libraries are free to either add the 996 field to existing records they are transferring to others (or alternatively make copies of the policy available to transferees), or not, at their discretion. <o:p></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt">&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0pt"><b style="mso-bidi-font-weight: normal"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">'No rights reserved" or 'some rights reserved'?<o:p></o:p></span></b></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The Record Use Study Group began its work with an environmental scan of the data sharing policies of a variety of content and metadata providers on the Web. We learned that, while the blogosphere is noisy with proclamations that "data should be open and free," nearly all organizations have terms and conditions for sharing--that is, they reserve some rights over how their content or data is used and transferred to others. My <a href="http://www.slideshare.net/amarintha/calhoun-data-sharing-panel-ifla-aug-2008-presentation">presentation to the Libraries and Web 2.0 Discussion Group at IFLA </a>a couple of months ago lays out the findings and conclusions of our investigation of the data sharing landscape (if you download the file you can see the speaker notes).</span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></span>&nbsp;</p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The Study Group was particularly influenced by the <a href="http://creativecommons.org/about/">Creative Commons </a>set of licenses. It is no accident that the structure of OCLC's updated policy mirrors that of the <a href="http://creativecommons.org/licenses/by-nc-sa/3.0/legalcode"><em>Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported </em></a>license (Definitions-License-Restrictions-Representations Etc.).&nbsp;</span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></span>&nbsp;</p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Creative Commons licensing provides an alternative to full control over content and metadata, building a bridge between&nbsp;a world that regulates every use--that is,&nbsp;"all rights reserved"--and an anarchic world&nbsp;in which content and data&nbsp;are exposed to exploitation. Under the variety of Creative Commons licenses that are available, content and metadata rights holders can protect their works while encouraging the freedom to remix and reuse content and metadata under specified circumstances--that is, to declare "some rights reserved." (And yes, while we considered simply adopting a Creative Commons license, we chose to retain an OCLC-specific&nbsp;policy&nbsp;to help us re-express well-established community practice from the <em>Guidelines</em>.)&nbsp;<o:p></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Meeting information seekers' expectations requires--<i style="mso-bidi-font-style: normal">demands</i>--more open sharing of library data on the Web. The OCLC leadership understands this and is committed to making it happen. However, the financial realities of many organizations--including OCLC--require careful transitions to more open models. It is not free (that is, without cost) to build services upon the valuable metadata contributed by members, and it is not free to be the steward of WorldCat (I discuss OCLC's stewardship/curatorial role <a href="http://community.oclc.org/metalogue/archives/2008/10/taking-care-of-the-socks-or-th.html">here</a>). To survive, OCLC must recover these costs, and it must do so from members; its funding does not come from government agencies, from higher education, from foundations or donations, from advertising, from parent companies, or from venture capitalists.</span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></span>&nbsp;</p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">OCLC's updated policy represents a first step toward truly modernizing WorldCat data sharing policies. The text and the practices we have proposed (e.g., the WorldCat Record Use Form, the linking field) are a balancing act. On the one hand, we have tried for a policy that will have the effect of opening WorldCat data to new uses by libraries, museums, and archives while fostering partnerships from which innovative noncommercial <b style="mso-bidi-font-weight: normal">and </b>commercial uses of WorldCat data can emerge. On the other, we have tried for a policy that will assure the continued economic viability of WorldCat and the WorldCat-based services&nbsp;provided to the cooperative. <o:p></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt">&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0pt"><b style="mso-bidi-font-weight: normal"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Why should libraries support the updated policy?<o:p></o:p></span></b></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">OCLC's update to the<i style="mso-bidi-font-style: normal"> Guidelines</i> intends to modernize them for application on the Web, foster new uses of WorldCat data that benefit members, and clarify data sharing rights and restrictions.<span style="mso-spacerun: yes">&nbsp; </span>It is definitely <b style="mso-bidi-font-weight: normal">not</b> OCLC's intent to rein in libraries' or consortia's customary use and transfer practices that have been in place for years and that have resulted in&nbsp;important library resource sharing systems and union catalogs. That is not what the updated policy&nbsp;is about, at all.<span style="mso-spacerun: yes">&nbsp; </span>It <b style="mso-bidi-font-weight: normal">is</b> our intent to implement an updated policy that will allow us to better manage commercial uses of WorldCat records, to assure such uses benefit members, and to defend against uses of WorldCat that could destroy the cooperative. <o:p></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">The updated policy is a legal document.<span style="mso-spacerun: yes">&nbsp; </span>Being a player on the Web, working on behalf of libraries, requires that the policy be a legal document.<span style="mso-spacerun: yes">&nbsp; </span>I know that some librarians will be uncomfortable with that, but it is necessary.<span style="mso-spacerun: yes">&nbsp; </span><o:p></o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">OCLC's and the members' central asset is the WorldCat database that we share. It is our common investment, our "commons." I believe it is the right course to protect the commons.* Thus, as Garrett Hardin has suggested in his writings about the "tragedy of the commons," it is appropriate to regulate the use of the commons.<span style="mso-spacerun: yes">&nbsp;</span>OCLC needs to manage WorldCat data sharing to assure that benefit accrues back to the members who have invested in WorldCat, and that the WorldCat commons is not exhausted through over-exploitation. Protecting the commons means adopting "some rights reserved" as the data sharing model.<span style="mso-spacerun: yes">&nbsp; </span>While a data sharing model based on "no rights reserved" is a laudable ideal, if OCLC were to adopt such a policy, it is possible, if not likely, that the WorldCat commons and the OCLC cooperative would not survive.&nbsp;</span></p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"></span>&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">We believe that&nbsp;libraries,&nbsp;the wider library-archives-museum community, and those they serve&nbsp;will benefit from the updated policy&nbsp;without placing our shared investment in WorldCat at peril. As OCLC's four decades of working with libraries to increase&nbsp;access to and use of the world's information demonstrates, sharing burden and benefit is a proven and remarkably durable cooperative model.&nbsp;</span>&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0pt">&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0pt">-----------------------------</p><o:p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">*I began drafting this post last weekend. It was interesting to read a blog post about the policy today that uses&nbsp;the same analogy.<span style="mso-spacerun: yes">&nbsp; </span><o:p></o:p></span></p></o:p></span>
<p class="MsoNormal" style="MARGIN: 0pt">&nbsp;<o:p></o:p></span></p><o:p></o:p></span>
<p class="MsoNormal" style="MARGIN: 0pt"></span></font></span>&nbsp;</p>
<p class="MsoNormal" style="MARGIN: 0pt"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><font color="#000000"><o:p></o:p></font></span>&nbsp;</p></span></span>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><font color="#000000"></font></span></span></span>&nbsp;</p>
<p><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Times; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><font color="#000000"></font></span></span>&nbsp;</p>]]>
        
    </content>
</entry>

</feed>
