<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"><channel><title>Disruptive Library Technology Jester &#187; ALA Midwinter 2009</title> <atom:link href="http://dltj.org/tag/alamw2009/feed/" rel="self" type="application/rss+xml" /><link>http://dltj.org</link> <description>We&#039;re Disrupted, We&#039;re Librarians, and We&#039;re Not Going to Take It Anymore</description> <lastBuildDate>Mon, 06 Feb 2012 20:04:22 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <cloud domain='dltj.org' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' /> <creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/us/</creativeCommons:license> <item><title>Further Consideration of OCLC Records Use Policy</title><link>http://dltj.org/article/oclc-records-use-policy-2/</link> <comments>http://dltj.org/article/oclc-records-use-policy-2/#comments</comments> <pubDate>Thu, 29 Jan 2009 01:37:26 +0000</pubDate> <dc:creator>Peter Murray</dc:creator> <category><![CDATA[policy]]></category> <category><![CDATA[ALA Midwinter 2009]]></category> <category><![CDATA[Biblios]]></category> <category><![CDATA[copyright]]></category> <category><![CDATA[description]]></category> <category><![CDATA[Google Book Search]]></category> <category><![CDATA[MARC]]></category> <category><![CDATA[OCLC]]></category> <category><![CDATA[Open Library]]></category><guid isPermaLink="false">http://dltj.org/?p=701</guid> <description><![CDATA[At ALA Midwinter, ALCTS sponsored a panel discussion about sharing library-created data inside and outside the library community, with a particular focus on cataloging data. I was honored to be ask to speak on the topic from the perspective of &#8230; <a href="http://dltj.org/article/oclc-records-use-policy-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<abbr class="unapi-id ignore noPrint" title="http://dltj.org/?p=701"></abbr><p>At ALA Midwinter, ALCTS sponsored a panel discussion about sharing library-created data inside and outside the library community, with a particular focus on cataloging data. I was honored to be ask to speak on the topic from the perspective of a consortial office. This is the second and final post in a series that represents an approximation of what I said on the panel.</p><p>The <a href="http://dltj.org/article/oclc-records-use-policy-1/">first part</a> examined the nature of surrogate records that we create as a means to get users to content.   The post looked at where we get records, how humans and machines can create them, and the rights associated with component data that makes up the records.</p><p><h2>Right to reuse records without restrictions</h2><br />One way to handle the clouded nature of surrogate ownership is to follow the lead of the &Dagger;biblios.net and the Open Library Project:  publish the surrogates with a public domain dedication or with an &ldquo;open data&rdquo; license.  This is going to become increasingly important as the variety of systems that use this kind of data evolve and in some cases move outside the library space.</p><p>The first area where is important is with discovery layers.  A new generation of discovery layers are taking surrogates from a variety of sources &ndash; catalogs, publishers, index/abstract services, etc. &ndash; and performing actions such as consolidating records and building relationships between surrogates.  These derived surrogates are presented to users in new interfaces or new portals into existing interfaces.  Examples of these systems are the <a href="http://www.extensiblecatalog.org/" title="About the eXtensible Catalog project">Extensible Catalog project</a> at the University of Rochester and the newly announced <a href="http://www.serialssolutions.com/summon/" title="Summon from Serials Solutions">Serials Solutions Summon product</a>.  OhioLINK recently <a href="http://dltj.org/article/discovery-layer-itn/">solicited responses from vendors</a> where this kind of capability is a key product of a new discovery layer.  Other projects (such as subject-specific portals) also seek to re-purpose the data &ndash; mix it up with other sources of data to create new uses and views that are specific to a particular user community.  Anything other than a permissive-for-all-by-default will put up roadblocks and cause builders of these systems to seek data from other services.</p><p>In addition to presenting the surrogates to users in new ways, libraries are also investigating new forms of workflow and collaborative activities surrounding the creation and maintenance of bibliographic records.  One of the strong desires of many involved in the <a href="http://oleproject.org/" title="The OLE Project homepage">OLE Project</a> is cooperative purchasing and cooperative technical services.  OhioLINK has also recently issued an RFI seeking new options for highly collaborative workflows in the maintenance of surrogate records.  Old models of charging for use of records can hinder the ability of cooperating institutions to optimize costs and efforts of back-room library options.</p><p>The elephant in the room is the recently proposed OCLC Records Use Policy.  Setting aside the debatable legal framework under which OCLC asserted the right to set a usage policy on records from the cooperative, there were clauses in the proposed policy that jeopardize the usability of records, and as a consequence the viability of the cooperative as a whole.  Actions that restrict use of data or create uncertainty around the use of data lessen the value of that data.  I think few would argue that value can be created by aggregating services on top of the data; the activities in the <a href="http://www.worldcat.org/devnet/wiki/Services" title="Services - WorldCat Developers&#039; Network">WorldCat Grid</a> and <a href="http://www.worldcat.org/devnet/index.php/Main_Page" title="Main Page - WorldCat Developers&#039; Network">Developer&rsquo;s Network</a> point to that.  Revenue could be generated in fees charged to non-cooperative members.  It is conceptually important to separate the hosting of the surrogates from the layered services on top of them &ndash; WorldCat Local, mediated ILL, collection analysis, by way of example.</p><p><h2>Parting thoughts</h2><br />OCLC was <a href="http://www.oclc.org/about/history/default.htm" title="History of OCLC">created forty years ago</a> based on the use of new technologies and relationships that technology enabled.  While we all want the cooperative to exist and flourish, it should not do so by engaging in activities that solely protect it.   Portions of the proposed policy appear to mandate that OCLC be in the middle of any exchange of records.  While one can appreciate the ability of a large web footprint like &ldquo;<a href="http://www.worldcat.org/" title="WorldCat homepage">worldcat.org</a>&rdquo; to drive traffic to local libraries, when it comes to sharing factual and non-factual data in surrogate records, being in the middle might not always be the most efficient way to make use of bibliographic data.  OhioLINK&rsquo;s efforts are based on a state mandate to be more efficient and effective for the users of higher education libraries in Ohio.  On balance, the rules of the cooperative cannot trump what might be in the best interests of the members.  Asserting the right to impose policy restrictions on records</p><p><h2>Post-panel Thoughts</h2><br />At the end of co-panelist Karen Calhoun&#8217;s remarks, she encouraged attendees to send comments to the Review Board of Shared Data Creation and Stewardship via the <a href="mailto:recorduse@oclc.org">recorduse@oclc.org</a> e-mail address.  I certainly encourage interested parties to do that, but to also find some way to post it in a public forum.  The <a href="http://wiki.code4lib.org/index.php/OCLC_Policy_Change" title="OCLC Policy Change - Code4Lib">discussion of the proposed policy</a> has been both spirited and informative.  Since this is a matter at the core of the cooperative, I don&#8217;t think the discussion should be limited to a one-way feed of information into the review board.  The discussion should also occur between us:  the members of the OCLC cooperative and community.  If you have a blog, post about it.  If not, consider <a href="http://lisnews.org/user/register" title="User account | LISNews">creating one at LISnews.org</a> and <span class="removed_link" title="http://lisnews.org/node/add/blog">post about it</span> there.  Or use mailing lists such as <a href="http://listserv.syr.edu/archives/autocat.html" title="Archives of AUTOCAT@LISTSERV.SYR.EDU">Autocat</a> and <a href="http://www.listserv.uga.edu/archives/radcat.html" title="Archives of RADCAT@LISTSERV.UGA.EDU">Radcat</a>.  OCLC already has a community forum platform &#8212; <a href="http://www.webjunction.org/home" title="WebJunction homepage">WebJunction</a> &#8212; and it would be good to see OCLC use that as a forum for public discussion.</p><p>Thanks to Charles Wilt, Executive Director of ALCTS, for inviting me to speak at the <a href="http://www.ala.org/ala/mgrps/divs/alcts/alcts.cfm" title="Association for Library Collections and Technical Services (ALCTS) homepage">ALCTS</a> Forum and to Karen Calhoun for facilitating the invitation.  My appreciation also goes out to my co-panelists:  Karen Calhoun (who has <a href="http://www.slideshare.net/amarintha/creating-and-sustaining-communities-around-shared-data-the-case-of-oclc-presentation" title="Creating and Sustaining Communities Around Shared Data: The Case of OCLC - SlideShare">posted her slides online</a>), <a href="http://everybodyslibraries.com/2009/01/28/open-catalog-apis-and-data-ala-presentation-notes-posted/" title="Open catalog APIs and data: ALA presentation notes posted &amp;laquo; Everybody&amp;#8217;s Libraries">John Mark Ockerbloom</a> (who also <a href="http://works.bepress.com/john_mark_ockerbloom/10/" title="Open records, open possibilities">posted his slides and approximate speech transcript</a>), and Brian Schottlaender (who eloquently summarized statements from the other panelists and took point in fielding questions from the audience).<p style="padding:0;margin:0;font-style:italic;" class="removed_link">The text was modified to remove a link to http://lisnews.org/node/add/blog on January 13th, 2011.</p><div class='series_links'><a href='http://dltj.org/article/oclc-records-use-policy-1/' title='Consideration of OCLC Records Use Policy'>Previous in series</a> <a href='http://dltj.org/article/guardian-correction/' title='Correction Added to Guardian Story on OCLC Record Use Policy'>Next in series</a></div>]]></content:encoded> <wfw:commentRss>http://dltj.org/article/oclc-records-use-policy-2/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>Consideration of OCLC Records Use Policy</title><link>http://dltj.org/article/oclc-records-use-policy-1/</link> <comments>http://dltj.org/article/oclc-records-use-policy-1/#comments</comments> <pubDate>Wed, 28 Jan 2009 04:46:11 +0000</pubDate> <dc:creator>Peter Murray</dc:creator> <category><![CDATA[policy]]></category> <category><![CDATA[ALA Midwinter 2009]]></category> <category><![CDATA[Amazon]]></category> <category><![CDATA[Biblios]]></category> <category><![CDATA[copyright]]></category> <category><![CDATA[description]]></category> <category><![CDATA[Google Book Search]]></category> <category><![CDATA[LibLime]]></category> <category><![CDATA[MARC]]></category> <category><![CDATA[OCLC]]></category> <category><![CDATA[Open Library]]></category><guid isPermaLink="false">http://dltj.org/?p=694</guid> <description><![CDATA[At ALA Midwinter, ALCTS sponsored a panel discussion about sharing library-created data inside and outside the library community, with a particular focus on cataloging data. I was honored to be ask to speak on the topic from the perspective of &#8230; <a href="http://dltj.org/article/oclc-records-use-policy-1/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<abbr class="unapi-id ignore noPrint" title="http://dltj.org/?p=694"></abbr><p>At ALA Midwinter, ALCTS sponsored a panel discussion about sharing library-created data inside and outside the library community, with a particular focus on cataloging data.  I was honored to be ask to speak on the topic from the perspective of a consortial office.  This is the first in a series of posts that represents an approximation of what I said on the panel.  (Also be sure to read the summary of the session by <a href="http://www.libraryjournal.com/article/CA6632413.html" title="OCLC Defends Records Policy, Faces Questions, Suggestions, and Criticisms">Norman Oder in Library Journal</a>.)</p><p>I think it is important to step back and reflect on the nature of what we are talking about.  We build bibliographic records as surrogates for the desired object, meaning that the surrogate is a means to an end – retrieving the described object – and not an end onto itself. We build indexes of these surrogates for patrons to use to discover information.  All other factors held constant, the better the surrogate, the greater the chance the user will find the information they are seeking.  The following discussion looks at the sources of records, the way they are built, and what it means to try to share them.</p><p><h2>Sources of Records</h2><br />The most familiar form of surrogates are the records generated by humans, and in our field <a href="http://www.aacr2.org/" title="AACR2 homepage">AACR2</a> encoded in <a href="http://www.loc.gov/marc/" title="MARC homepage">MARC</a> is the most common.  There are many sources of human-generated cataloging records.  For academic libraries, the most obvious is OCLC, but it is not the only one.  Integrated library systems include <a href="http://www.loc.gov/z3950/agency/" title="Z39.50 Maintenance Agency homepage">Z39.50</a> clients that enable the search of remote catalogs and import the resulting MARC records into the local catalog.  The Library of Congress catalog and the OhioLINK library catalog can be used in this fashion.  Records can also be purchased from vendors.  One emerging source is the recently announced ‘<a href="http://biblios.net/" title="biblios.net homepage">&Dagger;biblios.net</a>’ from <a href="http://liblime.com/" title="LibLime homepage">LibLime</a>.  The <a href="http://openlibrary.org/" title="Open Library homepage">Open Library project</a> of the Internet Archive could conceivably also be a source of cataloging records, although such use is not the goal of the project.</p><p>The humans creating these surrogate records are typically called “catalogers” although I’m coming to prefer the term descriptionists as a more accurate portrayal of their activity (if, for no other reason, that the description activity engaged in by these professionals extends beyond what we traditionally consider “the catalog”).  Using the tools of taxonomies and ontologies, the descriptionist creates the surrogate of the item to put into the catalog systems.</p><div id="attachment_google_tech_talk" class="wp-caption alignright" style="width: 314px;  border: 1px solid #dddddd; background-color: #f3f3f3; padding-top: 4px; margin: 10px; text-align:center; float: right;"><embed id="VideoPlayback" FlashVars="initialTime=1765" src="http://video.google.com/googleplayer.swf?docid=2159021324062223592&#038;hl=en&#038;fs=true" style="width:300px;height:245px" allowFullScreen="true" allowScriptAccess="always" type="application/x-shockwave-flash"> </embed><p style=' padding: 0 4px 5px; margin: 0;'  class="wp-caption-text">Google Tech Talk by David Weinberger about his book 'Everything is Miscellaneous', starting at 29 minutes and 25 seconds into the talk</p></div><p>There is another way emerging, however, to create these surrogates:  through computer algorithmic computation against the object itself.  In his book <a href="http://www.everythingismiscellaneous.com/" title="Website for &#038;039;Everything is Miscellaneous&#038;039; book">Everything is Miscellaneous</a>, David Weinberger talks about the fungible nature of metadata and data: &ldquo;metadata&rdquo; is what we know and &ldquo;data&rdquo; is what we want to find out.  In a <a href="http://video.google.com/videoplay?docid=2159021324062223592" title="Everything is Miscellaneous">talk given at Google in May 2007</a>, he gave an example of using something known &mdash; like a quote from a book &mdash; to find out something &mdash; like the author of that book.  (Skip to 29 minutes and 25 seconds into the video.)  The &ldquo;metadata&rdquo; (the quote) was used to find the &ldquo;data&rdquo; (the author) that was being sought.</p><p>This is Google&rsquo;s big experiment in computational analytics.  It is relying on an analysis of the text of the item itself to be the descriptive surrogate.  It employs algorithms that look at every word &mdash; perhaps even every concept &mdash; in an item and weights it relative to those words and terms in other items in the corpus.</p><p>Amazon has done something similar for years with its &ldquo;<a href="http://www.amazon.com/gp/phrase/help/help.html" title="Amazon.com: What are Key Phrases?">Key Phrases</a>&rdquo; techniques.  For Amazon, Capitalized Phrases are people, places, events, or terms mentioned in a book. Statistically Improbable Phrases are the most distinctive phrases in a book as compared against the corpus of texts in its catalog.  These become a form of index points &ndash; the surrogates &ndash; for finding the item.</p><p>Of human-generated or machine-generated, which of these is better &ndash; a measure of effectiveness in precision and recall as well as an assessment of the relative cost to create &ndash; is undoubtedly a topic of research and debate.  For those of us more familiar in the ways of the descriptionists, however, it is undoubtedly time to become familiar with the ways of the computationalists to understand the strengths of each.</p><p><h2>Ownership of records</h2><br />Our surrogate records contain two varieties of data:  recitation of facts and efforts of creativity.  Under U.S. intellectual property law, facts are not creative works and therefore are not covered by copyright.  (This is the common interpretation of <a href="http://en.wikipedia.org/wiki/Feist_v._Rural" title="Feist Publications v. Rural Telephone Service - Wikipedia">Feist v. Rural</a>, a 1991 Supreme Court case that determined that telephone directories are not creative works and therefore are not offered copyright protection.)  The legal status of our surrogate records is somewhat murkier, though.  While the inclusion of facts such as title, author, and publisher are not creative acts, the assignment of classification numbers and subject headings could be a creative act, and the person doing the creation would hold copyright for those acts.</p><p>Ownership of the data in records is even cloudier than what is outlined above.  By my estimation, we are entering a world in which there are four types of attributes that make up our bibliographic records. The first is the recitation of the facts, whether copied from the item-in-hand or obtained as a feed of information from publishers.  The second is the creative work of the descriptionist in adding value to the surrogate in the form of classification numbers, subject headings, abstracts, and the like.  The third is the additions that the computationalists &ndash; or, more specifically, their algorithms &ndash; bring to the object&rsquo;s description in the surrogate.  This can take the form of the previous discussed Google Book Search algorithms as well as Amazon&rsquo;s Capitalized Phrases and Statistically Improbable Phrases.  It also includes actions specific to our traditional domain of human-generated surrogates; for instance, of the algorithms OCLC runs across the Worldcat dataset to merge records and improve records.  And finally, thinking beyond the boundaries typical of AACR2 and MARC, there is a fourth type: user-contributed information.  The creative efforts of users to add tags, reviews, summaries, and commentary add to the surrogate, and with that we kick wide open a door to the problem of who &ldquo;owns&rdquo; these surrogate records.</p><p>The issue of who &ldquo;owns&rdquo; the user-contributed information to records is handled in a wide variety of ways.  In LibraryThing, for instance, the<a href="http://www.librarything.com/privacy#terms" title="LibraryThing terms of use"> creator retains copyright</a> over tags, reviews, summaries, and comments, and grants LibraryThing non-exclusive rights to make use of that creative effort.  LibraryThing also has a function where users can add &ldquo;Common Knowledge&rdquo; (character names and occupations, locations, honors/awards, and quotations, among other details) about the item.  Users <a href="http://www.librarything.com/wiki/index.php/Common_Knowledge_License" title="Common Knowledge License">add Common Knowledge augmentations with a Creative Commons &ldquo;By, Share-Alike&rdquo; license</a>.  The <a href="http://openlibrary.org/about/license" title="Open Library project license">Open Library project asserts no rights</a> over the data in its system; it declares the material in the open library database to be facts, and therefore in the public domain (at least under U.S. copyright law).  The newly announced <a href="http://biblios.net/pddl" title="biblios.net license">&Dagger;biblios.net repository</a> of records uses the Open Data Commons Public Domain Dedication and License, developed by Talis in the UK and Creative Commons.  It, too, asserts that the subject data is in the public domain and offers suggested community norms surrounding the use of the data.</p><p>Ownership of records is also a continuing source of discussion among members of the OCLC cooperative.  If a brief record from a publisher is added into the WorldCat database and is subsequently enhanced by one or more members, who &ldquo;owns&rdquo; the record.  If a library systematically adds enhancements to records that matter to its own community &ndash; enhancements such as paper and binding types &ndash; who &ldquo;owns&rdquo; those records?</p><p>One way to handle this variety of who (if anyone) owns portions of the surrogate is to split records based on who contributed what.  This would enable consuming systems to make decisions on what data to include based on the conditions the owners might put on their creative acts.  (Keep in mind that legal precedent would seem to indicate that the facts expressed in the surrogate couldn&rsquo;t be protected by copyright restrictions.)  But our existing record structures do not give us a way to do this, nor does there seem to be any work going on to enable this to happen.  Perhaps we are all just burying our collective heads in the sand and hoping it will go away.</p><p><h2>More to come&#8230;</h2><br /><a href="http://dltj.org/article/oclc-records-use-policy-2/">Part 2</a> reflects on the implication of restrictive licenses, with a focus on the now-withdrawn OCLC records use policy, and a call for open discussion.<p style="padding:0;margin:0;font-style:italic;">The text was modified to update a link from https://biblios.net/ to http://biblios.net/ on February 11th, 2011.</p><p style="padding:0;margin:0;font-style:italic;">The text was modified to update a link from https://biblios.net/pddl to http://biblios.net/pddl on February 11th, 2011.</p><div class='series_links'> <a href='http://dltj.org/article/oclc-records-use-policy-2/' title='Further Consideration of OCLC Records Use Policy'>Next in series</a></div>]]></content:encoded> <wfw:commentRss>http://dltj.org/article/oclc-records-use-policy-1/feed/</wfw:commentRss> <slash:comments>8</slash:comments> </item> <item><title>Midwinter Travel Tip:  Flying United?  Checking Luggage?  Save $3!</title><link>http://dltj.org/article/united-airlines-checked-baggage-savings/</link> <comments>http://dltj.org/article/united-airlines-checked-baggage-savings/#comments</comments> <pubDate>Tue, 20 Jan 2009 13:47:07 +0000</pubDate> <dc:creator>Peter Murray</dc:creator> <category><![CDATA[Meta Category]]></category> <category><![CDATA[ALA Midwinter 2009]]></category> <category><![CDATA[travel]]></category><guid isPermaLink="false">http://dltj.org/?p=685</guid> <description><![CDATA[United Airlines, along with many other carriers, has instituted a policy of charging for checked luggage. For United, the first bag is $15 and subsequent bags are $25 each. If you check-in for your flight online between now and January &#8230; <a href="http://dltj.org/article/united-airlines-checked-baggage-savings/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<abbr class="unapi-id ignore noPrint" title="http://dltj.org/?p=685"></abbr><p>United Airlines, along with many other carriers, has <a href="http://www.united.com/page/article/0,6722,52481,00.html?navSource=SidebarPromo&amp;linkTitle=UPDATED%3A+Checked+baggage+policy&amp;pos=1&amp;date=2009/01/12&amp;time=13" title="United Airlines - U.S./Canada checked baggage">instituted a policy of charging for checked luggage</a>.  For United, the first bag is $15 and subsequent bags are $25 each.  If you check-in for your flight online between now and January 31st, however, you can save $3 <del datetime="2009-01-22T02:03:38+00:00">on each</del> the first bag.  The online check-in process asks for your credit card to complete the transaction.  You can also print your boarding pass during the check-in process.  When you get to the airport, use the self-service kiosks to start your check-in process again.  The baggage tag will then automatically print behind the counter and you&#8217;ll soon be on your way.</p><p>This might be old news for some &#8212; it has been two years since I&#8217;ve been on a flight when I had to check a bag &#8212; but a combined 8-day trip of the OLE project in Lehigh University and the Midwinter meeting in Denver means I&#8217;ll be out longer than the typical carry-on bag will allow.  Still scheme for charging for bags based on a day&#8217;s flight activity seems a bit foreign to me.  The $15-per-day&#8217;s-itinerary doesn&#8217;t correlate to any actual charges I can think of.  If the main cost of handling checked bags was for the additional labor of handling them, I would expect charges for each <em>segment</em> of a day&#8217;s itinerary.  Likewise, if the charge is to handle the additional cost of fuel to transport the checked bag, it would make sense for the charge to be by segment.  So as near as I can figure out, with 15 minutes of thinking about the topic, the added baggage charge doesn&#8217;t really reflect the cost of actually transporting the bag and is just a way to collect more money.</p>]]></content:encoded> <wfw:commentRss>http://dltj.org/article/united-airlines-checked-baggage-savings/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>ALCTS Forum on Creating and Sustaining Communities Around Shared Library Data</title><link>http://dltj.org/article/alcts-forum-midwinter-2009/</link> <comments>http://dltj.org/article/alcts-forum-midwinter-2009/#comments</comments> <pubDate>Fri, 16 Jan 2009 20:03:55 +0000</pubDate> <dc:creator>Peter Murray</dc:creator> <category><![CDATA[Meeting]]></category> <category><![CDATA[ALA Midwinter 2009]]></category> <category><![CDATA[American Library Association]]></category> <category><![CDATA[description]]></category> <category><![CDATA[speaking]]></category><guid isPermaLink="false">http://dltj.org/?p=671</guid> <description><![CDATA[Community-shared metadata has certainly been a hot topic of late. It is timely, then that ALCTS is sponsoring a panel discussion about sharing library-created data inside and outside the library community at the upcoming ALA Midwinter meeting in Denver. From &#8230; <a href="http://dltj.org/article/alcts-forum-midwinter-2009/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description> <content:encoded><![CDATA[<abbr class="unapi-id ignore noPrint" title="http://dltj.org/?p=671"></abbr><div id="hcalendar-ALCTS-Forum" class="vevent">Community-shared metadata has certainly been a <a href="http://wiki.code4lib.org/index.php/OCLC_Policy_Change" title="OCLC Policy Change discussion">hot topic</a> of late.  It is timely, then that ALCTS is sponsoring <span class="description">a panel discussion about sharing library-created data inside and outside the library community</span> at the upcoming ALA Midwinter meeting in Denver.  From the panel description:<br /><blockquote>Panelists will share a variety of perspectives on community norms, policies, and best practices for accessing, using, and sharing the data that supports the discovery and delivery of library collections. What can libraries and the organizations that serve them learn from the open data movement and sites like Wikipedia? What principles and practices for shared data creation and maintenance will most help and strengthen libraries in the future? Panelists will also be addressing the changes in the OCLC Record Use Policy, particularly in light of the <a href="http://www.oclc.org/us/en/news/releases/20092.htm" title="Review Board on Shared Records [OCLC]">recent announcement</a> from OCLC on the establishment of the Review Board of Shared Data Creation and Stewardship.</p></blockquote><div style="float:right; padding: 1em 0 1.5em 3em; font-size: 80%; width: 100px; line-height: 95%"><a href="http://dltj.org/xhtml2vcal/xhtml2vcal.php/dltj/alcts-forum-midwinter-2009" title="Download iCal file" class="broken_link" rel="nofollow"><img src="http://cdn.dltj.org/wp-content/uploads/2009/01/microformat_hcalendar1.png" alt="hCalendar Encoded Microformat" width="80" height="15" style="border:none;text-decoration: none;" /><br />Add this event to your desktop calendar program.</a></div><p>The panel is called the <span class="summary">ALCTS Forum: Creating and Sustaining Communities Around Shared Library Data</span>, and it will be on January 26th from <abbr style="border:none;text-decoration: none;" title="2009-01-26T08:00-07:0000" class="dtstart">8:00am</abbr> to <abbr style="border:none;text-decoration: none;" title="2009-01-26T10:00-07:00" class="dtend">10:00am</abbr> at the <span class="location">Colorado Convention Center, Korbel Ballroom 3C</span>.  Yours truly has been asked to speak on shared catalog data from the perspective of a library membership organization (OhioLINK) that provides consortial access to a large union catalog, licensed content, dissertations, and digital media.  Also on the panel are:</p><ul type="disc"><li>Karen Calhoun (VP, OCLC WorldCat and Metadata Services), speaking on the environment for library data sharing and the process of revising OCLC&#8217;s 21-year-old Guidelines for the Use and Transfer of OCLC-Derived Records.</li><li><a href="http://orpheus.ucsd.edu/ucsdlibraries/brian.html" title="Brian Schottlaendar&#039;s homepage" class="broken_link" rel="nofollow">Brian Schottlaendar</a> (University Librarian, University of California San Diego), talking about library data sharing from his perspective as a library leader with a background in collections and technical services.</li><li><a href="http://everybodyslibraries.com/2009/01/14/chances-to-stop-and-think-about-the-future-of-library-catalogs/" title="Chances to stop and think about the future of library catalogs &amp;laquo; Everybody&amp;#8217;s Libraries">John Mark Ockerbloom</a> (Digital Library Planner &amp; Architect, University of Pennsylvania Libraries), on the perspective of a library practitioner with a keen interest in freely accessible data and content.</li></ul></div>]]></content:encoded> <wfw:commentRss>http://dltj.org/article/alcts-forum-midwinter-2009/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> </channel> </rss>
<!-- Served from: dltj.org @ 2012-02-11 11:29:33 by W3 Total Cache -->
