<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (rybesh)</title>
    <link>https://pinboard.in/u:rybesh/public/</link>
    <description>recent bookmarks from rybesh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://wikiframe.library.unlv.edu/"/>
	<rdf:li rdf:resource="https://go-to-hellman.blogspot.com/2023/12/the-revenge-of-cataloguers.html"/>
	<rdf:li rdf:resource="https://twitter.com/lisalibrarian/status/1277992040136048641"/>
	<rdf:li rdf:resource="https://coronavirus.illinois.gov/s/restore-illinois-phase-5"/>
	<rdf:li rdf:resource="https://id.ndl.go.jp/information/about_en/"/>
	<rdf:li rdf:resource="https://github.com/cmh2166/cmh2166.github.io/blob/master/_posts/2015-09-23-notes-on-being-a-metadata-supervisor.md"/>
	<rdf:li rdf:resource="https://twitter.com/i/web/status/1001085828670640129"/>
	<rdf:li rdf:resource="http://www.dreamcorps.org/en/aboutus.html"/>
	<rdf:li rdf:resource="https://archive.org/details/Kohacon2010OpenLibraryPresentation-GeorgeOates"/>
	<rdf:li rdf:resource="http://www.dlib.org/dlib/november15/vandesompel/11vandesompel.html"/>
	<rdf:li rdf:resource="http://guild2910.org/Pelopponesian%20War%20June%2013%202007.pdf"/>
	<rdf:li rdf:resource="http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0137041"/>
	<rdf:li rdf:resource="http://www.ala.org/advocacy/intfreedom/statementspols/corevalues"/>
	<rdf:li rdf:resource="https://gforge.inria.fr/projects/cendari-vre/"/>
	<rdf:li rdf:resource="http://www.aviz.fr/Research/CENDARI"/>
	<rdf:li rdf:resource="http://www.against-the-grain.com/2014/02/an-atg-original-university-presses-facing-enormous-tectonic-shift-in-publishing/"/>
	<rdf:li rdf:resource="http://homepages.gac.edu/~fister/HackingKnowledge.pdf"/>
	<rdf:li rdf:resource="http://arxiv.org/pdf/1302.4591v2.pdf"/>
	<rdf:li rdf:resource="http://scholar.google.com/citations?view_op=top_venues&amp;hl=en&amp;vq=eng_libraryinformationscience"/>
	<rdf:li rdf:resource="http://www.loc.gov/marc/transition/pdf/marcld-report-11-21-2012.pdf"/>
	<rdf:li rdf:resource="http://www.niso.org/publications/isq/2012/v24no2-3/"/>
	<rdf:li rdf:resource="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=2102542"/>
	<rdf:li rdf:resource="http://www.hathitrust.org/bib_api"/>
	<rdf:li rdf:resource="http://www.hathitrust.org/data_api"/>
	<rdf:li rdf:resource="http://www.hathitrust.org/data"/>
	<rdf:li rdf:resource="http://d2i.indiana.edu/htrc/uncamp2012/"/>
	<rdf:li rdf:resource="https://clojars.org/"/>
	<rdf:li rdf:resource="http://www.inthelibrarywiththeleadpipe.org/2012/answering-questions-about-library-impact-on-student-learning/"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.jp/2012/05/frbr-frad-isbd-in-ld-by-bne.html"/>
	<rdf:li rdf:resource="http://www.gbv.de/wikis/cls/DAIA_-_Document_Availability_Information_API"/>
	<rdf:li rdf:resource="http://hangingtogether.org/?p=1690"/>
	<rdf:li rdf:resource="http://www.loc.gov/catdir/cpso/romlandscape_Oct2011.html"/>
	<rdf:li rdf:resource="http://topics.cs.princeton.edu/Science/"/>
	<rdf:li rdf:resource="http://libraryjuicepress.com/blog/?cat=58"/>
	<rdf:li rdf:resource="http://www.oclc.org/research/publications/library/2010/2010-06.pdf"/>
	<rdf:li rdf:resource="http://libraryjuicepress.com/blog/?p=3280"/>
	<rdf:li rdf:resource="http://www.arl.org/bm~doc/spec-326-web.pdf"/>
	<rdf:li rdf:resource="http://people.ischool.berkeley.edu/~buckland/otlet.html"/>
	<rdf:li rdf:resource="http://www.w3.org/2005/Incubator/lld/XGR-lld-20111025/"/>
	<rdf:li rdf:resource="http://www.w3.org/2005/Incubator/lld/XGR-lld-vocabdataset-20111025/"/>
	<rdf:li rdf:resource="http://www.cira.ch/"/>
	<rdf:li rdf:resource="http://www.w3.org/2005/Incubator/lld/wiki/DraftReportWithTransclusion"/>
	<rdf:li rdf:resource="http://www.libraryjournal.com/lj/home/891826-264/how_the_w3c_has_come.html.csp"/>
	<rdf:li rdf:resource="http://www.opencontentalliance.org/2009/08/04/google-at-their-word/"/>
	<rdf:li rdf:resource="http://michaelzimmer.org/2009/05/13/stutzman-google-exposes-book-search-patron-records/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://wikiframe.library.unlv.edu/">
    <title>WikiframeVG - Wikidata Discovery Tool</title>
    <dc:date>2024-03-25T15:57:24+00:00</dc:date>
    <link>https://wikiframe.library.unlv.edu/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Welcome to wikiframeVG (Wikiframe Visual Graph), an open-source community initiative and tool aimed to help Wikidata editors and users explore knowledge generated from organized Wikidata sprints. wikiframeVG adopts a community driven, SPARQL template-based approach toward Wikidata graph exploration.

The application interacts with Wikidata's SPARQL query service and provides users with point-and-click tools to search and filter information. No SPARQL or other coding knowledge will be required to retrieve data linked across the Wikidata knowledge graph.]]></description>
<dc:subject>wikidata libraries visualization inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:63fc7a879538/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikidata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://go-to-hellman.blogspot.com/2023/12/the-revenge-of-cataloguers.html">
    <title>Go To Hellman: The Revenge of the Cataloguers</title>
    <dc:date>2023-12-15T14:35:24+00:00</dc:date>
    <link>https://go-to-hellman.blogspot.com/2023/12/the-revenge-of-cataloguers.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[What gets me really excited though, is thinking about how a library of the future will interact with content. I expect users will interact with the library using a pre-trained language model, rather than via databases. Content will get added to the model using packages of statistical vectors, compiled by human-expert-assisted content processors. These human experts won't be called "cataloguers" any longer but rather "meaning advisors". Or maybe "biblio-epistemologists". The  revenge of the cataloguers will be that because of the great responsibilities and breadth of expertise required, biblio-epistemologists will command salaries well exceeding the managers and programmers who will just take orders from well-trained AIs.]]></description>
<dc:subject>libraries language models cataloging description</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8dbee1a8c358/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:models"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/lisalibrarian/status/1277992040136048641">
    <title>Twitter</title>
    <dc:date>2020-06-30T17:53:15+00:00</dc:date>
    <link>https://twitter.com/lisalibrarian/status/1277992040136048641</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RT @jschneider: Great to hear - as an @Illinois_Alma faculty member!

For #academiclibraries in other states comparing, "phase 5" is "Illinois Restored" (vaccine/treatment/no new cases for a sustained period). 

#libraries #pandemic #adaptation ]]></description>
<dc:subject>academiclibraries adaptation libraries pandemic</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a06ba8c729f4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:academiclibraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:adaptation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pandemic"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://coronavirus.illinois.gov/s/restore-illinois-phase-5">
    <title>Corona</title>
    <dc:date>2020-06-30T17:53:15+00:00</dc:date>
    <link>https://coronavirus.illinois.gov/s/restore-illinois-phase-5</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RT @jschneider: Great to hear - as an @Illinois_Alma faculty member!

For #academiclibraries in other states comparing, "phase 5" is "Illinois Restored" (vaccine/treatment/no new cases for a sustained period). 

#libraries #pandemic #adaptation ]]></description>
<dc:subject>academiclibraries adaptation libraries pandemic</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5c33a1e84a65/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:academiclibraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:adaptation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pandemic"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://id.ndl.go.jp/information/about_en/">
    <title>About Web NDL Authorities « Web NDL Authoritiesについて</title>
    <dc:date>2019-10-09T23:59:46+00:00</dc:date>
    <link>https://id.ndl.go.jp/information/about_en/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Web NDL Authorities is a service by the National Diet Library (NDL), Japan, to access authority data created and maintained by the NDL.

In addition to being able to search authority data via “keyword search”, “classification number search” and “authority ID search”, you can download individual files of all types of the authority data and batch files of the National Diet Library Subject Headings (NDLSH).

Web NDL Authorities provides a variety of search functions, including search for the relevant bibliographic data by author or subject headings in collaboration with NDL Search.

Web NDL Authorities is based technically on the Semantic Web, which assigns semantically clear data to information resources on the Web. Each record in the authority data can be referenced via a URI in conformance to the Resource Description Framework (RDF) data model, and is searchable via SPARQL.

Authority data is automatically updated daily with new additions, corrections, and deletions. Additionally, notifications are provided via RSS feed for newly established subject headings within the NDLSH.]]></description>
<dc:subject>japan linkeddata libraries authority</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:807c21059dc9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:japan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authority"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/cmh2166/cmh2166.github.io/blob/master/_posts/2015-09-23-notes-on-being-a-metadata-supervisor.md">
    <title>Christina Harlow - Notes on being a metadata supervisor</title>
    <dc:date>2018-08-03T11:24:09+00:00</dc:date>
    <link>https://github.com/cmh2166/cmh2166.github.io/blob/master/_posts/2015-09-23-notes-on-being-a-metadata-supervisor.md</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[> I especially want to divorce cataloging expertise from knowing how to work with a particular ILS or OCLC Connexion editor.

> In the Ithaka S+R US Library Survey 2013, the question “Will your library add or reduce staff resources in any of the following areas over the next 5 years?” showed a steep decline of staff resources for technical services in response - close to 30%, and far more of a decline than any other academic library area mentioned in the context of this question. However, we see a lot of growth in response to that question for areas that can use the data expertise currently under-tapped in cataloging and metadata work: areas such as Digital preservation and archiving; Archives, rare books, and special collections; Assessment and data analytics; Specialized faculty research support (including data management); and Electronic resources management. This all uses the skills of cataloging and metadata workers in different ways

> content specialists are more often the metadata creators in digital collections, and catalogers need to be brought in increasingly for data review, remediation, enhancement, and education/outreach. Don't think this will happen with MARC records? I think it already is when we consider the poor state of most vendor MARC records we often accept.

]]></description>
<dc:subject>metadata cataloging libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:10a17e012f68/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/i/web/status/1001085828670640129">
    <title>Twitter</title>
    <dc:date>2018-05-28T16:48:45+00:00</dc:date>
    <link>https://twitter.com/i/web/status/1001085828670640129</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[RT @IDRC_CRDI: NEW BOOK! Shadow #Libraries is our latest book with @MITPress that explores #access to knowledge in #dev countries.… ]]></description>
<dc:subject>access Libraries dev</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d2c740656560/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:access"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:dev"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.dreamcorps.org/en/aboutus.html">
    <title>About Us | Dream Corps International</title>
    <dc:date>2017-05-05T18:09:18+00:00</dc:date>
    <link>http://www.dreamcorps.org/en/aboutus.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Dream Corps was founded in North Carolina by Chinese scholars and students in 2004. In September 2010，we welcomed our first full time staff, raising our standards for program operations and internal management.
We aim to improve the environment for learning and development of children in rural China. We hope to encourage them to realize their full potential, unfettered by the lack of resources and the economic conditions that they are born into. We also hope to involve privileged youth in projects that cultivate their sense of social responsibility.]]></description>
<dc:subject>china libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:024004834099/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:china"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://archive.org/details/Kohacon2010OpenLibraryPresentation-GeorgeOates">
    <title>KohaCon 2010 Open Library presentation - George Oates : George Oates : Free Download &amp; Streaming : Internet Archive</title>
    <dc:date>2017-04-04T18:28:14+00:00</dc:date>
    <link>https://archive.org/details/Kohacon2010OpenLibraryPresentation-GeorgeOates</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An introduction to Open Library for the awesome open source Koha Open Source Library Software system.]]></description>
<dc:subject>libraries interface design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:629447983cf1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:interface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.dlib.org/dlib/november15/vandesompel/11vandesompel.html">
    <title>Reminiscing About 15 Years of Interoperability Efforts</title>
    <dc:date>2016-10-19T12:26:05+00:00</dc:date>
    <link>http://www.dlib.org/dlib/november15/vandesompel/11vandesompel.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Over the past fifteen years, our perspective on tackling information interoperability problems for web-based scholarship has evolved significantly. In this opinion piece, we look back at three efforts that we have been involved in that aptly illustrate this evolution: OAI-PMH, OAI-ORE, and Memento. Understanding that no interoperability specification is neutral, we attempt to characterize the perspectives and technical toolkits that provided the basis for these endeavors. With that regard, we consider repository-centric and web-centric interoperability perspectives, and the use of a Linked Data or a REST/HATEAOS technology stack, respectively. We also lament the lack of interoperability across nodes that play a role in web-based scholarship, but end on a constructive note with some ideas regarding a possible path forward.]]></description>
<dc:subject>web libraries inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f34020eee284/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://guild2910.org/Pelopponesian%20War%20June%2013%202007.pdf">
    <title>The Peloponnesian War and the Future of Reference, Cataloging, and Scholarship in Research Libraries</title>
    <dc:date>2016-09-01T17:11:39+00:00</dc:date>
    <link>http://guild2910.org/Pelopponesian%20War%20June%2013%202007.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The paper is an examination of the overall principles and practices of both reference service and cataloging operations in the promotion of scholarly research, pointing out important differences not just in content available onsite and offsite, but also among necessary search techniques. It specifies the differences between scholarship and quick information seeking, and examines the implications of those differences for the future of cataloging. It examines various proposals that the profession should concentrate its efforts on alternatives to cataloging: relevance ranking, tagging, under-the-hood programming, etc. The paper considers the need for, and requirements of, education of researchers; and it examines in detail many of the glaring disconnects between theory and practice in the library profession today. Finally, it provides an overview of the whole “shape of the elephant” of library services, within which cataloging is only one component.]]></description>
<dc:subject>libraries cataloging reference inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6149ac135902/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0137041">
    <title>PLOS ONE: Characterizing the Google Books Corpus: Strong Limits to Inferences of Socio-Cultural and Linguistic Evolution</title>
    <dc:date>2015-10-14T12:37:45+00:00</dc:date>
    <link>http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0137041</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[It is tempting to treat frequency trends from the Google Books data sets as indicators of the “true” popularity of various words and phrases. Doing so allows us to draw quantitatively strong conclusions about the evolution of cultural perception of a given topic, such as time or gender. However, the Google Books corpus suffers from a number of limitations which make it an obscure mask of cultural popularity. A primary issue is that the corpus is in effect a library, containing one of each book. A single, prolific author is thereby able to noticeably insert new phrases into the Google Books lexicon, whether the author is widely read or not. With this understood, the Google Books corpus remains an important data set to be considered more lexicon-like than text-like. Here, we show that a distinct problematic feature arises from the inclusion of scientific texts, which have become an increasingly substantive portion of the corpus throughout the 1900s. The result is a surge of phrases typical to academic articles but less common in general, such as references to time in the form of citations. We use information theoretic methods to highlight these dynamics by examining and comparing major contributions via a divergence measure of English data sets between decades in the period 1800–2000. We find that only the English Fiction data set from the second version of the corpus is not heavily affected by professional texts. Overall, our findings call into question the vast majority of existing claims drawn from the Google Books corpus, and point to the need to fully characterize the dynamics of the corpus before using these data sets to draw broad conclusions about cultural and linguistic evolution.]]></description>
<dc:subject>digitalhumanities textanalysis libraries bigdata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:820c79b26249/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:textanalysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bigdata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ala.org/advocacy/intfreedom/statementspols/corevalues">
    <title>Core Values of Librarianship | Advocacy, Legislation &amp; Issues</title>
    <dc:date>2015-02-05T17:11:38+00:00</dc:date>
    <link>http://www.ala.org/advocacy/intfreedom/statementspols/corevalues</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The foundation of modern librarianship rests on an essential set of core values that define, inform, and guide our professional practice. These values reflect the history and ongoing development of the profession and have been advanced, expanded, and refined by numerous policy statements of the American Library Association. Among these are:

Access
Confidentiality/Privacy
Democracy
Diversity
Education and Lifelong Learning
Intellectual Freedom
Preservation
The Public Good
Professionalism
Service
Social Responsibility]]></description>
<dc:subject>libraries values</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0557bada4ece/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:values"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gforge.inria.fr/projects/cendari-vre/">
    <title>INRIAGForge: EditorsNotes: Cendari: Project Home</title>
    <dc:date>2014-04-18T17:43:14+00:00</dc:date>
    <link>https://gforge.inria.fr/projects/cendari-vre/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[CENDARI (Virtual Research Environment for historians based on note taking) project source code repos.]]></description>
<dc:subject>history research editorsnotes archives visualization semweb digitalhumanities libraries hci</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2e6dadb85e9a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hci"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.aviz.fr/Research/CENDARI">
    <title>CENDARI</title>
    <dc:date>2014-04-18T17:42:13+00:00</dc:date>
    <link>http://www.aviz.fr/Research/CENDARI</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Collaborative EuropeaN Digital Archive Infrastructure (CENDARI) will provide and facilitate access to existing archives and resources in Europe for the study of medieval and modern European history (specifically the First World War period) through the development of an ‘enquiry environment’.
This environment will increase access to records of historic importance across the European Research Area, creating a powerful new platform for accessing and investigating historical data in a transnational fashion overcoming the national and institutional data silos that now exist. It will leverage the power of the European infrastructure for Digital Humanities (DARIAH) bringing these technical experts together with leading historians and existing research infrastructures (archives, libraries and individual digital projects) within a programme of technical research informed by cutting edge reflection on the impact of the digital age on scholarly practice.]]></description>
<dc:subject>history research editorsnotes archives visualization semweb digitalhumanities libraries hci</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0dad248f6dcc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hci"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.against-the-grain.com/2014/02/an-atg-original-university-presses-facing-enormous-tectonic-shift-in-publishing/">
    <title>University Presses Facing ‘Enormous Tectonic Shift’ in Publishing | Against-the-Grain.com</title>
    <dc:date>2014-02-19T19:19:43+00:00</dc:date>
    <link>http://www.against-the-grain.com/2014/02/an-atg-original-university-presses-facing-enormous-tectonic-shift-in-publishing/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[University presses have worked hard to establish their reputation for high quality scholarly monographic and journal publication. In 2011, these presses were poised at the forefront of the transition to ebooks in the research sector. Even then, press directors were quick to point to “enormous tectonic shifts” yet to come in the transition to 21st century scholarly publishing.

The past three years have seen major changes and challenges to these presses, with potentially competing publishing initiatives from campus libraries and efforts by many universities to re-evaluate the role and organizational structure of their university presses.

]]></description>
<dc:subject>openaccess libraries scholarlycommunication publishing pubberlin</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:403f828f05e8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:openaccess"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pubberlin"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://homepages.gac.edu/~fister/HackingKnowledge.pdf">
    <title>Hacking Knowledge: Information Literacy as Creative Participation</title>
    <dc:date>2013-05-19T18:13:09+00:00</dc:date>
    <link>http://homepages.gac.edu/~fister/HackingKnowledge.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[What is information literacy for? Is it to help students succeed in college? To learn how to enter the conversations that scholars engage in? To enable students to create new knowledge? To give students tools to change the world? Though we may say "all of the above," our approaches to teaching and learning often focus on immediate needs ("how can I find five scholarly sources for my paper?") at the expense of deeper, more complex kinds of learning. We will unpack the unintended messages we often send when modeling the research process, examine the ways library systems position researchers as consumers rather than creators, and explore ways to invite students to hack the library and claim it as an intellectual maker space. If information literacy is preparation for lifelong learning, we need to consider the changing world we are sending our students into - and what we librarians can do to change it for the better.]]></description>
<dc:subject>information literacy knowledge research teaching libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2fa13e1cab27/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:literacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:teaching"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://arxiv.org/pdf/1302.4591v2.pdf">
    <title>Linking Things on the Web: A Pragmatic Examination of Linked Data for Libraries, Archives and Museums</title>
    <dc:date>2013-02-21T20:22:21+00:00</dc:date>
    <link>http://arxiv.org/pdf/1302.4591v2.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Web publishing paradigm of Linked Data has been gaining traction in the cultural heritage sector: libraries, archives and museums. At first glance, the principles of Linked Data seem simple enough. However experienced Web developers, designers and architects who attempt to put these ideas into practice often find themselves having to digest and understand debates about Web architecture, the semantic web, artificial intelligence and the philosophical nature of identity. In this paper I will discuss some of the reasons why Linked Data is of interest to the cultural heritage community, what some of the pain points are for deploying it, and characterize some pragmatic ways for cultural heritage organizations to realize the goals of Linked Data with examples from the Web we have today.]]></description>
<dc:subject>linkeddata libraries archives museum inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:63806d79d855/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:museum"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://scholar.google.com/citations?view_op=top_venues&amp;hl=en&amp;vq=eng_libraryinformationscience">
    <title>Library &amp; Information Science - Google Scholar Metrics</title>
    <dc:date>2012-11-27T02:14:13+00:00</dc:date>
    <link>http://scholar.google.com/citations?view_op=top_venues&amp;hl=en&amp;vq=eng_libraryinformationscience</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Top publications in Library & Information Science, according to Google.]]></description>
<dc:subject>academia journal libraries information science</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7f0869ae7b81/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:academia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:journal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:science"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loc.gov/marc/transition/pdf/marcld-report-11-21-2012.pdf">
    <title>Bibliographic Framework as a Web of Data: Linked Data Model and Supporting Services</title>
    <dc:date>2012-11-27T02:02:25+00:00</dc:date>
    <link>http://www.loc.gov/marc/transition/pdf/marcld-report-11-21-2012.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document provides a draft Linked Data model for the new Bibliographic Framework and identiﬁes a set of additional issues that will help shape the future of this work.  This Bibliographic Framework (BIBFRAME) Linked Data model is designed to be a basis for community discussion and dialog.  It is not complete.  Nor,  if this model is effective, will it ever be “complete” as it can and should be extended to support a range of new applications and descriptive assets that we currently can not imagine.]]></description>
<dc:subject>linkeddata libraries loc</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b3c12d8026d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:loc"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.niso.org/publications/isq/2012/v24no2-3/">
    <title>Spring/Summer 2012 (v.24 no.2/3) - National Information Standards Organization</title>
    <dc:date>2012-09-13T18:50:48+00:00</dc:date>
    <link>http://www.niso.org/publications/isq/2012/v24no2-3/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Special issue of Information Standards Quarterly on Linked Data in Libraries, Archives, and Museums.]]></description>
<dc:subject>linkeddata standards libraries archives museum</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2f3df1075855/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:museum"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=2102542">
    <title>Brief of Digital Humanities and Law Scholars as Amici Curiae in Authors Guild v. Google by Matthew Jockers, Matthew Sag, Jason Schultz :: SSRN</title>
    <dc:date>2012-09-10T18:54:09+00:00</dc:date>
    <link>http://papers.ssrn.com/sol3/papers.cfm?abstract_id=2102542</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[How Copyright Law Could Make or Break the Future for Digital Humanities.

This case raises many legal, technical, and epistemological issues related to the future of higher education, research, and scholarship – especially those efforts that seek to take advantage of “big data” analytics and methodologies. Advances in computer technology and the availability of digital texts will allow scholars of the humanities a chance to do what biologists, physicists and economists have been doing for decades – analyze massive amounts of data. Large-scale quantitative projects like those being undertaken at the Stanford Literary Lab are unearthing previously unknowable information about individual works, and entire genres of literature.

Researchers working in Information Retrieval frequently use text mining and computer-aided classification to identify and retrieve relevant documents. Using similar techniques, researchers in the Digital Humanities are able to identify and retrieve relevant texts, often from unlikely places. Humanities researchers can thereby expand their traditional study of a few canonical works to a study of any one of the several million books in the larger archive of literary history—an archive that has hitherto remained hidden because of the limitations of humans’ reading capacity.

In this amicus brief scholars from disciplines including law, computer science, linguistics, history and literature ask the court to consider the impact on this vital area of research when ruling on the legality of mass digitization. Specifically, the brief addresses whether United States copyright law should stand as an obstacle to statistical and computational analysis of the millions of books owned by the nation’s great university libraries. 

The brief argues that, just as copyright law has long recognized the distinction between protection for an author’s original expression (e.g., the narrative prose describing the plot) and the public’s right to access the facts and ideas contained within that expression (e.g., a list of characters or the places they visit), the law must also recognize the distinction between copying books for expressive purposes (e.g., reading) and nonexpressive purposes, such as extracting metadata and conducting macroanalyses. We amici urge the court to follow established precedent with respect to Internet search engines, software reverse engineering, and plagiarism detection software and to hold that the digitization of books for text-mining purposes is a form of incidental or intermediate copying to be regarded as fair use as long as the end product is also nonexpressive or otherwise non-infringing.

This brief updates the brief filed in Authors Guild v. HathiTrust.]]></description>
<dc:subject>copyright digitalhumanities HathiTrust digital libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a98dbc498069/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:HathiTrust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digital"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.hathitrust.org/bib_api">
    <title>HathiTrust Bibliographic API | HathiTrust Digital Library</title>
    <dc:date>2012-09-10T18:15:37+00:00</dc:date>
    <link>http://www.hathitrust.org/bib_api</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This API returns bibliographic, rights, and volume information when given a single or multiple standard identifiers (ISBN, LCCN, OCLC, etc.). It is intended for use to retrive information about small numbers of items at a time. Bulk retrieval should be done using OAI or the HathiTrust tab-delimited inventory files, as described at http://www.hathitrust.org/data. Note that use of the data may be subject to third-party agreements, such as OCLC's Record Use policy. Permission must be sought for bulk retrieval of OCLC records by non-OCLC members.]]></description>
<dc:subject>HathiTrust bibliography data api digital libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:06a14396aea2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:HathiTrust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digital"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.hathitrust.org/data_api">
    <title>HathiTrust Data API | HathiTrust Digital Library</title>
    <dc:date>2012-09-10T18:14:34+00:00</dc:date>
    <link>http://www.hathitrust.org/data_api</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document describes a RESTful API to provide access to HathiTrust repository data and metadata resources. The HathiTrust Repository Data (HTD) API is referred to simply as API in this document.]]></description>
<dc:subject>HathiTrust data api digital libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f6d36553eb85/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:HathiTrust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digital"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.hathitrust.org/data">
    <title>Data Availability and APIs | HathiTrust Digital Library</title>
    <dc:date>2012-09-10T18:12:46+00:00</dc:date>
    <link>http://www.hathitrust.org/data</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[HathiTrust distributes information about items in the repository (and items themselves where possible) through a variety of mechanisms.]]></description>
<dc:subject>hathitrust digital libraries data api metadata bibliography</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2acfa3c986f3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hathitrust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digital"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://d2i.indiana.edu/htrc/uncamp2012/">
    <title>HTRC UnCamp2012 | Data to Insight Center</title>
    <dc:date>2012-09-10T16:49:13+00:00</dc:date>
    <link>http://d2i.indiana.edu/htrc/uncamp2012/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[HTRC UnCamp. HTRC is hosting its first annual HTRC UnCamp in September 2012 at Indiana University in Bloomington. The UnCamp is different: it is part hands-on coding and demonstration, part inspirational use-cases, part community building, and a part informational, all structured in the dynamic setting of an un-conference programming format. It has visionary speakers mixed with boot-camp activities and hands-on sessions with HTRC infrastructure and tools. Through the HTRC Data API, attendees will be able to browse and run applications (yours or ours) against the full 2.8M volumes of the public domain corpus of HathiTrust. Bloomington is lovely in September and the IU campus is noted as one of the most beautiful public university campuses in the nation.]]></description>
<dc:subject>events digital libraries textanalysis tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d3a1746ed31a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:events"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digital"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:textanalysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://clojars.org/">
    <title>Clojars</title>
    <dc:date>2012-09-01T21:46:20+00:00</dc:date>
    <link>https://clojars.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Clojars is a dead easy community repository for open source Clojure libraries.]]></description>
<dc:subject>clojure libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:af15ff0ced11/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:clojure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.inthelibrarywiththeleadpipe.org/2012/answering-questions-about-library-impact-on-student-learning/">
    <title>In the Library with the Lead Pipe » Answering questions about library impact on student learning</title>
    <dc:date>2012-07-14T02:38:54+00:00</dc:date>
    <link>http://www.inthelibrarywiththeleadpipe.org/2012/answering-questions-about-library-impact-on-student-learning/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This essay reports on a project which evaluated the Understanding Library Impacts (ULI) protocol, a suite of instruments for detecting and communicating library impact on student learning. The project was a dissertation study conducted with undergraduates enrolled in upper-level and capstone history classes at six U.S. colleges and universities in 2011. My first essay for In the Library with The Lead Pipe introduced the protocol and provided background on the approach. This essay uses selected results from the 2011 project to demonstrate how the protocol works and suggests ways readers can get involved with future ULI projects.]]></description>
<dc:subject>learning libraries evaluation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0389f01b13c4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:learning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:evaluation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.jp/2012/05/frbr-frad-isbd-in-ld-by-bne.html">
    <title>Coyle's InFormation: FRBR, FRAD, ISBD in LD by BNE</title>
    <dc:date>2012-05-30T23:02:17+00:00</dc:date>
    <link>http://kcoyle.blogspot.jp/2012/05/frbr-frad-isbd-in-ld-by-bne.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[More and more I come to the conclusion that in the linked data space the thing we seem to focus on today, descriptive cataloging, will be less useful than the entities that are represented by our authority data.]]></description>
<dc:subject>linkeddata libraries authority naming cataloging</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cd20a7d16b34/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:authority"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:naming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.gbv.de/wikis/cls/DAIA_-_Document_Availability_Information_API">
    <title>DAIA - Document Availability Information API – Verbund-Wiki GBV</title>
    <dc:date>2012-05-23T21:58:22+00:00</dc:date>
    <link>http://www.gbv.de/wikis/cls/DAIA_-_Document_Availability_Information_API</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Document Availability Information API (DAIA) defines a data model with serializations in JSON and XML to encode information about the current availability of documents. This document defines the serialization formats DAIA/JSON and DAIA/XML and a HTTP query API to query DAIA information.]]></description>
<dc:subject>libraries api webservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:038603b21ad8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://hangingtogether.org/?p=1690">
    <title>hangingtogether.org » Blog Archive » Thick Description: Fingerprints, Sonnets, and Aboutness in Special Collections</title>
    <dc:date>2012-05-17T20:43:55+00:00</dc:date>
    <link>http://hangingtogether.org/?p=1690</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Archivists and librarians contribute to discovery when they discard illusions of neutrality and express their excitement for the materials and their opinions about their significance.]]></description>
<dc:subject>archives libraries description editorsnotes</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5db8d068efcd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editorsnotes"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loc.gov/catdir/cpso/romlandscape_Oct2011.html">
    <title>Romanization Landscape</title>
    <dc:date>2012-05-17T18:56:39+00:00</dc:date>
    <link>http://www.loc.gov/catdir/cpso/romlandscape_Oct2011.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[MARC formatting conventions and US practice put romanized forms in the ”regular” MARC fields, with parallel fields for the original scripts to support systems with the capability to handle one or both scripts. However, most library systems still cannot accept the entire Unicode “repertoire” of characters for all scripts and some still cannot accept any non-Latin scripts.]]></description>
<dc:subject>language writing notation libraries standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:62aa104b192a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:notation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://topics.cs.princeton.edu/Science/">
    <title>Modeling the Evolution of Science</title>
    <dc:date>2012-05-11T16:33:09+00:00</dc:date>
    <link>http://topics.cs.princeton.edu/Science/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This browseable 75-topic dynamic topic model of the Journal Science (1880-2002) is part of the on-line supplement to the submission "Modeling the Evolution of Science." This browser allows a user to visualize the dynamic topic model, and use the hidden topics that it has uncovered to guide an exploration of the original collection of documents.]]></description>
<dc:subject>linguistics topicmodels classification science libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0bdcff06089a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linguistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:topicmodels"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://libraryjuicepress.com/blog/?cat=58">
    <title>Beyond Access - Alan Mattlage</title>
    <dc:date>2012-05-04T14:13:10+00:00</dc:date>
    <link>http://libraryjuicepress.com/blog/?cat=58</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[...librarians must begin to de-emphasize the value of access in general and re-emphasize their role as research assistants. We need to provide our patrons with the reader advisory services that were once a core element of our work. In academic libraries, this can be done most readily by creating guides to the literature, but those guides need to go far beyond what we see in most guides.  They need to be more than simply lists of useful databases and video tutorials on using various search tools.  They need to do such things as introduce patrons to the nature of the field of study, provide a history of its devepment, and identify its most important figures, and its classic and important current works.  Library administrations will need  to hire subject specialists with significant expertise,  who are potentially capable of teaching courses in the departments they serve. 

Of course, this presents a challenge to our desire to remain “neutral” or “unbiased” with regard to the subject matter that we make available, but we need not shy away from the challenge. We must conscientiously identify the information that we judge to be most worthwhile, while remaining reasonably humble about our abilities to discriminate the wheat from the chaff.  We need to exercise our  right to the freedoms that our teaching colleagues have in expressing our views about our fields of expertise.  We owe it to our patrons to apply our professional judgment about the value of the resources available to them and not simply serve as human cogs in an access providing machine.]]></description>
<dc:subject>libraries access epistemology policy values</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:28c169dbf690/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:access"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:epistemology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:policy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:values"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.oclc.org/research/publications/library/2010/2010-06.pdf">
    <title>Implications of MARC Tag Usage on Library Metadata Practices</title>
    <dc:date>2012-02-15T15:58:11+00:00</dc:date>
    <link>http://www.oclc.org/research/publications/library/2010/2010-06.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Only a small subset of MARC 21 fields are used in WorldCat. Even when considering the MARC fields that are heavily used in non-book formats, there are 
only 21 to 30 tags that occur in 10% or more records. ]]></description>
<dc:subject>libraries cataloging metadata inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ad15fd8897fb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://libraryjuicepress.com/blog/?p=3280">
    <title>Library Juice » Data Mining</title>
    <dc:date>2012-02-06T22:56:11+00:00</dc:date>
    <link>http://libraryjuicepress.com/blog/?p=3280</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[ Austin et al. point out that the statistical methods that are at the heart of data mining are not able to distinguish real from spurious associations. Data mining employs the automated examination of enormous bodies of data. Its usefulness is thought to be proportional to the size of the data set that it collates; however, as the data set becomes larger and as the number of attributes that serve as potential relata increases, the number of potential relationships increases exponentially. Importantly, the number of spurious associations also increases. With enough data, no significance test will be stringent enough to provide assurance against the kind of results found in Austin et al. What is needed, according to Austin et al. is a “pre-specified plausible hypothesis.” For statistical analysis to be useful, the researcher must begin with a hypothesis, preferably a plausible one, if the research is to be valuable.

What exactly is a pre-specified plausible hypothesis and how can we generate it if data mining can’t do that for us? The question was posed some sixty years ago by the philosopher Nelson Goodman using different terms: Goodman believed that a critical question for epistemology was to distinguish between “projectible and non-projectible hypotheses.” One can more or less replace “pre-specified plausible hypothesis” with Goodman’s term “projectible hypothesis.” According to Goodman, when we seek to understand what hypothesis is (or is not) projectible, we do not come to the problem “empty-headed but with some stock of knowledge” which we use to determine what is (or is not) projectible. Projectible hypotheses will be those which do not conflict with other hypotheses that have been supported in the past. They will commonly use the same terminology of previously supported hypotheses. The terminology appearing in the hypotheses will have become “entrenched” in the language. This goes a long distance toward explaining why we don’t find the link between one’s astrological sign and medical conditions plausible. Twenty-first century Western medicine is not accustomed to linking astrological signs to ailments and so must find any hypothesis that does so implausible.

If Goodman is correct, then data mining is of little use without an historical understanding of the field of science to which the data pertains.

...

Here, we have another argument for allocating library resources to pay for librarians with deep subject expertise. As e-science develops, vendors will make more and more data sets available, regardless of their actual worth to researchers. To effectively choose the data sets that are of value, librarians must have a thorough understanding of the research needs of their patrons. To do this, they must have a deep understanding of the field. Unfortunately, with the excitement swirling around e-science, the mere access to large data sets threatens to become the be-all and end-all in collection management. If we aren’t careful, we may find ourselves with mountains of data from which everything and nothing can be concluded.]]></description>
<dc:subject>datamining statistics knowledge digitalhumanities libraries epistemology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:82c79ac769f0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:datamining"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:statistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:epistemology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.arl.org/bm~doc/spec-326-web.pdf">
    <title>ARL Report on Digital Humanities</title>
    <dc:date>2012-01-19T17:11:42+00:00</dc:date>
    <link>http://www.arl.org/bm~doc/spec-326-web.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Washington DC--The Association of Research Libraries (ARL) has published Digital Humanities, SPEC Kit 326, which provides a snapshot of research library experiences with digital scholarship centers or services that support the humanities (e.g., history, art, music, film, literature, philosophy, religion, etc.) and the benefits and challenges of hosting them. The survey asked ARL libraries about the organization of these services, how they are staffed and funded, what services they offer and to whom, what technical infrastructure is provided, whether the library manages or archives the digital resources produced, and how services are assessed, among other questions.

This survey revealed that library-based support for the digital humanities is offered predominantly on an ad hoc basis. However, as demand for services supporting the digital humanities has grown, libraries have begun to re-evaluate their provisional service and staffing models. Many respondents expressed a desire to implement practices, policies, and procedures that would allow them to cope with increases in demand for services.

This SPEC Kit includes documentation from respondents that describes the mission or purpose of digital humanities centers, the services offered, policies and procedures, examples of digital projects, fellowship and grant opportunities, promotional materials, and repositories for digital projects.]]></description>
<dc:subject>digitalhumanities research libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0703e1a396aa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digitalhumanities"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://people.ischool.berkeley.edu/~buckland/otlet.html">
    <title>Michael Buckland's Paul Otlet Page</title>
    <dc:date>2012-01-11T15:51:13+00:00</dc:date>
    <link>http://people.ischool.berkeley.edu/~buckland/otlet.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Michael Buckland's notes on Paul Otlet, with links to other Otlet resources.

"Paul Otlet (portrait) was born in Brussels, Belgium, in 1868. His monumental book Traité de documentation. (Brussels, 1934) was both central and symbolic in the development of information science - then called 'Documentation' - in the first half of this century. In addition, it reminds us of something that has been too widely forgotten: That this field did have a lively existence in the early decades of this century and a sophistication concerning theory and information technology that now commonly surprises people."]]></description>
<dc:subject>webhistory otlet cataloging classification history hypertext libraries inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6432e77d34e3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webhistory"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:otlet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:classification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:hypertext"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/2005/Incubator/lld/XGR-lld-20111025/">
    <title>Library Linked Data Incubator Group Final Report</title>
    <dc:date>2011-10-25T15:46:33+00:00</dc:date>
    <link>http://www.w3.org/2005/Incubator/lld/XGR-lld-20111025/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Key recommendations of the report are:

That library leaders identify sets of data as possible candidates for early exposure as Linked Data and foster a discussion about Open Data and rights;
That library standards bodies increase library participation in Semantic Web standardization, develop library data standards that are compatible with Linked Data, and disseminate best-practice design patterns tailored to library Linked Data;
That data and systems designers design enhanced user services based on Linked Data capabilities, create URIs for the items in library datasets, develop policies for managing RDF vocabularies and their URIs, and express library data by re-using or mapping to existing Linked Data vocabularies;
That librarians and archivists preserve Linked Data element sets and value vocabularies and apply library experience in curation and long-term preservation to Linked Data datasets.]]></description>
<dc:subject>libraries linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:9a15ef60beb0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/2005/Incubator/lld/XGR-lld-vocabdataset-20111025/">
    <title>Library Linked Data Incubator Group: Datasets, Value Vocabularies, and Metadata Element Sets</title>
    <dc:date>2011-10-25T15:18:09+00:00</dc:date>
    <link>http://www.w3.org/2005/Incubator/lld/XGR-lld-vocabdataset-20111025/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document, a deliverable from the W3C Library Linked Data Incubator Group, is an attempt to identify a set of useful resources for creating or consuming Linked Data in the library domain. It is intended both for novices seeking an overview of the library Linked Data domain, and for experts in search of a quick look-up or refresher. The final report of the Incubator Group suggests that the success of Linked Data in any domain depends on the ability of its practitioners to identify, re-use, or connect to already available datasets and data models. Library Linked Data is not an exception. Such an identification effort is crucial given the complexity and variety of library data resources, many of them already available as Linked Data at the time of writing this report. We hope that this document will help those who undertake such tasks.]]></description>
<dc:subject>libraries linkeddata vocabulary</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3cb56a3774a8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabulary"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cira.ch/">
    <title>Accueil – CIRA</title>
    <dc:date>2011-09-27T17:12:27+00:00</dc:date>
    <link>http://www.cira.ch/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The cira library collects, preserves and makes available a collection of books, periodicals and documents in all languages concerning the anarchist movement, its history and ideas. It was founded in Geneva in 1957.]]></description>
<dc:subject>anarchism special libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:19fb706648de/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:anarchism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:special"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/2005/Incubator/lld/wiki/DraftReportWithTransclusion">
    <title>DraftReportWithTransclusion - Library Linked Data</title>
    <dc:date>2011-09-20T16:41:23+00:00</dc:date>
    <link>http://www.w3.org/2005/Incubator/lld/wiki/DraftReportWithTransclusion</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Please note that the final report is not officially published yet. This will happen in the second half of September, at a different place on the W3C website, after some final copy editing has been made!]]></description>
<dc:subject>libraries linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1d24516bf55b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.libraryjournal.com/lj/home/891826-264/how_the_w3c_has_come.html.csp">
    <title>How the W3C Has Come To Love Library Linked Data</title>
    <dc:date>2011-09-20T16:38:15+00:00</dc:date>
    <link>http://www.libraryjournal.com/lj/home/891826-264/how_the_w3c_has_come.html.csp</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The number of influential libraries publishing their metadata onto the web as linked open data, which is the heart of the Semantic Web, is growing at a dizzying rate. To further this trend, the World Wide Web Consortium (W3C), a major nonlibrary organization that supports the technologies that undergird the Semantic Web (or the Web of Data), will release a new report in September devoted to library linked data (LLD).]]></description>
<dc:subject>linkeddata libraries</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:7961831f0748/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.opencontentalliance.org/2009/08/04/google-at-their-word/">
    <title>Google at their word</title>
    <dc:date>2009-08-04T23:57:17+00:00</dc:date>
    <link>http://www.opencontentalliance.org/2009/08/04/google-at-their-word/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[As part of Google’s propaganda tour selling their proposed book monopoly, a surprising and seemingly hypocritical theme emerged loud and clear.  Straight from the “have cake and eat it too” department, Google’s senior traveling digital book salesman, Dan Clancy, professed his undying commitment to the legislative process as it relates to orphan works.

At a Computer History Museum event last week in Silicon Valley, Clancy suggested that the best way to address the orphan books issue is for Congress to pass legislation, and that Google is not only supportive of this effort, but pushing for it.

Well, we’d like to take Google at their word and hope that they live up to that commitment.  And we hope that they do it in a way that is honest and forthright, not self-serving and diversionary.  At the Internet Archive, we believe that the right way to gain access to orphan books is to not break the law while you are doing it, and to work through Congress to ensure that the people’s voice in copyright is articulated the way the system was designed to work, not through a private, secret deal that we’re being assured is in our best interests by Google.  For the browsing, lending, and vending of digital books, the Archive is seeking an open and competitive market with appropriate safeguards for readers, not a monopoly bookstore created by the biggest online advertising company in the world.

No one elected Google to write copyright law for America.  And the Author’s Guild and American Association of Publishers simply do not accurately represent the diverse cross-section of those communities.  If Google is really interested in honoring our legislative process, let’s acknowledge that Congress is the path that our government chose to make copyright law and codify its exceptions — instead of crafting secret deals through class action settlements.

To that end, we are calling on Google to petition the court and seek a delay to the October hearing regarding the settlement. Furthermore, we demand that Google publicly demonstrate their leadership and influence in DC to immediately fuel the legislative process on orphan works.  That way, they could be part of a truly “non-exclusive” deal by ensuring that all stakeholders are provided the same set of rules from Day 1.

We await Google’s response.
]]></description>
<dc:subject>News Congress GBS Google_Books legislation libraries orphan_books SDNY</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:565f59776e79/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:News"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Congress"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:GBS"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Google_Books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:legislation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:orphan_books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:SDNY"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://michaelzimmer.org/2009/05/13/stutzman-google-exposes-book-search-patron-records/">
    <title>Stutzman: Google exposes Book Search patron records</title>
    <dc:date>2009-05-14T05:14:30+00:00</dc:date>
    <link>http://michaelzimmer.org/2009/05/13/stutzman-google-exposes-book-search-patron-records/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I’ve written frequently about how the shift from accessing information in offline spaces to online spaces has particular privacy implications. For example, strikingly different privacy norms and expectations emerge when comparing information-seeking activities in libraries vs. bookstores vs. Google Book Search.

Today, Fred Stutzman revealed a particularly troublesome example of how relying on the “My Library” feature of Google Book Search might mean you have even less privacy with regard to your online intellectual endeavors:

I was shocked to find out that saving a book to your library requires that the book be added to your “shared library”, a public listing tied to your Google account.

There is no way to save a book privately in Google Booksearch.  As Google writes in their FAQ, “When you add reviews, ratings, notes, or labels to a book—or when you add a book to your my Library page—that information will be publicly displayed on Google Book Search.”  They go on to write that “No matter where you use these features, the information you submit will be displayed publicly.”

I couldn’t believe it either.  If you want to set up a Google Library, even if it is just for convenience sake, you have to show the world what you’ve been reading.  As far as I can tell, there’s no good technical or legal reason why one can’t save a book privately, or limit their book-sharing to a group of friends.  This decision seems arbitrary and downright scary (or at least terribly ill-advised).

Stutzman points out the incongruence between Google’s policy and the American Library Association’s longstanding code of ethics, bill of rights, and core values, including their commitment to protecting patron privacy:

 I must wonder why Google is not adhering to ALA policy, and the broader cultural norm of protecting library patron privacy.  As Google partners with large institutions and attempts to monetize Booksearch, failing to respect patron privacy seems foolish and potentially dangerous.  A patron researching a sensitive topic, or a topic that reveals information about the patron (for example, books about a health condition) will have their information revealed publicly if they add such a book to their library.

I also suggest a read of the comment thread on Stutzman’s post, where a suggestion has been made (channelling Zuckerberg) that all your favorited books should be public in an ideal world. Stutzman aptly counters such a proposition.

This is a serious design flaw (or a seriously flawed design decision). Google must act quickly to give users control over which books in their library are publicly viewable.



Related posts: (automatically generated)Banned Book Week is Coming…Even in WasillaLocal Library uses RFID to Manage Materials, but Privacy Concerns AboundUpdate on Local Library SSN Practices
]]></description>
<dc:subject>Google_Book_Search Google_Print Intellectual_Privacy Libraries</dc:subject>
<dc:identifier>https://pinboard.in/u:rybesh/b:ccffb4bb48b8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Google_Book_Search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Google_Print"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Intellectual_Privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:Libraries"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>