Code4Lib - User contributions [en]

Rogue

2009-03-03T05:36:25Z

Edward Vielmetti:

== ROGUE 05 ==

Really Obtuse Generalized Underutilized Elaborations (ROGUE) is a standards making body formed on Friday September 23 2005 at 4:35pm. Like other minimalist movements such as DOGME 95 and SCRWU 03 we operate on a handful of basic inviolable principles:

* Specifications must fit on one page
* Specifications are developed on public lists
* The specification process starts with a public draft
* Specifications have a 120-day cycle with drafts due at 30 and 60 days and a ballot spec due at 90 days
* Three separate and verifiable implementations are required for every draft revision to complete the 30, 60, and 90 day steps
* Failing three separate implementations within any 30 day step, specifications are abandoned
* Comments are welcome/encouraged from the public for 30 days after publication of ballot spec at 90 day mark
* Final votes on comments are taken after 30 day comment period from individuals having submitted working implementations
* In case of a tie, implementation submitters from the 30, 60, and 90 day steps who submitted multiple implementations at one step or implementations at multiple steps get an extra vote, which counts as many times as their implementation submissions. In case of a tie, still, the original draft author breaks the tie.
* Specifications must be public documents which do not restrict copying or implementation in any way
* During the specification process, and after any successfully balloted specifications are completed (having passed a vote at the 120 day mark), specifications must remain publicly accessible at a stable location

ROGUE 05 welcomes participation from anyone, anywhere, at no cost. Add your own below:

* [http://web.archive.org/web/20070205082415/curtis.med.yale.edu/dchud/log/project/rogue/rogue-no.1-coins-pmh?showcomments=yes COinS-PMH] - The ContextObjects in Spans Protocol for Metadata Harvesting ([[COinS-PMH]]) is a simplified version of the Open Archives Initiative Protocol for Metadata Harvesting v2.0 ([[OAI-PMH]]) for use with ContextObjects in Spans ([[COinS]]).
* [http://unapi.info/ unAPI] - unAPI is a tiny HTTP API for the few basic operations necessary to copy discrete, identified content from any kind of web application.

[[Category: Standards groups]]

COinS

2009-03-03T05:35:19Z

Edward Vielmetti: Redirecting to COinS (layman's description)

#REDIRECT [[COinS (layman's description)]]

COinS (layman's description)

2009-03-03T05:34:46Z

Edward Vielmetti:

This page is no longer maintained. It was used to create http://journal.code4lib.org/coins
Unconsumed COinS from the Code4Lib Journal link to that page.

Example page:
http://vlib.mpg.de/sfx-coins.html

Wikipedia page on [[COinS]]:
http://en.wikipedia.org/w/index.php?title=COinS

==Services that consume COinS==
*Zotero http://zotero.org
*OpenURL Referrer http://www.openly.com/openurlref/
*[[LibX]] Library Browser plugin http://www.libx.org/
*Check for a library [[OpenURL]] resolver associated with your IP address at [http://worldcatlibraries.org/registry/gateway OCLC OpenURL Gateway] (for more information about this service see [OCLC URL Resolver http://www.oclc.org/productworks/urlresolver.htm]
*refbase http://refbase.sourceforge.net/

==Resources for finding an OpenURL Resolver==
OCLC Registry http://www.oclc.org/productworks/urlresolver.htm

http://dev.zotero.org/making_coins has this language:
" “COinS” stands for “ContextObject in Span.” “[[ContextObject]]” is [[OpenURL]] jargon for the part of an OpenURL carrying the bibliographic information - basically, it’s a query string, everything that would follow the ? in a regular URL. And “span” refers here to the HTML tag <span>. It’s the ContextObject that carries the bibliographic information.

The ContextObject is very flexible, and can carry everything from a simple title and author to more obscure things like a [[Serial Item and Contribution Identifier]] (SICI).

The upshot of which is that if you stick COinS in your web page, [[Zotero]] can pull all that data out again.
"

[[Category: Code4Lib Journal]]

MARC4J

2009-02-26T15:22:26Z

Edward Vielmetti: more internal links to let you go all the way back to the sources

The goal of MARC4J is to provide an easy to use Application Programming Interface (API) for working with [[MARC]] and [[MARCXML]] in Java. MARC stands for MAchine Readable Cataloging and is a widely used exchange format for bibliographic data. MARCXML provides a loss-less conversion between MARC ([[MARC21]] but also other formats like [[UNIMARC]]) and XML.

== More information ==
* [http://marc4j.tigris.org/ MARC4J project home] on Tigris

LibX

2009-02-26T15:04:56Z

Edward Vielmetti: systems support list

LibX is a browser plugin for Firefox and Internet Explorer that provides direct access to your library's resources.
LibX is an open source framework from which editions for specific libraries can be built.
Currently, 563 academic and public libraries have created public LibX editions.

LibX supports [[OpenURL]], [[Google Scholar]], off-campus access via [[EZProxy]] or [[WAM]], [[CiteULike]], [[COinS]] and [[xISBN]].

== More information ==
* [http://libx.org LibX] home page
* [[LibX Preconference]] - notes on LibX 2.0 development

[[Category: Browser plugins]]

LibX

2009-02-26T15:02:54Z

Edward Vielmetti: New page: LibX is a browser plugin for Firefox and Internet Explorer that provides direct access to your library's resources. LibX is an open source framework from which editions for specific libra...

LibX is a browser plugin for Firefox and Internet Explorer that provides direct access to your library's resources.
LibX is an open source framework from which editions for specific libraries can be built.
Currently, 563 academic and public libraries have created public LibX editions.

== More information ==
* [http://libx.org LibX] home page
* [[LibX Preconference]] - notes on LibX 2.0 development

[[Category: Browser plugins]]

Category:OCLC

2009-02-26T13:55:16Z

Edward Vielmetti:

: Founded in 1967, OCLC Online Computer Library Center is a nonprofit, membership, computer library service and research organization dedicated to the public purposes of furthering access to the world's information and reducing the rate of rise of library costs. More than 69,000 libraries in 112 countries and territories around the world use OCLC services to locate, acquire, catalog, lend and preserve library materials.

== More information ==
* [http://www.oclc.org OCLC home page]

OCLC

2009-02-26T13:55:04Z

Edward Vielmetti: Redirecting to Category:OCLC

#REDIRECT [[:Category:OCLC]]

LibX Preconference

2009-02-26T07:29:09Z

Edward Vielmetti:

== The LibX 2.0 Platform ==

[http://libx.org LibX] is a popular browser plugin for Firefox and Internet Explorer that has been adopted and customized by hundreds of libraries. Through its intuitive configuration interface, LibX can be customized by librarians even without programming skills. [[LibX]] can give libraries a presence on web pages to which they would not have access otherwise, allowing them to contextualize those web pages in a manner that is useful to and relevant for their users. As libraries compete with other online resources, extending the library's presence onto those sites becomes crucial. LibX 2.0 will provide a community platform for the development, sharing, and deployment of applications that will facilitate this presence.

== Aims and Overview ==

[[Image:Libx2overview.png|right|500px|The LibX 2.0 Platform]]

This half-day preconference is targeted at developers who wish to use the LibX 2.0 platform to extend the reach of their services, or who wish to provide existing services in new contexts.

First, we'll give an under-the-hood overview of how LibX works internally and how it maintains its configuration information. We'll briefly review how maintainers build and configure editions using the LibX Edition Builder.

Second, we'll present our architecture that allows the creation and publication of [[LibApps]]. LibApps are applications composed by librarians using modules that are created by developers. We'll present the abstractions that explain how such applications are created and published and the necessary API to develop and publish modules and LibApps.

Third, we'll demonstrate a number of LibApps and show in detail how they are developed.

Lastly, we'll provide a collaborative space for participants to brainstorm about LibApps, and to develop and deploy a LibApp of their own.

== Participants ==

We envision a minimum number of 10 participants. To keep the size of the group workable, we would limit the number of participants at 25.
This is a half-day preconference.

== Presenters ==

* Godmar Back (Virginia Tech)
* Annette Bailey (Virginia Tech)
* LibX Team members

MARC4J

2009-02-26T06:55:54Z

Edward Vielmetti: New page: The goal of MARC4J is to provide an easy to use Application Programming Interface (API) for working with MARC and MARCXML in Java. MARC stands for MAchine Readable Cataloging and is a wide...

The goal of MARC4J is to provide an easy to use Application Programming Interface (API) for working with MARC and MARCXML in Java. MARC stands for MAchine Readable Cataloging and is a widely used exchange format for bibliographic data. MARCXML provides a loss-less conversion between MARC (MARC21 but also other formats like UNIMARC) and XML.

== More information ==
* [http://marc4j.tigris.org/ MARC4J project home] on Tigris

Marc4j

2009-02-26T01:13:21Z

Edward Vielmetti: all caps as per the code

#REDIRECT [[MARC4J]]

Notes from Open Source Discovery Portal Camp

2009-02-26T01:13:03Z

Edward Vielmetti: /* solr marc */

== Notes from Open Source Discovery Portal Camp ==

On 6 November 2008, there was a meeting at the Palinet offices in Philadelphia to discuss the future of open source discovery portals. The [[VuFind]] and [[Blacklight]] projects had already started cooperating by sharing indexing code in the form of [[Solrmarc]], and as a community we wanted to explore whether there were other ways we could be cooperating, and what our development priorities should be. We discussed the following topics and some people identified themselves as particularly interested in following up on specific topics and doing further work in a given area. Bess took notes, which are pasted here, but please feel free to expand upon these with your own memories of the conversation.

=== Jangle ===

Andrew started by giving us a brief introduction to [[Jangle]], a standard approach to building a toolset for interacting with the ILS. It was kickstarted by the DLF ILS API set. The idea is to create a standard way of interacting with the ILS. Jangle is the first implementation of this, and is planned as the "reference implementation." It's an open source standard approach, and will give us a lot of flexibility.

Gabe points out that the DLF standard and the Jangle standard aren't the same thing exactly, but people seem to agree it's still a good start at standardization. Andrew asks, how do we contribute the VuFind drivers to Jangle? Is there an [[NCIP]] driver for Jangle? [http://www.extensiblecatalog.org/ Xtensible Catalog] is using NCIP, for example. One problem with this, though, is that many vendors don't implement NCIP.

Ross Singer is the main developer for Jangle, and he wrote an article about it for the latest code4lib journal. Everyone's homework is to go read that article, available [http://journal.code4lib.org/articles/109 here]. Many institutions are hacking their own ILS, it would be more efficient if we all share this code through something like Jangle, which could then be used by VuFind, Blacklight, [http://code.google.com/p/fac-back-opac/ Helios], or any other project that could talk to Jangle.

Eric Morgan: Jangle is a step in the right direction. DLF came up with a list of API features they want, and then Ross came along and said here's a simple RESTful implementation of a lot of that API, based on [[ATOM]] publishing protocol. We need a number of agreed upon shapes of URLs that do things like tell me the status of this book, authority information for a person. To what degree do we want to use something like Jangle in vufind? There aren't a lot of choices right now, and this seems like a good project to explore further.

What about [[XC]]? There's a lot of frustration around this project, because they say they are open source but haven't actually made any of their source available. How do we get them to participate with the larger community? There's a growing community of developers around these issues, and XC should be involved. Eric says someone should have explicitly invited them.

(interested in further development: Bess, Andrew, Gabe)

=== Non-catalog content / digital repositories ===

Could we adapt [[SolrMARC]] to also include [[SolrOAI]]? Yes, Bob, Naomi and Andrew all have ideas about how this could work. Sounds like this is the kernel of our kernel. [[Solr]] already has a lot of functionality to allow for this. Do we want a couple of plugins, one for solr and one for [[OAI]]? Or do we want an app that handles both?

Lots of little data silos aren't going to work, we need everything in a local catalog. But that doesn't mean we should all try to be google. We still need well-defined collection development policies.

What about social data? [[SoPAC]] is neat, and has an independent layer for saving social data.

We also talked about [[Blacklight]] and the ways it brings in various data sources and handles behavior for different kinds of objects, e.g., [http://musicbrainz.org/ MusicBrainz] data for music items.

(interested in further development: Bob, Dennis, Peter, Naomi, Bess)

=== solr marc ===

Q: How well is solr marc handling bad data these days?

Bob: I've been adding to [[marc4j]] more permissive reading and error correction. It's also reporting errors as it finds them, to make it easier to find bad records. Request for writing to log files instead of standard out. How to handle records with bad leaders? Naomi has some marc test data. We need more test driven development.

Naomi is offering code for parsing OCLC numbers and LC numbers, she'll be working with Bob next week to get that into solrmarc.

Chris from Villanova is going to do some graphic design work for solr marc. Yay!

(Interested in further development: Bob, Naomi, Chris, Bess)

=== Authority control ===

Can we get the LC authority control data, index it locally, and take advantage of that in our searching. Actually getting the authority index data is the problem. It's government monitored data, so why can't we get access to it? We can get snapshots, but there's no method for harvesting it. We need some way to get weekly / monthly updates of authority data. EdSu might have set something up, but it isn't an official service.

Eric says go ahead and implement something, and don't worry about the update method right now. Can we get authority data? Does Open Library have any authority data? Bess will look into this.

"Fred Data" <-- subject authorities

Consensus seems to be that we need a proof of concept first, see how well that scales, and then after that start lobbying LC / OCLC / Palinet / other vendors.

(Interested in further development: Ya'aqov, Daniel, Mark, Bess)

=== Dedupping / FRBR ===

We need to look at Trish Williams' work with hierarchical solr records for implementing FRBR. If we start working with this maybe we can advocate for getting this into the solr trunk.

Do we really need FRBR or will "other editions" do the trick? xISBN and xISSN does a pretty good job from OCLC, and can be implemented in just a few lines of code. No one understands FRBR anyway.

One user group that could really use FRBR is musicians, to tie together recordings and scores. The Variations project at Indiana is working with this. OCLC also made public their algorithm for FRBRizing work. Some libraries have a problem stemming from having digitized versions of an item, and then the digital version has a catalog entry, but then in your VuFind system you index both the digital surrogate and the catalog record about the digital surrogate. You probably want to combine these or suppress

Open Library is also very interested in de-duping research.

=== Serials holdings ===

Marc format for holdings data (MFHD)
xISSN service might be helpful for this, too
Bibliographic records for serials should refer to each other.

How to represent this data for users? There's a summary holdings field, a one-line display, and then there's a detailed holding display. There can be multiple screens of lines with this. Summary holdings are pretty easy, detail holdings are hard. Are they necessary?

Maybe we can handle this the way we're doing "composition era" in blacklight? If we know the range, we can assign values for all possible values of this range.

You can get an extract of all serial holdings from your Open URL database (SFX), harvest your journal holdings through that. Texas A&M is doing this w/ SFX. This seems like an efficient way of getting detailed holdings. Indexing this might be helpful if you don't have marc records for all of your electronic holdings, and it also might help for knowing when you have full text online and when you don't.

(interested in further development: Ya'aqov, Mark)

=== Federated Search / article content ===

Can we partner with LibraryFind? Or should we implement an engine like pazpar2?
IndexData has something called pazpar2, which is a federated search engine.

(Interested in further development: one guy, whose name I didn't catch. Please self identify!)

=== back-end arch / OSS methods ===

We never really discussed this, but Peter and Peter said they were interested in following up on this topic.

=== kernelizing the projects ===

- solrmarc
- solroai
- authority data & merging

=== How do we organize - How do we reach out to libraries and formalize a committment? ===
John, Dennis, Joe, Andrew, Mark, Daniel

[[Category: Meeting agendas]]

SolrMARC

2009-02-26T00:55:57Z

Edward Vielmetti: not sure of the canonial punctuation

#REDIRECT [[Solrmarc]]

Notes from Open Source Discovery Portal Camp

2009-02-26T00:54:44Z

Edward Vielmetti: /* Non-catalog content / digital repositories */

== Notes from Open Source Discovery Portal Camp ==

On 6 November 2008, there was a meeting at the Palinet offices in Philadelphia to discuss the future of open source discovery portals. The [[VuFind]] and [[Blacklight]] projects had already started cooperating by sharing indexing code in the form of [[Solrmarc]], and as a community we wanted to explore whether there were other ways we could be cooperating, and what our development priorities should be. We discussed the following topics and some people identified themselves as particularly interested in following up on specific topics and doing further work in a given area. Bess took notes, which are pasted here, but please feel free to expand upon these with your own memories of the conversation.

=== Jangle ===

Andrew started by giving us a brief introduction to [[Jangle]], a standard approach to building a toolset for interacting with the ILS. It was kickstarted by the DLF ILS API set. The idea is to create a standard way of interacting with the ILS. Jangle is the first implementation of this, and is planned as the "reference implementation." It's an open source standard approach, and will give us a lot of flexibility.

Gabe points out that the DLF standard and the Jangle standard aren't the same thing exactly, but people seem to agree it's still a good start at standardization. Andrew asks, how do we contribute the VuFind drivers to Jangle? Is there an [[NCIP]] driver for Jangle? [http://www.extensiblecatalog.org/ Xtensible Catalog] is using NCIP, for example. One problem with this, though, is that many vendors don't implement NCIP.

Ross Singer is the main developer for Jangle, and he wrote an article about it for the latest code4lib journal. Everyone's homework is to go read that article, available [http://journal.code4lib.org/articles/109 here]. Many institutions are hacking their own ILS, it would be more efficient if we all share this code through something like Jangle, which could then be used by VuFind, Blacklight, [http://code.google.com/p/fac-back-opac/ Helios], or any other project that could talk to Jangle.

Eric Morgan: Jangle is a step in the right direction. DLF came up with a list of API features they want, and then Ross came along and said here's a simple RESTful implementation of a lot of that API, based on [[ATOM]] publishing protocol. We need a number of agreed upon shapes of URLs that do things like tell me the status of this book, authority information for a person. To what degree do we want to use something like Jangle in vufind? There aren't a lot of choices right now, and this seems like a good project to explore further.

What about [[XC]]? There's a lot of frustration around this project, because they say they are open source but haven't actually made any of their source available. How do we get them to participate with the larger community? There's a growing community of developers around these issues, and XC should be involved. Eric says someone should have explicitly invited them.

(interested in further development: Bess, Andrew, Gabe)

=== Non-catalog content / digital repositories ===

Could we adapt [[SolrMARC]] to also include [[SolrOAI]]? Yes, Bob, Naomi and Andrew all have ideas about how this could work. Sounds like this is the kernel of our kernel. [[Solr]] already has a lot of functionality to allow for this. Do we want a couple of plugins, one for solr and one for [[OAI]]? Or do we want an app that handles both?

Lots of little data silos aren't going to work, we need everything in a local catalog. But that doesn't mean we should all try to be google. We still need well-defined collection development policies.

What about social data? [[SoPAC]] is neat, and has an independent layer for saving social data.

We also talked about [[Blacklight]] and the ways it brings in various data sources and handles behavior for different kinds of objects, e.g., [http://musicbrainz.org/ MusicBrainz] data for music items.

(interested in further development: Bob, Dennis, Peter, Naomi, Bess)

=== solr marc ===

Q: How well is solr marc handling bad data these days?

Bob: I've been adding to marc4j more permissive reading and error correction. It's also reporting errors as it finds them, to make it easier to find bad records. Request for writing to log files instead of standard out. How to handle records with bad leaders? Naomi has some marc test data. We need more test driven development.

Naomi is offering code for parsing OCLC numbers and LC numbers, she'll be working with Bob next week to get that into solrmarc.

Chris from Villanova is going to do some graphic design work for solr marc. Yay!

(Interested in further development: Bob, Naomi, Chris, Bess)

=== Authority control ===

Can we get the LC authority control data, index it locally, and take advantage of that in our searching. Actually getting the authority index data is the problem. It's government monitored data, so why can't we get access to it? We can get snapshots, but there's no method for harvesting it. We need some way to get weekly / monthly updates of authority data. EdSu might have set something up, but it isn't an official service.

Eric says go ahead and implement something, and don't worry about the update method right now. Can we get authority data? Does Open Library have any authority data? Bess will look into this.

"Fred Data" <-- subject authorities

Consensus seems to be that we need a proof of concept first, see how well that scales, and then after that start lobbying LC / OCLC / Palinet / other vendors.

(Interested in further development: Ya'aqov, Daniel, Mark, Bess)

=== Dedupping / FRBR ===

We need to look at Trish Williams' work with hierarchical solr records for implementing FRBR. If we start working with this maybe we can advocate for getting this into the solr trunk.

Do we really need FRBR or will "other editions" do the trick? xISBN and xISSN does a pretty good job from OCLC, and can be implemented in just a few lines of code. No one understands FRBR anyway.

One user group that could really use FRBR is musicians, to tie together recordings and scores. The Variations project at Indiana is working with this. OCLC also made public their algorithm for FRBRizing work. Some libraries have a problem stemming from having digitized versions of an item, and then the digital version has a catalog entry, but then in your VuFind system you index both the digital surrogate and the catalog record about the digital surrogate. You probably want to combine these or suppress

Open Library is also very interested in de-duping research.

=== Serials holdings ===

Marc format for holdings data (MFHD)
xISSN service might be helpful for this, too
Bibliographic records for serials should refer to each other.

How to represent this data for users? There's a summary holdings field, a one-line display, and then there's a detailed holding display. There can be multiple screens of lines with this. Summary holdings are pretty easy, detail holdings are hard. Are they necessary?

Maybe we can handle this the way we're doing "composition era" in blacklight? If we know the range, we can assign values for all possible values of this range.

You can get an extract of all serial holdings from your Open URL database (SFX), harvest your journal holdings through that. Texas A&M is doing this w/ SFX. This seems like an efficient way of getting detailed holdings. Indexing this might be helpful if you don't have marc records for all of your electronic holdings, and it also might help for knowing when you have full text online and when you don't.

(interested in further development: Ya'aqov, Mark)

=== Federated Search / article content ===

Can we partner with LibraryFind? Or should we implement an engine like pazpar2?
IndexData has something called pazpar2, which is a federated search engine.

(Interested in further development: one guy, whose name I didn't catch. Please self identify!)

=== back-end arch / OSS methods ===

We never really discussed this, but Peter and Peter said they were interested in following up on this topic.

=== kernelizing the projects ===

- solrmarc
- solroai
- authority data & merging

=== How do we organize - How do we reach out to libraries and formalize a committment? ===
John, Dennis, Joe, Andrew, Mark, Daniel

[[Category: Meeting agendas]]

EXtensible Catalog

2009-02-26T00:53:23Z

Edward Vielmetti: New page: (properly the name of this is eXtensible Catalog, or XC for short) == More information == * [http://www.extensiblecatalog.org/ eXtensible Catalog] home page * [http://www.library.nd.edu/d...

(properly the name of this is eXtensible Catalog, or XC for short)

== More information ==
* [http://www.extensiblecatalog.org/ eXtensible Catalog] home page
* [http://www.library.nd.edu/daiad/morgan/musings/future-of-search/ Catalog Collectivism: XC and the Future of Library Search], Eric Lease Morgan, Hesburgh Libraries, University of Notre Dame

XC

2009-02-26T00:51:35Z

Edward Vielmetti: Redirecting to EXtensible Catalog

#REDIRECT [[eXtensible Catalog]]

XC

2009-02-26T00:50:25Z

Edward Vielmetti: Redirecting to Xtensible Catalog

#REDIRECT [[Xtensible Catalog]]

Notes from Open Source Discovery Portal Camp

2009-02-26T00:50:08Z

Edward Vielmetti: /* Jangle */

== Notes from Open Source Discovery Portal Camp ==

On 6 November 2008, there was a meeting at the Palinet offices in Philadelphia to discuss the future of open source discovery portals. The [[VuFind]] and [[Blacklight]] projects had already started cooperating by sharing indexing code in the form of [[Solrmarc]], and as a community we wanted to explore whether there were other ways we could be cooperating, and what our development priorities should be. We discussed the following topics and some people identified themselves as particularly interested in following up on specific topics and doing further work in a given area. Bess took notes, which are pasted here, but please feel free to expand upon these with your own memories of the conversation.

=== Jangle ===

Andrew started by giving us a brief introduction to [[Jangle]], a standard approach to building a toolset for interacting with the ILS. It was kickstarted by the DLF ILS API set. The idea is to create a standard way of interacting with the ILS. Jangle is the first implementation of this, and is planned as the "reference implementation." It's an open source standard approach, and will give us a lot of flexibility.

Gabe points out that the DLF standard and the Jangle standard aren't the same thing exactly, but people seem to agree it's still a good start at standardization. Andrew asks, how do we contribute the VuFind drivers to Jangle? Is there an [[NCIP]] driver for Jangle? [http://www.extensiblecatalog.org/ Xtensible Catalog] is using NCIP, for example. One problem with this, though, is that many vendors don't implement NCIP.

Ross Singer is the main developer for Jangle, and he wrote an article about it for the latest code4lib journal. Everyone's homework is to go read that article, available [http://journal.code4lib.org/articles/109 here]. Many institutions are hacking their own ILS, it would be more efficient if we all share this code through something like Jangle, which could then be used by VuFind, Blacklight, [http://code.google.com/p/fac-back-opac/ Helios], or any other project that could talk to Jangle.

Eric Morgan: Jangle is a step in the right direction. DLF came up with a list of API features they want, and then Ross came along and said here's a simple RESTful implementation of a lot of that API, based on [[ATOM]] publishing protocol. We need a number of agreed upon shapes of URLs that do things like tell me the status of this book, authority information for a person. To what degree do we want to use something like Jangle in vufind? There aren't a lot of choices right now, and this seems like a good project to explore further.

What about [[XC]]? There's a lot of frustration around this project, because they say they are open source but haven't actually made any of their source available. How do we get them to participate with the larger community? There's a growing community of developers around these issues, and XC should be involved. Eric says someone should have explicitly invited them.

(interested in further development: Bess, Andrew, Gabe)

=== Non-catalog content / digital repositories ===

Could we adapt SolrMARC to also include SolrOAI? Yes, Bob, Naomi and Andrew all have ideas about how this could work. Sounds like this is the kernel of our kernel. Solr already has a lot of functionality to allow for this. Do we want a couple of plugins, one for solr and one for OAI? Or do we want an app that handles both?

Lots of little data silos aren't going to work, we need everything in a local catalog. But that doesn't mean we should all try to be google. We still need well-defined collection development policies.

What about social data? SoPAC is neat, and has an independent layer for saving social data.

We also talked about Blacklight and the ways it brings in various data sources and handles behavior for different kinds of objects, e.g., [http://musicbrainz.org/ MusicBrainz] data for music items.

(interested in further development: Bob, Dennis, Peter, Naomi, Bess)

=== solr marc ===

Q: How well is solr marc handling bad data these days?

Bob: I've been adding to marc4j more permissive reading and error correction. It's also reporting errors as it finds them, to make it easier to find bad records. Request for writing to log files instead of standard out. How to handle records with bad leaders? Naomi has some marc test data. We need more test driven development.

Naomi is offering code for parsing OCLC numbers and LC numbers, she'll be working with Bob next week to get that into solrmarc.

Chris from Villanova is going to do some graphic design work for solr marc. Yay!

(Interested in further development: Bob, Naomi, Chris, Bess)

=== Authority control ===

Can we get the LC authority control data, index it locally, and take advantage of that in our searching. Actually getting the authority index data is the problem. It's government monitored data, so why can't we get access to it? We can get snapshots, but there's no method for harvesting it. We need some way to get weekly / monthly updates of authority data. EdSu might have set something up, but it isn't an official service.

Eric says go ahead and implement something, and don't worry about the update method right now. Can we get authority data? Does Open Library have any authority data? Bess will look into this.

"Fred Data" <-- subject authorities

Consensus seems to be that we need a proof of concept first, see how well that scales, and then after that start lobbying LC / OCLC / Palinet / other vendors.

(Interested in further development: Ya'aqov, Daniel, Mark, Bess)

=== Dedupping / FRBR ===

We need to look at Trish Williams' work with hierarchical solr records for implementing FRBR. If we start working with this maybe we can advocate for getting this into the solr trunk.

Do we really need FRBR or will "other editions" do the trick? xISBN and xISSN does a pretty good job from OCLC, and can be implemented in just a few lines of code. No one understands FRBR anyway.

One user group that could really use FRBR is musicians, to tie together recordings and scores. The Variations project at Indiana is working with this. OCLC also made public their algorithm for FRBRizing work. Some libraries have a problem stemming from having digitized versions of an item, and then the digital version has a catalog entry, but then in your VuFind system you index both the digital surrogate and the catalog record about the digital surrogate. You probably want to combine these or suppress

Open Library is also very interested in de-duping research.

=== Serials holdings ===

Marc format for holdings data (MFHD)
xISSN service might be helpful for this, too
Bibliographic records for serials should refer to each other.

How to represent this data for users? There's a summary holdings field, a one-line display, and then there's a detailed holding display. There can be multiple screens of lines with this. Summary holdings are pretty easy, detail holdings are hard. Are they necessary?

Maybe we can handle this the way we're doing "composition era" in blacklight? If we know the range, we can assign values for all possible values of this range.

You can get an extract of all serial holdings from your Open URL database (SFX), harvest your journal holdings through that. Texas A&M is doing this w/ SFX. This seems like an efficient way of getting detailed holdings. Indexing this might be helpful if you don't have marc records for all of your electronic holdings, and it also might help for knowing when you have full text online and when you don't.

(interested in further development: Ya'aqov, Mark)

=== Federated Search / article content ===

Can we partner with LibraryFind? Or should we implement an engine like pazpar2?
IndexData has something called pazpar2, which is a federated search engine.

(Interested in further development: one guy, whose name I didn't catch. Please self identify!)

=== back-end arch / OSS methods ===

We never really discussed this, but Peter and Peter said they were interested in following up on this topic.

=== kernelizing the projects ===

- solrmarc
- solroai
- authority data & merging

=== How do we organize - How do we reach out to libraries and formalize a committment? ===
John, Dennis, Joe, Andrew, Mark, Daniel

[[Category: Meeting agendas]]

Jangle

2009-02-26T00:48:33Z

Edward Vielmetti: more about jangle

The Jangle project intends to expose the data hidden in library systems by using the [[Atom Publishing Protocol]] to provide simple, consistent access to content and resources.

== more information ==
* [http://www.jangle.org/ Jangle] home page
* [http://journal.code4lib.org/articles/109 Unveiling Jangle: Untangling Library Resources and Exposing them through the Atom Publishing Protocol], Code4Lib Journal, Issue 4, 2008-09-22, By Ross Singer and James Farrugia

Logo Design Process

2009-02-26T00:08:45Z

Edward Vielmetti: Undo revision 2358 by 83.142.23.194 (Talk)

__NOTOC__
This page will document the process we are undertaking to create a logo for Code4Lib.

== Working Group ==

* Roy Tennant
* Ranti Junus
* Emily Molanphy

== Process ==

* We (the working group) will draft a logo requirements statement -- what Code4Lib is, who we are, and any kind of "messages" or "themes" we think should be considered in the design process.
* When we're satisfied with the draft, we send it past David Cloutman, who has offered to review it.
* We make any adjustments we want based on David's feedback.
* We send it out the Code4Lib list for group comments.
* We change it, if necessary, based on the feedback.
* We submit it to Stephanie so she can get started, requesting a few draft concepts for review and feedback.
* We request volunteers to help review the drafts who have familiarity with the process of selecting a logo.
* When the draft designs are available, the working group and the volunteers select one design to further develop (if needed)
* We forward to Stephanie collated suggestions for anything we'd like to see in a final version.

== Requirements Document ==

'''Code4Lib Logo Design Briefing and Requirements'''

''About Code4Lib''

Code4Lib is a loose collaboration of library software developers and technologists interested in learning, sharing their experiences, and having fun. There is no "membership", you simply participate. There is no "organization", you simply lead. Anyone who wishes to be involved with an activity (for example, the Code4Lib Journal) simply does it.

There are many ways to participate. Code4Lib offers a web site, a wiki, a chatroom, a mailing list, an RSS aggregation service, a journal, and a conference.

Key themes to consider include software, technology, libraries, librarians, participation, openness, and collaboration. The group is very technically-inclined and savvy about writing, debugging, and deploying software. At the same time, the group has a playful attitude and has fun while doing serious work.

''Logo requirements:''
* The organization name (Code4Lib) must be included in the final logo.
* The logo must be identifiable.
* The logo should be simple and clear in concept.
* It must be distinctive in the quality and originality of its visual image and not offend any sensitivities.
* The concept should have relevance to the organization.
* It must adapt well to electronic and printed media, to reproduction on small surfaces, and to use in color, both in positive and in negative form.
* It must be free of any copyright or other intellectual property claims.

== History ==

On September 19, 2008 Roy Tennant [http://serials.infomotions.com/code4lib/archive/2008/200809/1492.html posted a suggestion] on the Code4Lib mailing list that we create a logo for this group.

There was enough interest expressed that Roy put up an online poll. The result of [http://serials.infomotions.com/code4lib/archive/2008/200809/1544.html that vote] indicated a strong interest in creating a logo, but the preferred process for doing so was not clear.

A run-off vote was then held, and "Professional Option 1" [http://dilettantes.code4lib.org/voting_booth/election/results/6 won the vote], which was "We accept Stephanie Brinley's kind offer, request a few different ideas, vote on those ideas to settle on one, and the final version is created from the winning idea."

A [http://serials.infomotions.com/code4lib/archive/2008/200811/1993.html call for volunteers] to draft a requirements document was then made, and Ranti Junus and Emily Molanphy volunteered.

On January 5, 2009, Stephanie Brinley submitted a set of [http://roytennant.com/c4ldesigns.pdf draft concepts] and Roy Tennant called for volunteers with experience in a logo design process to view and comment on the concepts.

The following Code4Lib participants volunteered to help review the designs and comment: Sean Hannan, Karen Schneider, Rob Styles, Steve Toub, Tito Sierra, and David Cloutman.

On January 8, 2009, Roy Tennant [http://roytennant.com/1-8-09.txt replied to Stephanie] with the summarized response from the reviewers.

On January 12, 2009, Stephanie Brinley replied with a set of [http://roytennant.com/c4l_finalvariations.pdf final variations] in response to our feedback.

On January 16, 2009, the group decided to go with option #1, while checking with Stephanie that the colors were actual Pantone colors.

On January 29, 2009, Roy Tennant created [http://code4lib.org/logo/ a page on the code4lib web site] for all of the files and instructions.

Solrmarc

2009-02-26T00:07:52Z

Edward Vielmetti:

Solrmarc can index your [[MARC]] records into apache [[Solr]]. It also comes with an improved version of [[marc4j]] that improves handling of UTF-8 characters, is more forgiving of malformed marc data, and can recover from data errors gracefully. This indexer is used by [[Blacklight]] and [[VuFind]].

== More information and code ==
* [http://code.google.com/p/solrmarc/ Solrmarc] home page on Google Code
* [http://wiki.apache.org/solr/Solr4Lib Solr4Lib] on Solr Wiki says "libraries integrating Solr have their own unique challenges that the rest of the computer programming world is advised to steer clear of"

Z39.83

2009-02-25T23:47:00Z

Edward Vielmetti: Redirecting to NCIP

#REDIRECT [[NCIP]]

NCIP

2009-02-25T23:46:47Z

Edward Vielmetti: New page: NCIP (the NISO circulation interchange protocol, also known as Z39.83), was intended to help establish communications between disparate systems for use in Direct Consortial Lending (DC...

NCIP (the NISO circulation interchange protocol, also known as [[Z39.83]]), was intended to help establish communications between disparate systems for use in Direct Consortial Lending (DCL), circulation ILL and self service circulation systems.

== More information ==
* [http://litablog.org/2006/10/29/are-there-no-limits-to-what-ncip-can-do/ Are there no limits to what NCIP can do?], LITA Blog, October 2006

[[Category: Standards]]

Notes from Open Source Discovery Portal Camp

2009-02-25T23:43:26Z

Edward Vielmetti: /* Jangle */

== Notes from Open Source Discovery Portal Camp ==

On 6 November 2008, there was a meeting at the Palinet offices in Philadelphia to discuss the future of open source discovery portals. The [[VuFind]] and [[Blacklight]] projects had already started cooperating by sharing indexing code in the form of [[Solrmarc]], and as a community we wanted to explore whether there were other ways we could be cooperating, and what our development priorities should be. We discussed the following topics and some people identified themselves as particularly interested in following up on specific topics and doing further work in a given area. Bess took notes, which are pasted here, but please feel free to expand upon these with your own memories of the conversation.

=== Jangle ===

Andrew started by giving us a brief introduction to [[Jangle]], a standard approach to building a toolset for interacting with the ILS. It was kickstarted by the DLF ILS API set. The idea is to create a standard way of interacting with the ILS. Jangle is the first implementation of this, and is planned as the "reference implementation." It's an open source standard approach, and will give us a lot of flexibility.

Gabe points out that the DLF standard and the Jangle standard aren't the same thing exactly, but people seem to agree it's still a good start at standardization. Andrew asks, how do we contribute the VuFind drivers to Jangle? Is there an [[NCIP]] driver for Jangle? [http://www.extensiblecatalog.org/ Xtensible Catalog] is using NCIP, for example. One problem with this, though, is that many vendors don't implement NCIP.

Ross Singer is the main developer for Jangle, and he wrote an article about it for the latest code4lib journal. Everyone's homework is to go read that article, available [http://journal.code4lib.org/articles/109 here]. Many institutions are hacking their own ILS, it would be more efficient if we all share this code through something like Jangle, which could then be used by VuFind, Blacklight, [http://code.google.com/p/fac-back-opac/ Helios], or any other project that could talk to Jangle.

Eric Morgan: Jangle is a step in the right direction. DLF came up with a list of API features they want, and then Ross came along and said here's a simple RESTful implementation of a lot of that API, based on [[ATOM]] publishing protocol. We need a number of agreed upon shapes of URLs that do things like tell me the status of this book, authority information for a person. To what degree do we want to use something like Jangle in vufind? There aren't a lot of choices right now, and this seems like a good project to explore further.

What about XC? There's a lot of frustration around this project, because they say they are open source but haven't actually made any of their source available. How do we get them to participate with the larger community? There's a growing community of developers around these issues, and XC should be involved. Eric says someone should have explicitly invited them.

(interested in further development: Bess, Andrew, Gabe)

=== Non-catalog content / digital repositories ===

Could we adapt SolrMARC to also include SolrOAI? Yes, Bob, Naomi and Andrew all have ideas about how this could work. Sounds like this is the kernel of our kernel. Solr already has a lot of functionality to allow for this. Do we want a couple of plugins, one for solr and one for OAI? Or do we want an app that handles both?

Lots of little data silos aren't going to work, we need everything in a local catalog. But that doesn't mean we should all try to be google. We still need well-defined collection development policies.

What about social data? SoPAC is neat, and has an independent layer for saving social data.

We also talked about Blacklight and the ways it brings in various data sources and handles behavior for different kinds of objects, e.g., [http://musicbrainz.org/ MusicBrainz] data for music items.

(interested in further development: Bob, Dennis, Peter, Naomi, Bess)

=== solr marc ===

Q: How well is solr marc handling bad data these days?

Bob: I've been adding to marc4j more permissive reading and error correction. It's also reporting errors as it finds them, to make it easier to find bad records. Request for writing to log files instead of standard out. How to handle records with bad leaders? Naomi has some marc test data. We need more test driven development.

Naomi is offering code for parsing OCLC numbers and LC numbers, she'll be working with Bob next week to get that into solrmarc.

Chris from Villanova is going to do some graphic design work for solr marc. Yay!

(Interested in further development: Bob, Naomi, Chris, Bess)

=== Authority control ===

Can we get the LC authority control data, index it locally, and take advantage of that in our searching. Actually getting the authority index data is the problem. It's government monitored data, so why can't we get access to it? We can get snapshots, but there's no method for harvesting it. We need some way to get weekly / monthly updates of authority data. EdSu might have set something up, but it isn't an official service.

Eric says go ahead and implement something, and don't worry about the update method right now. Can we get authority data? Does Open Library have any authority data? Bess will look into this.

"Fred Data" <-- subject authorities

Consensus seems to be that we need a proof of concept first, see how well that scales, and then after that start lobbying LC / OCLC / Palinet / other vendors.

(Interested in further development: Ya'aqov, Daniel, Mark, Bess)

=== Dedupping / FRBR ===

We need to look at Trish Williams' work with hierarchical solr records for implementing FRBR. If we start working with this maybe we can advocate for getting this into the solr trunk.

Do we really need FRBR or will "other editions" do the trick? xISBN and xISSN does a pretty good job from OCLC, and can be implemented in just a few lines of code. No one understands FRBR anyway.

One user group that could really use FRBR is musicians, to tie together recordings and scores. The Variations project at Indiana is working with this. OCLC also made public their algorithm for FRBRizing work. Some libraries have a problem stemming from having digitized versions of an item, and then the digital version has a catalog entry, but then in your VuFind system you index both the digital surrogate and the catalog record about the digital surrogate. You probably want to combine these or suppress

Open Library is also very interested in de-duping research.

=== Serials holdings ===

Marc format for holdings data (MFHD)
xISSN service might be helpful for this, too
Bibliographic records for serials should refer to each other.

How to represent this data for users? There's a summary holdings field, a one-line display, and then there's a detailed holding display. There can be multiple screens of lines with this. Summary holdings are pretty easy, detail holdings are hard. Are they necessary?

Maybe we can handle this the way we're doing "composition era" in blacklight? If we know the range, we can assign values for all possible values of this range.

You can get an extract of all serial holdings from your Open URL database (SFX), harvest your journal holdings through that. Texas A&M is doing this w/ SFX. This seems like an efficient way of getting detailed holdings. Indexing this might be helpful if you don't have marc records for all of your electronic holdings, and it also might help for knowing when you have full text online and when you don't.

(interested in further development: Ya'aqov, Mark)

=== Federated Search / article content ===

Can we partner with LibraryFind? Or should we implement an engine like pazpar2?
IndexData has something called pazpar2, which is a federated search engine.

(Interested in further development: one guy, whose name I didn't catch. Please self identify!)

=== back-end arch / OSS methods ===

We never really discussed this, but Peter and Peter said they were interested in following up on this topic.

=== kernelizing the projects ===

- solrmarc
- solroai
- authority data & merging

=== How do we organize - How do we reach out to libraries and formalize a committment? ===
John, Dennis, Joe, Andrew, Mark, Daniel

[[Category: Meeting agendas]]

Jangle

2009-02-25T23:34:19Z

Edward Vielmetti: New page: == more information == * [http://www.jangle.org/ Jangle] home page

== more information ==
* [http://www.jangle.org/ Jangle] home page

Notes from Open Source Discovery Portal Camp

2009-02-25T23:33:56Z

Edward Vielmetti: /* Jangle */ [http://www.jangle.org/ Jangle]

== Notes from Open Source Discovery Portal Camp ==

On 6 November 2008, there was a meeting at the Palinet offices in Philadelphia to discuss the future of open source discovery portals. The [[VuFind]] and [[Blacklight]] projects had already started cooperating by sharing indexing code in the form of [[Solrmarc]], and as a community we wanted to explore whether there were other ways we could be cooperating, and what our development priorities should be. We discussed the following topics and some people identified themselves as particularly interested in following up on specific topics and doing further work in a given area. Bess took notes, which are pasted here, but please feel free to expand upon these with your own memories of the conversation.

=== Jangle ===

Andrew started by giving us a brief introduction to [[Jangle]], a standard approach to building a toolset for interacting with the ILS. It was kickstarted by the DLF ILS API set. The idea is to create a standard way of interacting with the ILS. Jangle is the first implementation of this, and is planned as the "reference implementation." It's an open source standard approach, and will give us a lot of flexibility.

Gabe points out that the DLF standard and the Jangle standard aren't the same thing exactly, but people seem to agree it's still a good start at standardization. Andrew asks, how do we contribute the VuFind drivers to Jangle? Is there an NCIP driver for Jangle? [http://www.extensiblecatalog.org/ Xtensible Catalog] is using NCIP, for example. One problem with this, though, is that many vendors don't implement NCIP.

Ross Singer is the main developer for Jangle, and he wrote an article about it for the latest code4lib journal. Everyone's homework is to go read that article, available [http://journal.code4lib.org/articles/109 here]. Many institutions are hacking their own ILS, it would be more efficient if we all share this code through something like Jangle, which could then be used by VuFind, Blacklight, [http://code.google.com/p/fac-back-opac/ Helios], or any other project that could talk to Jangle.

Eric Morgan: Jangle is a step in the right direction. DLF came up with a list of API features they want, and then Ross came along and said here's a simple RESTful implementation of a lot of that API, based on ATOM publishing protocol. We need a number of agreed upon shapes of URLs that do things like tell me the status of this book, authority information for a person. To what degree do we want to use something like Jangle in vufind? There aren't a lot of choices right now, and this seems like a good project to explore further.

What about XC? There's a lot of frustration around this project, because they say they are open source but haven't actually made any of their source available. How do we get them to participate with the larger community? There's a growing community of developers around these issues, and XC should be involved. Eric says someone should have explicitly invited them.

(interested in further development: Bess, Andrew, Gabe)

=== Non-catalog content / digital repositories ===

Could we adapt SolrMARC to also include SolrOAI? Yes, Bob, Naomi and Andrew all have ideas about how this could work. Sounds like this is the kernel of our kernel. Solr already has a lot of functionality to allow for this. Do we want a couple of plugins, one for solr and one for OAI? Or do we want an app that handles both?

Lots of little data silos aren't going to work, we need everything in a local catalog. But that doesn't mean we should all try to be google. We still need well-defined collection development policies.

What about social data? SoPAC is neat, and has an independent layer for saving social data.

We also talked about Blacklight and the ways it brings in various data sources and handles behavior for different kinds of objects, e.g., [http://musicbrainz.org/ MusicBrainz] data for music items.

(interested in further development: Bob, Dennis, Peter, Naomi, Bess)

=== solr marc ===

Q: How well is solr marc handling bad data these days?

Bob: I've been adding to marc4j more permissive reading and error correction. It's also reporting errors as it finds them, to make it easier to find bad records. Request for writing to log files instead of standard out. How to handle records with bad leaders? Naomi has some marc test data. We need more test driven development.

Naomi is offering code for parsing OCLC numbers and LC numbers, she'll be working with Bob next week to get that into solrmarc.

Chris from Villanova is going to do some graphic design work for solr marc. Yay!

(Interested in further development: Bob, Naomi, Chris, Bess)

=== Authority control ===

Can we get the LC authority control data, index it locally, and take advantage of that in our searching. Actually getting the authority index data is the problem. It's government monitored data, so why can't we get access to it? We can get snapshots, but there's no method for harvesting it. We need some way to get weekly / monthly updates of authority data. EdSu might have set something up, but it isn't an official service.

Eric says go ahead and implement something, and don't worry about the update method right now. Can we get authority data? Does Open Library have any authority data? Bess will look into this.

"Fred Data" <-- subject authorities

Consensus seems to be that we need a proof of concept first, see how well that scales, and then after that start lobbying LC / OCLC / Palinet / other vendors.

(Interested in further development: Ya'aqov, Daniel, Mark, Bess)

=== Dedupping / FRBR ===

We need to look at Trish Williams' work with hierarchical solr records for implementing FRBR. If we start working with this maybe we can advocate for getting this into the solr trunk.

Do we really need FRBR or will "other editions" do the trick? xISBN and xISSN does a pretty good job from OCLC, and can be implemented in just a few lines of code. No one understands FRBR anyway.

One user group that could really use FRBR is musicians, to tie together recordings and scores. The Variations project at Indiana is working with this. OCLC also made public their algorithm for FRBRizing work. Some libraries have a problem stemming from having digitized versions of an item, and then the digital version has a catalog entry, but then in your VuFind system you index both the digital surrogate and the catalog record about the digital surrogate. You probably want to combine these or suppress

Open Library is also very interested in de-duping research.

=== Serials holdings ===

Marc format for holdings data (MFHD)
xISSN service might be helpful for this, too
Bibliographic records for serials should refer to each other.

How to represent this data for users? There's a summary holdings field, a one-line display, and then there's a detailed holding display. There can be multiple screens of lines with this. Summary holdings are pretty easy, detail holdings are hard. Are they necessary?

Maybe we can handle this the way we're doing "composition era" in blacklight? If we know the range, we can assign values for all possible values of this range.

You can get an extract of all serial holdings from your Open URL database (SFX), harvest your journal holdings through that. Texas A&M is doing this w/ SFX. This seems like an efficient way of getting detailed holdings. Indexing this might be helpful if you don't have marc records for all of your electronic holdings, and it also might help for knowing when you have full text online and when you don't.

(interested in further development: Ya'aqov, Mark)

=== Federated Search / article content ===

Can we partner with LibraryFind? Or should we implement an engine like pazpar2?
IndexData has something called pazpar2, which is a federated search engine.

(Interested in further development: one guy, whose name I didn't catch. Please self identify!)

=== back-end arch / OSS methods ===

We never really discussed this, but Peter and Peter said they were interested in following up on this topic.

=== kernelizing the projects ===

- solrmarc
- solroai
- authority data & merging

=== How do we organize - How do we reach out to libraries and formalize a committment? ===
John, Dennis, Joe, Andrew, Mark, Daniel

[[Category: Meeting agendas]]

Discovery

2009-02-25T23:33:17Z

Edward Vielmetti:

== Open Source Discovery ==

The Open Source Discovery is an interest group focused on Open Source software applications to enhance "discovery" for library resources.

This group was initially formed from the [http://opensourcediscovery.pbwiki.com/ConferenceNovember2008|Open Source Discovery Portal Camp] conference held in Philadelphia on November 6, 2008. You can read the [[Notes_from_Open_Source_Discovery_Portal_Camp|notes]] from the conference

== Sub Groups ==

* Integrating and Contributing to [[Jangle]]
* Importing Non-catalog content
* Integrating and Contributing to [[SolrMARC]]
* Implementing Authority Control
** Daniel Lovins
* Dedupping / [[FRBR]]
* Better Serials Holdings
* Implementing and Managing Federated Search and Article Content
* Documenting Back-End Architectures
* Planning an approach to kernelizing the projects
* Interest Group Organization and Planning
** Daniel Lovins

CQL

2009-02-25T21:51:11Z

Edward Vielmetti: New page: CQL is a query language used by SRU. == About CQL == as described in the [http://www.loc.gov/standards/sru/specs/cql.html CQL specification]: : CQL, the Contextual Query Language, ...

CQL is a query language used by [[SRU]].

== About CQL ==

as described in the [http://www.loc.gov/standards/sru/specs/cql.html CQL specification]:

: CQL, the Contextual Query Language, is a formal language for representing queries to information retrieval systems such as web indexes, bibliographic catalogs and museum collection information. The design objective is that queries be human readable and writable, and that the language be intuitive while maintaining the expressiveness of more complex languages.

: Traditionally, query languages have fallen into two camps: Powerful, expressive languages, not easily readable nor writable by non-experts (e.g. [[SQL]], [[PQF]], and [[XQuery]]);or simple and intuitive languages not powerful enough to express complex concepts (e.g. [[CCL]] and google). CQL tries to combine simplicity and intuitiveness of expression for simple, every day queries, with the richness of more expressive languages to accomodate complex concepts when necessary.

[[Category: Query languages]]

Notes from Open Source Discovery Portal Camp

2009-02-25T21:09:40Z

Edward Vielmetti: /* Notes from Open Source Discovery Portal Camp */

== Notes from Open Source Discovery Portal Camp ==

On 6 November 2008, there was a meeting at the Palinet offices in Philadelphia to discuss the future of open source discovery portals. The [[VuFind]] and [[Blacklight]] projects had already started cooperating by sharing indexing code in the form of [[Solrmarc]], and as a community we wanted to explore whether there were other ways we could be cooperating, and what our development priorities should be. We discussed the following topics and some people identified themselves as particularly interested in following up on specific topics and doing further work in a given area. Bess took notes, which are pasted here, but please feel free to expand upon these with your own memories of the conversation.

=== Jangle ===

Andrew started by giving us a brief introduction to [http://www.jangle.org/ Jangle], a standard approach to building a toolset for interacting with the ILS. It was kickstarted by the DLF ILS API set. The idea is to create a standard way of interacting with the ILS. Jangle is the first implementation of this, and is planned as the "reference implementation." It's an open source standard approach, and will give us a lot of flexibility.

Gabe points out that the DLF standard and the Jangle standard aren't the same thing exactly, but people seem to agree it's still a good start at standardization. Andrew asks, how do we contribute the VuFind drivers to Jangle? Is there an NCIP driver for Jangle? [http://www.extensiblecatalog.org/ Xtensible Catalog] is using NCIP, for example. One problem with this, though, is that many vendors don't implement NCIP.

Ross Singer is the main developer for Jangle, and he wrote an article about it for the latest code4lib journal. Everyone's homework is to go read that article, available [http://journal.code4lib.org/articles/109 here]. Many institutions are hacking their own ILS, it would be more efficient if we all share this code through something like Jangle, which could then be used by VuFind, Blacklight, [http://code.google.com/p/fac-back-opac/ Helios], or any other project that could talk to Jangle.

Eric Morgan: Jangle is a step in the right direction. DLF came up with a list of API features they want, and then Ross came along and said here's a simple RESTful implementation of a lot of that API, based on ATOM publishing protocol. We need a number of agreed upon shapes of URLs that do things like tell me the status of this book, authority information for a person. To what degree do we want to use something like Jangle in vufind? There aren't a lot of choices right now, and this seems like a good project to explore further.

What about XC? There's a lot of frustration around this project, because they say they are open source but haven't actually made any of their source available. How do we get them to participate with the larger community? There's a growing community of developers around these issues, and XC should be involved. Eric says someone should have explicitly invited them.

(interested in further development: Bess, Andrew, Gabe)

=== Non-catalog content / digital repositories ===

Could we adapt SolrMARC to also include SolrOAI? Yes, Bob, Naomi and Andrew all have ideas about how this could work. Sounds like this is the kernel of our kernel. Solr already has a lot of functionality to allow for this. Do we want a couple of plugins, one for solr and one for OAI? Or do we want an app that handles both?

Lots of little data silos aren't going to work, we need everything in a local catalog. But that doesn't mean we should all try to be google. We still need well-defined collection development policies.

What about social data? SoPAC is neat, and has an independent layer for saving social data.

We also talked about Blacklight and the ways it brings in various data sources and handles behavior for different kinds of objects, e.g., [http://musicbrainz.org/ MusicBrainz] data for music items.

(interested in further development: Bob, Dennis, Peter, Naomi, Bess)

=== solr marc ===

Q: How well is solr marc handling bad data these days?

Bob: I've been adding to marc4j more permissive reading and error correction. It's also reporting errors as it finds them, to make it easier to find bad records. Request for writing to log files instead of standard out. How to handle records with bad leaders? Naomi has some marc test data. We need more test driven development.

Naomi is offering code for parsing OCLC numbers and LC numbers, she'll be working with Bob next week to get that into solrmarc.

Chris from Villanova is going to do some graphic design work for solr marc. Yay!

(Interested in further development: Bob, Naomi, Chris, Bess)

=== Authority control ===

Can we get the LC authority control data, index it locally, and take advantage of that in our searching. Actually getting the authority index data is the problem. It's government monitored data, so why can't we get access to it? We can get snapshots, but there's no method for harvesting it. We need some way to get weekly / monthly updates of authority data. EdSu might have set something up, but it isn't an official service.

Eric says go ahead and implement something, and don't worry about the update method right now. Can we get authority data? Does Open Library have any authority data? Bess will look into this.

"Fred Data" <-- subject authorities

Consensus seems to be that we need a proof of concept first, see how well that scales, and then after that start lobbying LC / OCLC / Palinet / other vendors.

(Interested in further development: Ya'aqov, Daniel, Mark, Bess)

=== Dedupping / FRBR ===

We need to look at Trish Williams' work with hierarchical solr records for implementing FRBR. If we start working with this maybe we can advocate for getting this into the solr trunk.

Do we really need FRBR or will "other editions" do the trick? xISBN and xISSN does a pretty good job from OCLC, and can be implemented in just a few lines of code. No one understands FRBR anyway.

One user group that could really use FRBR is musicians, to tie together recordings and scores. The Variations project at Indiana is working with this. OCLC also made public their algorithm for FRBRizing work. Some libraries have a problem stemming from having digitized versions of an item, and then the digital version has a catalog entry, but then in your VuFind system you index both the digital surrogate and the catalog record about the digital surrogate. You probably want to combine these or suppress

Open Library is also very interested in de-duping research.

=== Serials holdings ===

Marc format for holdings data (MFHD)
xISSN service might be helpful for this, too
Bibliographic records for serials should refer to each other.

How to represent this data for users? There's a summary holdings field, a one-line display, and then there's a detailed holding display. There can be multiple screens of lines with this. Summary holdings are pretty easy, detail holdings are hard. Are they necessary?

Maybe we can handle this the way we're doing "composition era" in blacklight? If we know the range, we can assign values for all possible values of this range.

You can get an extract of all serial holdings from your Open URL database (SFX), harvest your journal holdings through that. Texas A&M is doing this w/ SFX. This seems like an efficient way of getting detailed holdings. Indexing this might be helpful if you don't have marc records for all of your electronic holdings, and it also might help for knowing when you have full text online and when you don't.

(interested in further development: Ya'aqov, Mark)

=== Federated Search / article content ===

Can we partner with LibraryFind? Or should we implement an engine like pazpar2?
IndexData has something called pazpar2, which is a federated search engine.

(Interested in further development: one guy, whose name I didn't catch. Please self identify!)

=== back-end arch / OSS methods ===

We never really discussed this, but Peter and Peter said they were interested in following up on this topic.

=== kernelizing the projects ===

- solrmarc
- solroai
- authority data & merging

=== How do we organize - How do we reach out to libraries and formalize a committment? ===
John, Dennis, Joe, Andrew, Mark, Daniel

[[Category: Meeting agendas]]

Blacklight

2009-02-25T21:07:47Z

Edward Vielmetti: /* More information */

Blacklight is an open source [[OPAC]] (online public access catalog). That means libraries (or anyone else) can use it to allow people to search and browse their collections online. Blacklight uses [[Solr]] to index and search, and it has a highly configurable [[Ruby on Rails]] front-end. Currently, Blacklight can index, search, and provide faceted browsing for [[MARC]] records and several kinds of XML documents, including [[TEI]], [[EAD]], and [[GDMS]]. Blacklight was developed at the University of Virginia Library and is made public under an Apache 2.0 license.

== More information ==
* [http://blacklight.rubyforge.org/ Blacklight] home page
* [[Solrmarc]] is the MARC indexer

[[Category: OPAC]]

Solrmarc

2009-02-25T21:07:05Z

Edward Vielmetti: New page: Solrmarc can index your MARC records into apache Solr. It also comes with an improved version of marc4j that improves handling of UTF-8 characters, is more forgiving of malform...

Solr

2009-02-25T21:05:36Z

Edward Vielmetti:

Solr is an open source enterprise search server based on the [[Lucene]] Java search library, with XML/HTTP and JSON APIs, hit highlighting, faceted search, caching, replication, a web administration interface and many more features. It runs in a Java servlet container such as [[Tomcat]].

== Projects and code ==
* [[Solrmarc]] - indexing [[MARC]] records with Solr

== More information ==
* [http://lucene.apache.org/solr/ Solr] home page

[[Category: Search engines]]

VuFind

2009-02-25T20:38:51Z

Edward Vielmetti:

: VuFind is a library resource portal designed and developed for libraries by libraries. The goal of VuFind is to enable your users to search and browse through all of your library's resources by replacing the traditional [[OPAC]].

== More information ==
* [http://vufind.org/ VuFind] home page
* [http://www.librarytechnology.org/ltg-displayarticle.pl?RC=12664 Villanova University releases VUFIND, an open source next generation library catalog], July 2007

VUFind

2009-02-25T20:37:57Z

Edward Vielmetti: caps

#REDIRECT [[VuFind]]

Solr

2009-02-25T20:37:22Z

Edward Vielmetti: New page: Solr is an open source enterprise search server based on the Lucene Java search library, with XML/HTTP and JSON APIs, hit highlighting, faceted search, caching, replication, a web admi...

Solr is an open source enterprise search server based on the [[Lucene]] Java search library, with XML/HTTP and JSON APIs, hit highlighting, faceted search, caching, replication, a web administration interface and many more features. It runs in a Java servlet container such as [[Tomcat]].

== More information ==
* [http://lucene.apache.org/solr/ Solr] home page

[[Category: Search engines]]

Blacklight

2009-02-25T20:36:09Z

Edward Vielmetti: about us + hyperlink acronyms

Notes from Open Source Discovery Portal Camp

2009-02-25T20:34:12Z

Edward Vielmetti: [http://blacklight.rubyforge.org/ Blacklight

== Notes from Open Source Discovery Portal Camp ==

On 6 November 2008, there was a meeting at the Palinet offices in Philadelphia to discuss the future of open source discovery portals. The [[VuFind]] and [[Blacklight]] projects had already started cooperating by sharing indexing code in the form of [http://code.google.com/p/solrmarc/ SolrMarc], and as a community we wanted to explore whether there were other ways we could be cooperating, and what our development priorities should be. We discussed the following topics and some people identified themselves as particularly interested in following up on specific topics and doing further work in a given area. Bess took notes, which are pasted here, but please feel free to expand upon these with your own memories of the conversation.

=== Jangle ===

Andrew started by giving us a brief introduction to [http://www.jangle.org/ Jangle], a standard approach to building a toolset for interacting with the ILS. It was kickstarted by the DLF ILS API set. The idea is to create a standard way of interacting with the ILS. Jangle is the first implementation of this, and is planned as the "reference implementation." It's an open source standard approach, and will give us a lot of flexibility.

Gabe points out that the DLF standard and the Jangle standard aren't the same thing exactly, but people seem to agree it's still a good start at standardization. Andrew asks, how do we contribute the VuFind drivers to Jangle? Is there an NCIP driver for Jangle? [http://www.extensiblecatalog.org/ Xtensible Catalog] is using NCIP, for example. One problem with this, though, is that many vendors don't implement NCIP.

Ross Singer is the main developer for Jangle, and he wrote an article about it for the latest code4lib journal. Everyone's homework is to go read that article, available [http://journal.code4lib.org/articles/109 here]. Many institutions are hacking their own ILS, it would be more efficient if we all share this code through something like Jangle, which could then be used by VuFind, Blacklight, [http://code.google.com/p/fac-back-opac/ Helios], or any other project that could talk to Jangle.

Eric Morgan: Jangle is a step in the right direction. DLF came up with a list of API features they want, and then Ross came along and said here's a simple RESTful implementation of a lot of that API, based on ATOM publishing protocol. We need a number of agreed upon shapes of URLs that do things like tell me the status of this book, authority information for a person. To what degree do we want to use something like Jangle in vufind? There aren't a lot of choices right now, and this seems like a good project to explore further.

What about XC? There's a lot of frustration around this project, because they say they are open source but haven't actually made any of their source available. How do we get them to participate with the larger community? There's a growing community of developers around these issues, and XC should be involved. Eric says someone should have explicitly invited them.

(interested in further development: Bess, Andrew, Gabe)

=== Non-catalog content / digital repositories ===

Could we adapt SolrMARC to also include SolrOAI? Yes, Bob, Naomi and Andrew all have ideas about how this could work. Sounds like this is the kernel of our kernel. Solr already has a lot of functionality to allow for this. Do we want a couple of plugins, one for solr and one for OAI? Or do we want an app that handles both?

Lots of little data silos aren't going to work, we need everything in a local catalog. But that doesn't mean we should all try to be google. We still need well-defined collection development policies.

What about social data? SoPAC is neat, and has an independent layer for saving social data.

We also talked about Blacklight and the ways it brings in various data sources and handles behavior for different kinds of objects, e.g., [http://musicbrainz.org/ MusicBrainz] data for music items.

(interested in further development: Bob, Dennis, Peter, Naomi, Bess)

=== solr marc ===

Q: How well is solr marc handling bad data these days?

Bob: I've been adding to marc4j more permissive reading and error correction. It's also reporting errors as it finds them, to make it easier to find bad records. Request for writing to log files instead of standard out. How to handle records with bad leaders? Naomi has some marc test data. We need more test driven development.

Naomi is offering code for parsing OCLC numbers and LC numbers, she'll be working with Bob next week to get that into solrmarc.

Chris from Villanova is going to do some graphic design work for solr marc. Yay!

(Interested in further development: Bob, Naomi, Chris, Bess)

=== Authority control ===

Can we get the LC authority control data, index it locally, and take advantage of that in our searching. Actually getting the authority index data is the problem. It's government monitored data, so why can't we get access to it? We can get snapshots, but there's no method for harvesting it. We need some way to get weekly / monthly updates of authority data. EdSu might have set something up, but it isn't an official service.

Eric says go ahead and implement something, and don't worry about the update method right now. Can we get authority data? Does Open Library have any authority data? Bess will look into this.

"Fred Data" <-- subject authorities

Consensus seems to be that we need a proof of concept first, see how well that scales, and then after that start lobbying LC / OCLC / Palinet / other vendors.

(Interested in further development: Ya'aqov, Daniel, Mark, Bess)

=== Dedupping / FRBR ===

We need to look at Trish Williams' work with hierarchical solr records for implementing FRBR. If we start working with this maybe we can advocate for getting this into the solr trunk.

Do we really need FRBR or will "other editions" do the trick? xISBN and xISSN does a pretty good job from OCLC, and can be implemented in just a few lines of code. No one understands FRBR anyway.

One user group that could really use FRBR is musicians, to tie together recordings and scores. The Variations project at Indiana is working with this. OCLC also made public their algorithm for FRBRizing work. Some libraries have a problem stemming from having digitized versions of an item, and then the digital version has a catalog entry, but then in your VuFind system you index both the digital surrogate and the catalog record about the digital surrogate. You probably want to combine these or suppress

Open Library is also very interested in de-duping research.

=== Serials holdings ===

Marc format for holdings data (MFHD)
xISSN service might be helpful for this, too
Bibliographic records for serials should refer to each other.

How to represent this data for users? There's a summary holdings field, a one-line display, and then there's a detailed holding display. There can be multiple screens of lines with this. Summary holdings are pretty easy, detail holdings are hard. Are they necessary?

Maybe we can handle this the way we're doing "composition era" in blacklight? If we know the range, we can assign values for all possible values of this range.

You can get an extract of all serial holdings from your Open URL database (SFX), harvest your journal holdings through that. Texas A&M is doing this w/ SFX. This seems like an efficient way of getting detailed holdings. Indexing this might be helpful if you don't have marc records for all of your electronic holdings, and it also might help for knowing when you have full text online and when you don't.

(interested in further development: Ya'aqov, Mark)

=== Federated Search / article content ===

Can we partner with LibraryFind? Or should we implement an engine like pazpar2?
IndexData has something called pazpar2, which is a federated search engine.

(Interested in further development: one guy, whose name I didn't catch. Please self identify!)

=== back-end arch / OSS methods ===

We never really discussed this, but Peter and Peter said they were interested in following up on this topic.

=== kernelizing the projects ===

- solrmarc
- solroai
- authority data & merging

=== How do we organize - How do we reach out to libraries and formalize a committment? ===
John, Dennis, Joe, Andrew, Mark, Daniel

[[Category: Meeting agendas]]

OCLC Policy Change

2009-02-25T19:09:26Z

Edward Vielmetti:

== Background ==
On 5-Nov-2008, [[OCLC]] announced the Policy for Use and Transfer of [[WorldCat]]® Records to replace the Guidelines for the Use and Transfer of OCLC-Derived Records. The goals of the policy, as described by OCLC, were "to modernize record use and transfer practices for application on the Web, foster new uses of WorldCat data that benefit members and clarify data sharing rights and restrictions." This new policy generated considerable discussion in the library community, including two petitions, several trade publication articles, and over 80 blog posts with related comments.

On 13-Jan-2009, OCLC announced a Review Board of Shared Data Creation and Stewardship with a charge to: consult with librarians and member representatives as appropriate; review reports, letters and comments including blog and listserv messages from the global library community regarding the revised Policy; and recommend principles of shared data creation and changes in the Policy for Use and Transfer of WorldCat Records that will preserve the community around WorldCat infrastructure and services, and strengthen libraries. The review board is to present a preliminary report at the February meeting of the OCLC Members Council and a final draft of the report at the May Members Council meeting. The final report is to be submitted to the OCLC Board of Trustees following the May meeting. The implementation of a new policy is not set to occur prior to the third quarter of 2009.

This page documents the discussion of members of the library community surrounding the revision of the Guidelines and creation of the Policy. It can be edited by anyone who has registered for an account on the Code4Lib wiki. [[Special:Userlogin|Registration]] on the Code4Lib wiki is open to anyone with an e-mail address.

== The Policy ==

* [http://www.oclc.org/us/en/news/releases/20092.htm Press release regarding the Review Board of Shared Data Creation and Stewardship]

* [http://www.oclc.org/worldcat/catalog/policy/policy.htm Policy for Use and Transfer of WorldCat® Records] (Last known update is 19-Nov-2008; this version is in PDF)
* [http://www.oclc.org/worldcat/catalog/policy/ OCLC's summary statement about the policy]
* [http://www.oclc.org/support/documentation/worldcat/records/guidelines/default.htm Guidelines for the Use and Transfer of OCLC-Derived Records] (the "Previous 1987 version")

* [http://marc.coffeecode.net/oclc_2008_11_02/ Archived copy of 2-Nov-2008 version]
* [http://www.librarything.com/wiki/index.php?title=OCLC_Policy_Changes&diff=11748&oldid=11747 Difference between the November 2nd version and the November 5th version]
* [http://www.librarything.com/wiki/index.php?title=OCLC_Policy_Changes&diff=12067&oldid=12062 Difference between the November 5th version and the November 19th version]

== Petitions ==

On November 13, 2008, a petition called [http://watchdog.net/c/stop-oclc Stop the OCLC powergrab!] was started by Aaron Swartz to repeal the new policy. Background in his blog post, [http://www.aaronsw.com/weblog/oclcscam Stealing Your Library: The OCLC Powergrab].

On December 1, 2008, Elaine Sanchez created a new [http://www.petitiononline.com/oclc/petition.html petition] with more depth and specificity. The petition calls for OCLC to vacate the new policy, create a more open process for revising the 1987 guidelines, and assert that the records are the property of the respective contributing members. Ms. Sanchez [http://news.gmane.org/find-root.php?message_id=%3cA5EA7312DD1822479490004ED396177E96E8D2D455%40BOBCATMAIL4.matrix.txstate.edu%3e posted an announcement about it] on the Autocat mailing list.

== Commentary Regarding First Revision (nov 2) ==

* pmurray - [http://dltj.org/article/oclc-gbs-speculation/ Is OCLC’s Change of WorldCat Record Use/Transfer Policy Related to the Google Book Search Agreement?]
* jrochkind - [http://bibwild.wordpress.com/2008/11/03/viral-nature-of-oclc-usage-policy-like-open-source-no/ viral nature of OCLC usage policy–like open source? No.]
* Thingology - [http://www.librarything.com/thingology/2008/11/worldcat-policy-change.php OCLC Policy Change]
* Ed Summers - [http://inkdroid.org/journal/2008/11/03/bibliovirus/ Bibliovirus]
* Dan Scott - [http://coffeecode.net/archives/174-Archive-of-OCLC-WorldCat-Policy-as-posted-2008-11-02.html Archive of OCLC WorldCat Policy as posted 2008-11-02]
* Libology - [http://www.libology.com/blog/2008/11/03/oclc-worldcat-is-the-tiger-not-the-lady.html OCLC WorldCat is the Tiger, not the Lady]

== Commentary Regarding Second Revision (nov 5) / General ==

{| class="wikitable sortable"
|- style="text-align: left;"
! Date !! Author !! Title
|-
| 2008-11-02 || Reese, Terry || [http://oregonstate.edu/~reeset/blog/archives/574 OCLC’s proposed new guidelines for the transfer of bibliographic records]
|-
| 2008-11-03 || Reese, Terry || [http://oregonstate.edu/~reeset/blog/archives/579 What would it look like if OCLC was broken up?]
|-
| 2008-11-03 || Corrado, Ed || [http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/ oclc’s new policy for use and transfer of worldcat records]
|-
| 2008-11-04 || Calhoun, Karen || [http://community.oclc.org/metalogue/archives/2008/11/notes-on-oclcs-updated-record.html Notes on OCLC's Updated Record Use Policy] (NC)
|-
| 2008-11-04 || Panlibus || [http://blogs.talis.com/panlibus/archives/2008/11/what-are-oclc-playing-at.php What are OCLC playing at?]
|-
| 2008-11-04 || Mahoney, Richard || [http://lists.indexdata.dk/pipermail/yazlist/2008-November/002594.html Yazlist: Impact of new OCLC `Policy for Use and Transfer of WC Records' on federated search/virtual union catalogues] (NC)
|-
| 2008-11-05 || Coombs, Karen || [http://www.librarywebchic.net/wordpress/2008/11/05/whos-record-is-it-anyway/ Who’s record is it anyway?]
|-
| 2008-11-05 || Corrado, Ed || [http://blog.ecorrado.us/2008/11/05/karen-calhoun-on-worldcat/ karen calhoun on oclc’s updated record use policy]
|-
| 2008-11-05 || Corrado, Ed || [http://blog.ecorrado.us/2008/11/05/new-oclc-policy-on-worldcat-records-re-released/ new oclc policy on worldcat records re-released]
|-
| 2008-11-05 || Open Content Alliance || [http://www.opencontentalliance.org/?p=162 New OCLC Records Policy Generates Debate]
|-
| 2008-11-05 || Reese, Terry || [http://oregonstate.edu/~reeset/blog/archives/582 A look at the Policy for Use and Transfer of WorldCat Records revision]
|-
| 2008-11-05 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2008/11/05/more-on-oclcs-policies/ More on OCLC’s policies]
|-
| 2008-11-06 || ''Library Journal'' || [http://www.libraryjournal.com/article/CA6612175.html After Delay, OCLC Lays Out New Policy for Records Use and Transfer] (NC)
|-
| 2008-11-06 || Repohate || [http://repohate.blogspot.com/2008/11/declaration-of-independance-of-metadata.html Declaration of Independance of Metadata]
|-
| 2008-11-06 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2008/11/06/copyright-trivia/ copyright trivia], [http://bibwild.wordpress.com/2008/11/06/one-more/ one more]
|-
| 2008-11-06 || Styles, Rob || [http://dynamicorange.com/2008/11/06/oclc-record-usage-copyright-contracts-and-the-law/ OCLC, Record Usage, Copyright, Contracts and the Law]
|-
| 2008-11-07 || Corrado, Ed || [http://blog.ecorrado.us/2008/11/07/update-on-oclc-worldcat-policy/ update on oclc worldcat policy]
|-
| 2008-11-07 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2008/11/07/a-logical-oclc-argument/ A logical OCLC argument]
|-
| 2008-11-07 || Wallis, Richard (Panlibus) || [http://blogs.talis.com/panlibus/archives/2008/11/keeping-the-worldcat-in-the-bag.php Keeping the WorldCat in the bag]
|-
| 2008-11-12 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2008/11/12/i-dont-actually-want-to-destroy-oclc/ I don’t actually want to destroy OCLC]
|-
| 2008-11-12 || Uncontrolled Vocabulary #62 (podcast) || [http://uncontrolledvocabulary.com/2008/11/12/uncontrolled-vocabulary-62-a-reliable-guide-to-unicorns/ A Reliable Guide to Unicorns]
|-
| 2008-11-12 || Wallis, Richard (Panlibus) || [http://blogs.talis.com/panlibus/archives/2008/11/oclc-any-questions.php OCLC – any questions?]
|-
| 2008-11-13 || Hartman-Caverly, Sarah || [http://seriallyyours.wordpress.com/2008/11/13/final-policy-for-use-and-transfer-of-worldcat-records-post-by-oclc/ Final ‘Policy for Use and Transfer of WorldCat Records’ Posted by OCLC]
|-
| 2008-11-13 || O'Steen, Ben || [http://oxfordrepo.blogspot.com/2008/11/oclc-viral-licence-being-added-to.html OCLC - viral licence being added to WorldCat data]
|-
| 2008-11-13 || Slashdot || [http://news.slashdot.org/article.pl?sid=08/11/13/1929213 Non-Profit Org Claims Rights In Library Catalog Data] (NC)
|-
| 2008-11-13 || Swartz, Aaron || [http://www.aaronsw.com/weblog/oclcscam Stealing Your Library: The OCLC Powergrab] (NC)
|-
| 2008-11-14 || ''Inside Higher Ed'' || [http://www.insidehighered.com/news/2008/11/14/worldcat Maelstrom Over Metadata] (NC)
|-
| 2008-11-14 || Calhoun, Karen / Roy Tennant / Richard Wallis || [http://blogs.talis.com/panlibus/archives/2008/11/oclc-talk-with-talis-about-the-new-record-use-policy.php OCLC Talk with Talis about the new Record Use Policy]
|-
| 2008-11-14 || Calhoun, Karen (via Autocat) || [http://news.gmane.org/find-root.php?message_id=%3c2FA61018D659CF4B95A0F938AE66965A037EAA5A%40OAEXCH4SERVER.oa.oclc.org%3e OCLC Record Use Policy] (NC)
|-
| 2008-11-14 || Corrado, Ed || [http://blog.ecorrado.us/2008/11/14/oclc-worldcat-record-policy-makes-it-to-inside-higher-ed-and-slashdot/ OCLC WorldCat Record Policy makes it to Inside Higher Ed and Slashdot]
|-
| 2008-11-14 || Libology || [http://www.libology.com/blog/2008/11/14/more-oclc-comments.html More OCLC Comments]
|-
| 2008-11-14 || Litwin, Roy || [http://libraryjuicepress.com/blog/?p=792 OCLC Powergrab?]
|-
| 2008-11-14 || Sanchez, Elaine (via Autocat) || [http://news.gmane.org/find-root.php?message_id=%3cA5EA7312DD1822479490004ED396177E96E853AE0A%40BOBCATMAIL4.matrix.txstate.edu%3e Petition to stop OCLC from initiating the new WorldCat Policy] (NC)
|-
| 2008-11-14 || Styles, Rob || [http://dynamicorange.com/2008/11/14/more-oclc-policy/ More OCLC Policy…]
|-
| 2008-11-14 || Suburban Banshee || [http://suburbanbanshee.wordpress.com/2008/11/14/oclc-gets-grabby/ OCLC Gets Grabby]
|-
| 2008-11-15 || Corrado, Ed || [http://blog.ecorrado.us/2008/11/15/talis-podcast-about-oclc-worldcat-record-use-policy-with-karen-clahoun-and-roy-tennant/ Talis Podcast about OCLC WorldCat Record Use Policy with Karen Clahoun and Roy Tennant]
|-
| 2008-11-15 || LISnews || [http://lisnews.org/oclc_claims_ownership_data_opacs OCLC Claims Ownership of Data In OPACs]
|-
| 2008-11-15 || Swartz, Aaron || [http://www.aaronsw.com/weblog/oclcreply OCLC on the Run] (NC)
|-
| 2008-11-15 || West, Jessamyn || [http://www.librarian.net/stax/2536/what-is-up-with-oclc/ What is up with OCLC?]
|-
| 2008-11-16 || Mazzocchi, Stefano || [http://www.betaversion.org/~stefano/linotype/news/220/ Rule #1 for Surviving Paradigm Shifts: Don’t S**t Where You Eat]
|-
| 2008-11-16 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2008/11/16/more-oclc/ more OCLC]
|-
| 2008-11-16 || Schwartz, Christine || [http://www.catalogingfutures.com/catalogingfutures/2008/11/essential-listening-calhoun-and-tennant-on-oclcs-policy.html Essential listening: Calhoun and Tennant on OCLC's policy]
|-
| 2008-11-17 || Alford, Larry (Chair, OCLC Board of Trustees) || [http://www.oclc.org/worldcat/catalog/policy/trusteesletter.pdf An open letter to the OCLC membership on the WorldCat Record Use Policy] (NC)
|-
| 2008-11-17 || Annoyed Librarian || [http://www.libraryjournal.com/blog/580000658/post/290036629.html How I Learned to Stop Worrying and Love OCLC] (NC)
|-
| 2008-11-18 || Mehta, Devanshu || [http://www.geekactivism.com/2008/11/18/on-community-based-collaboration-lesson-from-the-oclc-debacle/ On Community-Based Collaboration: Lesson From the OCLC Debacle]
|-
| 2008-11-18 || Styles, Rob || [http://dynamicorange.com/2008/11/18/schroedingers_worldcat/ Schroedinger’s WorldCat]
|-
| 2008-11-18 || Baker, Gavin || [http://www.earlham.edu/~peters/fos/2008/11/oclc-fighting-oa-to-bibliographic-data.html OCLC fighting OA to bibliographic data]
|-
| 2008-11-18 || Lawson, Steve || [http://stevelawson.name/seealso/archives/2008/11/clarifications_and_cautions.html Clarifications and Cautions]
|-
| 2008-11-19 || Lang, John || [http://lonewolflibrarian.wordpress.com/2008/11/19/oclc-and-google-policy-discussion-continues111908/ OCLC and Google Policy Discussion Continues…11.19.08]
|-
| 2008-11-19 || Library 2.0 Gang (podcast) || [http://librarygang.talis.com/2008/11/19/library-20-gang-1008-policy-oclc-google-book-search/ Library 2.0 Gang 10/08: Policy – OCLC & Google Book Search]
|-
| 2008-11-19 || Sauers, Michael (screenshot) || [http://www.flickr.com/photos/travelinlibrarian/3044179351/ Hey Roy, remember this?] (NC)
|-
| 2008-11-19 || Uncontrolled Vocabulary #63 (podcast) || [http://uncontrolledvocabulary.com/2008/11/19/uncontrolled-vocabulary-63-aacr3-now-with-frbr/ Uncontrolled Vocabulary #63 - AACR3, now with FRBR] (OCLC discussion starts at the 20:50 mark.)
|-
| 2008-11-19 || Mark Ockerbloom, John || [http://everybodyslibraries.com/2008/11/19/drawing-a-line-in-the-sand-part-1-the-importance-of-open-library-metadata/ Drawing a line in the sand, Part 1: The importance of open library metadata]
|-
| 2008-11-20 || Spalding, Tim || [http://www.librarything.com/thingology/2008/11/oclc-policy-re-re-released-now-in.php OCLC Policy Re-re-released, now in unfriendly PDF]
|-
| 2008-11-20 || Jastram, Iris || [http://pegasuslibrarian.blogspot.com/2008/11/oclc-kerfuffle-in-which-i-write-much.html The OCLC Kerfuffle: In which I write much but come to few conclusions]
|-
| 2008-11-20 || Bridle, James || [http://www.liberalconspiracy.org/2008/11/20/the-great-public-library-scandal/ The great public library scandal]
|-
| 2008-11-21 || Sauers, Michael || [http://www.travelinlibrarian.info/2008/11/oclc-and-cc.html OCLC and CC]
|-
| 2008-11-21 || Mehta, Devanshu || [http://www.geekactivism.com/2008/11/21/the-continuing-adventures-of-worldcat-conditions-not-restrictions/ Continuing Adventures of WorldCat: Conditions, not Restrictions]
|-
| 2008-11-21 || Wallis, Richard || [http://blogs.talis.com/panlibus/archives/2008/11/oclc-questions-answers-and-an-open-letter.php OCLC - Questions Answers and an Open Letter]
|-
| 2008-11-21 || Coyle, Karen || [http://kcoyle.blogspot.com/2008/11/fork-worldcat.html Fork WorldCat]
|-
| 2008-11-21 || Mark Ockerbloom, John || [http://everybodyslibraries.com/2008/11/21/drawing-a-line-in-the-sand-part-2-problems-with-oclcs-catalog-policy/ Drawing a line in the sand, Part 2: Problems with OCLC’s catalog policy]
|-
| 2008-11-24 || Kleinman, Molly || [http://mollykleinman.com/2008/11/24/oclc-licensing-saga/ The OCLC data licensing saga: Adapt or die]
|-
| 2008-11-24 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2008/11/24/of-identifiers-matching-oclcnums-and-umlaut/ Of Identifiers, matching, OCLCnums, and Umlaut]
|-
| 2008-11-24 || Mark Ockerbloom, John || [http://everybodyslibraries.com/2008/11/24/drawing-a-line-in-the-sand-part-3-how-to-respond/ Drawing a line in the sand, Part 3: How to respond?]
|-
| 2008-11-24 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2008/11/24/creative-commons-is-not-appropriate-for-data/ Creative Commons is not appropriate for data]
|-
| 2008-11-25 || Salo, Dorothea || [http://cavlec.yarinareth.net/2008/11/25/oclc-catalogue-records-and-labor/ OCLC, catalogue records, and labor]
|-
| 2008-11-25 || Mehta, Devanshu || [http://www.geekactivism.com/2008/11/25/i-can-haz-worldcats/ I Can Haz Worldcat?]
|-
| 2008-11-26 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2008/11/26/380/ OCLC, and what we lose without openness (a True Story)]
|-
| 2008-11-26 || Corrado, Ed || [http://blog.ecorrado.us/2008/11/26/putting-your-golden-eggs-in-one-basket/ Putting Your Golden Eggs in One Basket]
|-
| 2008-11-27 || NELLCO USS project blog || [http://blog.nellco.org/?p=47 USS Use of OCLC MARC Records]
|-
| 2008-11-28 || Coyle, Karen || [http://kcoyle.blogspot.com/2008/11/oclc-use-policy-details-your-records.html OCLC Use Policy Details: Your Records]
|-
| 2008-11-28 || Kline, Heather || [http://heatherjkline.wordpress.com/2008/11/28/maelstrom-over-metadata/ "Maelstrom over Metadata"]
|-
| 2008-11-28 || Coyle, Karen || [http://kcoyle.blogspot.com/2008/11/oclc-use-policy-details-use-and.html OCLC Use Policy Details: Use and Transparency]
|-
| 2008-12-01 || Schwartz, Christine || [http://www.catalogingfutures.com/catalogingfutures/2008/12/oclc-policy-spreading-the-bibliographic-wealth-around.html OCLC policy: spreading the bibliographic wealth around?]
|-
| 2008-12-01 || Sanchez, Elaine (via autocat) || [http://news.gmane.org/find-root.php?message_id=%3cA5EA7312DD1822479490004ED396177E96E8D2D455%40BOBCATMAIL4.matrix.txstate.edu%3e Petition for OCLC to Collaboratively Re-write Policy for Use and Transfer of WorldCat Records] (NC)
|-
| 2008-12-01 || York University Libraries Bibliographic Services || [http://www.yorku.ca/yul/bibserv/blog/?p=190 The Bib Blog: Petition for OCLC to Collaboratively Re-write Policy for Use and Transfer of WorldCat Records]
|-
| 2008-12-04 || Voss, Jacob || [http://jakoblog.de/2008/12/04/bibliographische-daten-muessen-frei-sein/ Bibliographische Daten müssen frei sein] ([http://translate.google.com/translate?u=http%3A//jakoblog.de/2008/12/04/bibliographische-daten-muessen-frei-sein/&hl=en&langpair=auto%2Fen&tbb=1&ie=UTF-8 rough English translation] via Google)
|-
| 2008-12-07 || Spalding, Tim || [http://www.librarything.com/thingology/2008/12/elusive-moose-and-oclc.php The Elusive Moose and OCLC]
|-
| 2008-12-07 || barbarakitten_t (Livejournal) || [http://community.livejournal.com/library_mofo/988321.html OCLC Policy Suckage] (NC)
|-
| 2008-12-07 || Anonymous blogger (paraprofessional?*) || [http://kittent.wordpress.com/2008/12/07/oclc-policy-sucks/ OCLC policy Sucks]
|-
| 2008-12-08 || techdirt || [http://www.techdirt.com/articles/20081208/1224123056.shtml Landgrab For Ownership Of Library Catalog Data]
|-
| 2008-12-09 || Missouri Libr Net Corp || [http://pipeup.wordpress.com/2008/12/09/worldcat-records-policy-update/ WorldCat Records Policy Update]
|-
| 2008-12-09 || PALINET Cataloging Blog || [http://blog.palinet.org/cat/?p=118 OCLC Record Use Policy]
|-
| 2008-12-09 || Spalding, Tim || [http://www.librarything.com/thingology/2008/12/new-oclc-policy-and-federal-libraries.php The New OCLC Policy and Federal Libraries]
|-
| 2008-12-10 || Mason, Rick || [http://www.libology.com/blog/2008/12/10/oclc-license-policy-a-recommendation.html OCLC License Policy - A Recommendation]
|-
| 2008-12-10 || ''Autocat'' list discussion || [http://news.gmane.org/find-root.php?message_id=%3cDE579CE2077A804AB69F6A84F17421DA0F0F37%40TFTMEXCH1.tufts.ad.tufts.edu%3e Re: The new OCLC Policy and Federal libraries] [http://news.gmane.org/find-root.php?message_id=%3c17C8A0DAFF17854790F2BC013D9F5BC5132D328583%40XVS2%2dCLUSTER.yu.yale.edu%3e more] [http://news.gmane.org/find-root.php?message_id=%3cDE579CE2077A804AB69F6A84F17421DA0F0F38%40TFTMEXCH1.tufts.ad.tufts.edu%3e more] [http://news.gmane.org/find-root.php?message_id=%3cDE579CE2077A804AB69F6A84F17421DA0F0F39%40TFTMEXCH1.tufts.ad.tufts.edu%3e more] [http://news.gmane.org/find-root.php?message_id=%3c63d3c8ce0812101051rf0b0cdbg825c7e26ee7c4002%40mail.gmail.com%3e more] [http://news.gmane.org/find-root.php?message_id=%3cPine.SOL.4.21.0812101417360.13972%2d100000%40sun8.loc.gov%3e more] [http://news.gmane.org/find-root.php?message_id=%3cDE579CE2077A804AB69F6A84F17421DA0F0F3A%40TFTMEXCH1.tufts.ad.tufts.edu%3e more] [http://news.gmane.org/find-root.php?message_id=%3cPine.SOL.4.21.0812102245300.27468%2d100000%40sun8.loc.gov%3e more] (NC)
|-
| 2008-12-12 || Anonymous blogger (Cainmark) || [http://cainmark.livejournal.com/629741.html OCLC trying to use its EULA to hold freely given catolog data hostage.] (NC)
|-
| 2008-12-12 || ''American Libraries Online'' || [http://www.ala.org/ala/alonline/currentnews/newsarchive/2008/december2008/worldcatobjections.cfm WorldCat Policy Revision Draws Librarians’ Ire] (NC)
|-
| 2008-12-12 || Open Libraries Tech list || [http://mail.archive.org/pipermail/ol-tech/2008-December/thread.html#192 the land-grabs] (NC)
|-
| 2008-12-12 || Klienman, Molly || [http://librarycopyright.net/wordpress/?p=180 OCLC licensing saga]
|-
| 2008-12-13 || Schneider, Karen || [http://freerangelibrarian.com/2008/12/13/oclcs-policy-train-stop-cried-the-constable-on-the-rails/ OCLC’s policy: Train, stop, cried the constable on the rails]
|-
| 2008-12-15 || Wallis, Richard || [http://blogs.talis.com/panlibus/archives/2008/12/oclc-record-sharing-yogurt-and-copyright.php OCLC Record Sharing, Yogurt, and Copyright]
|-
| 2008-12-16 || ''Library Journal'' || [http://www.libraryjournal.com/article/CA6622391.html?rssid=191 ARL/ASERL Task Force to Investigate OCLC Policy Change] (NC)
|-
| 2008-12-16 || Spalding, Tim || [http://www.librarything.com/thingology/2008/12/new-oclc-logos.php New OCLC logos], [http://www.librarything.com/thingology/2008/12/666.php more]
|-
| 2008-12-18 || Salo, Dorothea || [http://cavlec.yarinareth.net/2008/12/18/thursday-wtfery/ Thursday WTFery]
|-
| 2008-12-20 || Singer Gordon, Rachel || [http://www.lisjobs.com/blog/?p=401 Mine! Mine! Mine!]
|-
| 2009-01-04 || McGrath, Kelley || [http://news.gmane.org/find-root.php?message_id=%3c20439895A37DB5408D0D28C0177E097F3D90DD7C61%40EMAILBACKEND01.bsu.edu%3e OCLC's new WorldCat Record Policy, original cataloging, and 040 $a] [http://news.gmane.org/find-root.php?message_id=%3c2FA61018D659CF4B95A0F938AE66965A03D09B9A%40OAEXCH4SERVER.oa.oclc.org%3e more] [http://news.gmane.org/find-root.php?message_id=%3cA070928F0B0F46EFA59DE0EBFFBD7D31%40cstserver.local%3e more] (NC)
|-
| 2009-01-07 || Houghton-Jan, Sarah || [http://librarianinblack.typepad.com/librarianinblack/2009/01/problems-with-oclc-policy-on-worldcat-records.html Problems with OCLC Policy on WorldCat Records] (NC)
|-
| 2009-01-07 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2009/01/07/bibliosnet-and-the-future-of-cataloging/ biblios.net and the future of cataloging]
|-
| 2009-01-09 || Leggott, Mark || [http://loomware.typepad.com/loomware/2009/01/oclc-worldcat-record-policy-petition.html OCLC WorldCat Record Policy Petition] (NC)
|-
| 2009-01-10 || Morgan, Eric Lease || [http://litablog.org/2009/01/10/eric-lease-morgans-top-tech-trends-for-ala-mid-winter-2009/ Eric Lease Morgan’s Top Tech Trends for ALA Mid-Winter, 2009]
|-
| 2009-01-11 || Spalding, Tim || [http://www.librarything.com/thingology/2009/01/this-is-like-heinlein-novel.php This is like a Heinlein novel!]
|-
| 2009-01-11 || Spalding, Tim || [http://www.librarything.com/thingology/2009/01/why-libraries-must-reject-oclc-policy.php Why libraries must reject the OCLC Policy (part 1)]
|-
| 2009-01-12 || Kleinman, Molly || [http://librarycopyright.net/wordpress/?p=180 OCLC licensing saga]
|-
| 2009-01-12 || Mason, Rick || [http://www.libology.com/blog/2009/01/11/why-libraries-must-reject-the-oclc-policy.html Why Libraries Must Reject the OCLC Policy]
|-
| 2009-01-12 || Kellat, Stephen Michael || [http://www.lisnews.org/listen_lisnews_org_podcast_episode_56 LISTen: The LISNews.org Podcast -- Episode #56 (Commentary portion of episode)]
|-
| 2009-01-13 || Datema, Jay || [http://www.bookism.org/open/2009/01/13/lock-in-leads-to-lockdown/ Lock-in leads to lockdown]
|-
| 2009-01-13 || Spalding, Tim || [http://www.librarything.com/thingology/2009/01/oclc-protest-teeshirts-are-here.php OCLC protest teeshirts are here!]
|-
| 2009-01-13 || OCLC, Board of Trustees, Members Council || [http://www.oclc.org/us/en/news/releases/20092.htm Review Board of Shared Data Creation and Stewardship]
|-
|}

* "working as staff at University of Illinois, Urbana-Champaign"

== Commentary Following the Announcement of the Review Board ==

{| class="wikitable sortable"
|- style="text-align: left;"
! Date !! Author !! Title
|-
| 2009-01-13 || Reese, Terry || [http://oregonstate.edu/~reeset/blog/archives/612 OCLC to convene a Review Board of Shared Data Creation and Stewardship]
|-
| 2009-01-13 || ''LISNews'' || [http://lisnews.org/oclc_convene_review_board_shared_data OCLC to convene Review Board of Shared Data]
|-
| 2009-01-13 || Mason, Rick || [http://www.libology.com/blog/2009/01/13/oclc-creates-review-board-of-shared-data-creation-and-stewardship.html OCLC Creates Review Board of Shared Data Creation and Stewardship]
|-
| 2009-01-14 || Bigwood, David || [http://catalogablog.blogspot.com/2009/01/oclc-record-sharing-news.html OCLC Record Sharing News]
|-
| 2009-01-14 || Open Content Alliance blog || [http://www.opencontentalliance.org/2009/01/14/is-oclc-reconsidering-its-proposed-records-policy/ Is OCLC Reconsidering its Proposed Records Policy?]
|-
| 2009-01-14 || Styles, Rob || [http://blogs.talis.com/panlibus/archives/2009/01/oclc-is-listening.php OCLC is listening.]
|-
| 2009-01-14 || Coyle, Karen || [http://kcoyle.blogspot.com/2009/01/oclc-pushes-back-policy-to-fall-2009.html OCLC pushes back policy to fall, 2009]
|-
| 2009-01-14 || Mark Ockerbloom, John || [http://everybodyslibraries.com/2009/01/14/chances-to-stop-and-think-about-the-future-of-library-catalogs/ Chances to stop and think about the future of library catalogs]
|-
| 2009-01-15 || Uncontrolled Vocabulary #67 (podcast) || [http://uncontrolledvocabulary.com/2009/01/15/uncontrolled-vocabulary-67-policy-driven-drm/ Uncontrolled Vocabulary #67 ("Policy-driven DRM")]
|-
| 2009-01-15 || ''AUTOCAT mailing list'' || [http://news.gmane.org/find-root.php?message_id=%3cLISTSERV%25200901151548150370.1BA6%40LISTSERV.SYR.EDU%3e OCLC to review record use policy] (NC)
|-
| 2009-01-15 || Anonymous blogger || [http://catalogsofbabes.wordpress.com/2009/01/15/more-about-oclc-and-nipples/ From the Catalogs of Babes: more about OCLC and nipples]
|-
| 2009-01-15 || Chatterjee, Anirvan || [http://journal.bookfinder.com/archives/entry/000424.html Bookfinder Journal: Notes from all over] (NC)
|-
| 2009-01-15 || Schwartz, Christine || [http://www.catalogingfutures.com/catalogingfutures/2009/01/oclc-establishes-review-board-to-look-at-question-of-shared-library-data.html OCLC establishes review board to look at question of shared library data]
|-
| 2009-01-16 || Spalding, Tim || [http://www.librarything.com/thingology/2009/01/library-social-media-wins-one.php Library social media wins one]
|-
| 2009-01-16 || ''American Libraries Online'' || [http://www.ala.org/ala/alonline/currentnews/newsarchive/2009/January2009/worldcatreview.cfm OCLC Delays WorldCat Policy Pending Review Board] (NC)
|-
| 2009-01-17 || Matienzo, Mark A. || [http://thesecretmirror.com/mark/this-is-all-im-going-to-say-on-this-here-blogsite-concerning-the-brouhaha-about-the-policy-for-use-and-transfer-of-worldcat-records-because-i-have-other-more-interesting-and-more-complex-problems-t/comment-page-1 This Is All I’m Going To Say On This Here Blogsite ...]
|-
| 2009-01-22 || Grossman, Wendy M; ''The Guardian'' || [http://www.guardian.co.uk/technology/2009/jan/22/library-search-engines-books Why you can't find a library book in your search engine] (NC)
|-
| 2009-01-22 || ''FriendFeed commentary on Guardian article || [http://friendfeed.com/e/ae0253d3-1af3-404f-8889-e74a472b1d11/Why-you-can-t-find-a-library-book-in-your-search/ FriendFeed] (NC)
|-
| 2009-01-21 || Spalding, Tim || [http://www.librarything.com/thingology/2009/01/guardian-asks-why-you-cant-find-library.php The Guardian asks "Why you can't find a library book in your search engine?"]
|-
| 2009-01-22 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2009/01/22/oclc-in-the-guardian/ OCLC in the Guardian]
|-
| 2009-01-22 || Bermès, Manue || [http://figoblog.org/node/1953 Le côté obscur de la force ?] ([http://translate.google.com/translate?u=http%3A//figoblog.org/node/1953&hl=en&langpair=auto%7cen&tbb=1&ie=UTF-8 Translation to English] from French courtesy of Google) [NC]
|-
| 2009-01-22 || Lone Wolf Librarian || [http://lonewolflibrarian.wordpress.com/2009/01/22/oclc-policy-changes-appear-in-international-media012209/ OCLC Policy Change Controversy Appears in International Media]
|-
| 2009-01-22 || Biancu, Bonaria || [http://bonariabiancu.wordpress.com/2009/01/22/libraries-need-freedom/ Libraries need freedom] ([http://translate.google.com/translate?u=http%3A//bonariabiancu.wordpress.com/2009/01/22/libraries-need-freedom/&hl=en&langpair=auto%7cen&tbb=1&ie=UTF-8 Translation to English] from Italian courtesy of Google)
|-
| 2009-01-22 || Powell, Andy || [http://efoundations.typepad.com/efoundations/2009/01/why-cant-i-find-a-library-book-in-my-search-engine.html Why can't I find a library book in my search engine?] (NC)
|-
| 2009-01-22 || West, Jessamyn || [http://www.librarian.net/stax/2661/why-you-cant-google-a-library-book/ why you can’t google a library book]
|-
| 2009-01-22 || Baumgart, Jessica || [http://blogs.law.harvard.edu/jkbaumga/2009/01/22/why-you-can%e2%80%99t-google-a-library-book/ why you can’t google a library book]
|-
| 2009-01-22 || Ottevanger, Jeremy || [http://doofercall.blogspot.com/2009/01/worldcatoclc-get-rough-end-of-guardians.html WorldCat/OCLC get the rough end of the Guardian's stick]
|-
| 2009-01-23 || Marcel || [http://mondayevening.wordpress.com/2009/01/23/finding-and-reading-books/ Finding and reading books]
|-
| 2009-01-23 || ''the.effing.librarian'' || [http://effinglibrarian.blogspot.com/2009/01/oclc-vs-everyone.html OCLC vs. Everyone]
|-
| 2009-01-23 || Miedema, John || [http://johnmiedema.ca/2009/01/23/youve-heard-of-worldcat-now-meet-fuzzycat/ You’ve Heard of WorldCat, Now Meet FuzzyCat]
|-
| 2009-01-23 || Cairns, Michael || [http://personanondata.blogspot.com/2009/01/bibliographic-studies.html Bibliographic Studies]
|-
| 2009-01-25 || ''AUTOCAT mailing list'' || [http://article.gmane.org/gmane.education.libraries.autocat/19178 OCLC and the Guardian] [http://news.gmane.org/find-root.php?message_id=%3cPine.SOL.4.21.0901250927110.9718%2d100000%40sun8.loc.gov%3e more] [http://news.gmane.org/find-root.php?message_id=%3cPine.SOL.4.21.0901252149140.28128%2d100000%40sun8.loc.gov%3e more] [http://news.gmane.org/find-root.php?message_id=%3c497F24E6020000CA0004B82A%40ntgwgate.loc.gov%3e more] [http://news.gmane.org/find-root.php?message_id=%3cPine.SOL.4.21.0901271743270.24031%2d100000%40sun8.loc.gov%3e more] [http://news.gmane.org/find-root.php?message_id=%3cPine.SOL.4.21.0901271835590.24031%2d100000%40sun8.loc.gov%3e more] (NC)
|-
| 2009-01-26 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2009/01/26/enforcing-cataloging-copyright-whose-interest/ enforcing catalog record copyright is in whose interest?]
|-
| 2009-01-26 || Ahlberg, Carina || [http://www.biblioteksrelaterat.se/2009/01/varf%C3%B6r-man-inte-hittar-bibliotekets-b%C3%B6cker-i-google.html Varför man inte hittar bibliotekets böcker i Google] ([http://translate.google.com/translate?u=http%3A//www.biblioteksrelaterat.se/2009/01/varf%25C3%25B6r-man-inte-hittar-bibliotekets-b%25C3%25B6cker-i-google.html&hl=en&langpair=auto%7cen&tbb=1&ie=UTF-8 Translation to English] from Sweedish courtesy of Google)
|-
| 2009-01-27 || Calhoun, Karen || [http://www.slideshare.net/amarintha/creating-and-sustaining-communities-around-shared-data-the-case-of-oclc-presentation Creating and Sustaining Communities Around Shared Data: The Case of OCLC] (NC)
|-
| 2009-01-27 || Calhoun, Karen || [http://community.oclc.org/metalogue/archives/2009/01/data-sharing-libraries-and-the.html Data Sharing, Libraries, and the Landscape of the Web] (NC)
|-
| 2009-01-27 || Oder, Norman, ''Library Journal'' || [http://www.libraryjournal.com/article/CA6632413.html OCLC Defends Records Policy, Faces Questions, Suggestions, and Criticisms] (NC)
|-
| 2009-01-27 || Murray, Peter || [http://dltj.org/article/oclc-records-use-policy-1/ Consideration of OCLC Records Use Policy]
|-
| 2009-01-27 || ''York University Libraries Bibliographic Services'' || [http://www.yorku.ca/yul/bibserv/blog/?p=195 Guardian Article on OCLC, Libraries and the Internet]
|-
| 2009-01-28 || Lone Wolf Librarian || [http://lonewolflibrarian.wordpress.com/2009/01/28/oclc-yet-againtries-to-defend-controversial-policy-shift012809/ OCLC Yet Again Unsuccessfully Tries to Defend Controversial Major Policy Shift…01.28.09]
|-
| 2009-01-28 || ''LISNews'' || [http://www.lisnews.org/oclc_defends_records_policy_faces_questions_suggestions_and_criticisms OCLC Defends Records Policy, Faces Questions, Suggestions, and Criticisms]
|-
| 2009-01-28 || Kellat, Stephen Michael || [http://lisnews.org/reflections_upon_lj_story Reflections upon an LJ story]
|-
| 2009-01-28 || Rochkind, Jonathan || [http://bibwild.wordpress.com/2009/01/28/yet-more-on-copyright-and-cataloging/ yet more on copyright and cataloging]
|-
| 2009-01-28 || Ockerbloom, John Mark || [http://everybodyslibraries.com/2009/01/28/open-catalog-apis-and-data-ala-presentation-notes-posted/ Open catalog APIs and data: ALA presentation notes posted]
|-
| 2009-01-28 || Corrado, Ed || [http://blog.ecorrado.us/2009/01/28/library-journal-report-on-the-oclc-worldcat-policy/ Library Journal report on the OCLC WorldCat policy discussion]
|-
| 2009-01-28 || Murray, Peter || [http://dltj.org/article/oclc-records-use-policy-2/ Further Consideration of OCLC Records Use Policy]
|-
| 2009-01-28 || ''liblicense-l mailing list'' || [http://www.library.yale.edu/~llicense/ListArchives/0901/msg00115.html OCLC's New License for Bibliographic Records] (NC)
|-
| 2009-01-29 || Mason, Rick || [http://www.libology.com/blog/2009/01/29/oclc-license-policy-at-ala-midwinter.html OCLC License Policy at ALA Midwinter]
|-
| 2009-01-30 || ''AUTOCAT mailing list'' || [http://news.gmane.org/find-root.php?message_id=%3c705314404.777621233352002233.JavaMail.root%40sz0136a.westchester.pa.mail.comcast.net%3e Copyright in Bib Records] [http://news.gmane.org/find-root.php?message_id=%3cPine.SOL.4.21.0901311900170.1301%2d100000%40sun8.loc.gov%3e more] [http://news.gmane.org/find-root.php?message_id=%3cPine.SOL.4.21.0902010026210.29243%2d100000%40sun8.loc.gov%3e more] (NC)
|-
| 2009-02-01 || Spalding, Tim || [http://www.librarything.com/thingology/2009/02/evil-326.php The evil 3.26%]
|-
| 2009-02-02 || Mijnsbergen, Edwin || [http://www.zbdigitaal.nl/2009/02/te-lui-om-te-begrijpen.html Te lui om te begrijpen] ([http://translate.google.com/translate?u=http%3A//www.zbdigitaal.nl/2009/02/te-lui-om-te-begrijpen.html&hl=en&langpair=auto%7cen&tbb=1&ie=UTF-8 Translation to English] courtesy of Google)
|-
| 2009-02-02 || Lone Wolf Librarian || [http://lonewolflibrarian.wordpress.com/2009/02/02/librarything-responds-to-oclcs-monopoly-counter-defense020209/ LibraryThing Responds to OCLC’s Questioning of Motives…02.02.09]
|-
| 2009-02-02 || McNamara, Frances || [http://bdfar.wordpress.com/2009/02/02/oclc-hullaballou-ala-midwinter-2009-monday/ OCLC Hullaballou ALA Midwinter 2009 Monday]
|-
| 2009-02-06 || OCLC || [http://www.oclc.org/us/en/news/releases/200910.htm OCLC Board of Trustees, Members Council name Review Board of Shared Data Creation and Stewardship.]
|-
| 2009-02-07 || Mason, Rick || [http://www.libology.com/blog/2009/02/07/oclc-announces-review-board-members.html OCLC Announces Review Board Members]
|-
| 2009-02-07 || Murray, Peter || [http://dltj.org/article/oclc-review-board-members/ Members of the OCLC Review Board Announced]
|-
| 2009-02-09 || ''OCLC Review Board'' || [http://community.oclc.org/reviewboard/archives/2009/02/from-the-review-board.html From the Review Board] (Public comment space)
|-
| 2009-02-10 || Ostrowsky, Ben || [http://blog.benostrowsky.com/2009/02/10/oclc-should-share-worldcat-data-for-commercial-and-noncommercial-use/ OCLC should share WorldCat data for commercial and noncommercial use]
|-
| 2009-02-10 || McNamara, Frances || [http://bdfar.wordpress.com/2009/02/10/oclc-review-board/ OCLC Review Board]
|-
| 2009-02-10 || Murray, Peter || [http://dltj.org/article/oclc-review-board-blog/ OCLC Review Board’s Blog]
|-
| 2009-02-18 || Lawson, Steve || [http://stevelawson.name/seealso/archives/2009/02/matters_of_policy.html Matters of Policy]
|-
| 2009-02-19 || ''Miss Information'' || [http://closedstacks.wordpress.com/2009/02/19/big-brother-is-facebook/ Big Brother is Facebook (?)]
|-
| 2009-02-19 || Ivy || [http://catalogsofbabes.wordpress.com/2009/02/19/facebook-or-oclc-perhaps-both/ Facebook or OCLC? Perhaps both.]
|-
| 2009-02-20 || ARL || [http://www.arl.org/bm~doc/oclc-report-jan09.pdf Ad Hoc Task Force to Review the Proposed OCLC Policy for Use and Transfer of WorldCat Records: Final Report to the ARL Board, January 30, 2009] (PDF)
|-
| 2009-02-20 || ResourceShelf || [http://www.resourceshelf.com/2009/02/20/arl-recommends-community-wide-process-to-develop-new-oclc-policy-for-use-transfer-of-worldcat-records/ ARL Recommends Community-Wide Process to Develop New OCLC Policy for Use & Transfer of WorldCat Records]
|-
| 2009-02-21 || Mason, Rick || [http://www.libology.com/blog/2009/02/21/oclc-policy-final-report-to-the-arl-board.html OCLC Policy - Final Report to the ARL Board]
|-
| 2009-02-21 || Brantley, Peter || [http://blogs.lib.berkeley.edu/shimenawa.php/2009/02/21/sending-oclc-on-its-way Sending OCLC on its way]
|-
| 2009-02-23 || Spalding, Tim || [http://www.librarything.com/thingology/2009/02/research-libraries-clobber-oclc-policy.php Research libraries clobber OCLC Policy ]
|-
| 2009-02-23 || Goldstein, Jeremy || [http://geekylibrarian.wordpress.com/2009/02/23/another-blow/ Another Blow]
|-
| 2009-02-23 || Mason, Rick || [http://www.libology.com/blog/2009/02/23/librarything-on-the-arl-report.html LibraryThing on the ARL Report]
|-
| 2009-02-23 || ''Library Journal'' || [http://www.libraryjournal.com/article/CA6639210.html ARL Says OCLC Should Revise WorldCat Policy] (NC)
|-
| 2009-02-24 || Vielmetti, Edward || [http://vielmetti.typepad.com/superpatron/2009/02/pitchforks-for-oclc-rebellion-against-mandatory-licensing-for-cooperatively-developed-catalog-data.html Pitchforks for OCLC: rebellion against mandatory licensing for cooperatively developed catalog data] (NC)
|}

== Comments on Comments ==

Sometimes the best insight comes in the comments added to blog postings and other stories. [http://pipes.yahoo.com/pipes/pipe.info?_id=jOpatQmu3RGENlDTBRNMsA This Yahoo! Pipe] (also available as an [http://pipes.yahoo.com/pipes/pipe.run?_id=jOpatQmu3RGENlDTBRNMsA&_render=rss RSS feed]) is a concatenation of comments from the postings and stories listed on this page -- with the exception of those marked "(NC)" because of use of software that doesn't support comment feeds. It was last updated as of [http://wiki.code4lib.org/index.php?title=OCLC_Policy_Change&oldid=2309 page revision 2309].

[[Category: OCLC]]

SRU

2009-02-25T19:07:46Z

Edward Vielmetti:

SRU "is a standard XML-focused search protocol for Internet search queries, utilizing [[CQL]] (Contextual Query Language), a standard syntax for representing queries."

== More information ==
* [http://www.loc.gov/standards/sru/index.html SRU] home page at the [[Library of Congress]]
* [http://www.ariadne.ac.uk/issue40/morgan/ An Introduction to the Search/Retrieve URL Service (SRU)], Eric Lease Morgan, Ariadne 40, July 2004.

[[Category: Standards]]

SRU

2009-02-25T19:05:25Z

Edward Vielmetti: link to home page

WorldCat

2009-02-25T19:03:35Z

Edward Vielmetti: again de minimus

[[OCLC]] describes WorldCat as "a global network of library-management and user-facing services built upon cooperatively-maintained databases of bibliographic and institutional metadata.".

== More information ==
* [http://www.oclc.org/us/en/worldcat/ WorldCat] home page (US, English)

[[Category: OCLC]]

OCLC

2009-02-25T19:01:53Z

Edward Vielmetti: "about us" level information, so the link resolves

Localizable Views

2009-02-25T18:35:19Z

Edward Vielmetti: links out

[[Category:Patterns]]

There needs to be a way for local implementers to customize the 'templates' or 'views' to have, at a minimum, their own branding, without actually editing shared distribution code. Ideally, they should be able to customize as much as possible of the templates/views.

Localized templates/views should probably live in different directories than distributed templates/views, for ease of local source control.

There are a variety of ways to accomplish this, depending on environment.

== Specific example: XSLT ==

If your views are in [[XSLT]], the XSLT 'import' function provides a convenient method to allow over-riding of XSLT for localization.

Put your XSLT that is distributed with the application in one directory or directory tree.

Have another separate directory tree for local XSLT "overrides".

When your application loads an XSLT file, it can first check to see if an XSLT file with the same name/pat exists in the 'local' directory. If so, it can combine the 'distribution' and the 'local' version of that XSLT file can be combined together using XSLT 'import' statement, so that any templates or variables in the 'local' version will override the distribution version.

Application Example: Xerxes

Category:III

2009-02-25T18:33:25Z

Edward Vielmetti: New page: For, about, or regarding the III catalog.

For, about, or regarding the III catalog.

III Search URL Structure

2009-02-25T18:33:04Z

Edward Vielmetti:

This page goes over the URL structures for the normal III OPAC. This can be useful when trying to link back to functions that don't exist via API such as holds.

http://magic.msu.edu - normal hostname. Brings up page based on mainmenu.html

http://magic.msu.edu/search/ - specifies a search. Should be followed by the search type

http://magic.msu.edu/search/t - title search

http://magic.msu.edu/search/tgenetics - title search for genetics

== A Full Browse URL ==

http://magic.msu.edu/search/tgenetics/tgenetics/1,491,609,B/browse

* The first tgenetics is used to populate the search box and does not appear to affect the search
* The second tgenetics is the actual search terms. Changing this will change the results
* The '1' is the starting result. Changing this to '5' would have the results start at the 5th result.
* The '491' is the number of titles (or groups) retrieved. For a title search where titles are grouped this would be the number of groups. For keyword it is the same as number of results. Changing this will affect the number of titles displayed except for '1' which will display 12.
* The '609' is the number of results returned. Changing this does not actually affect the number displayed, just the text saying how many are returned.
* The 'B' is the display type. 'B' for Brief or 'E' for Expanded
* The /browse gives browse screens. There is also /limit for limiting the search, /marc for marc display if the search is for a bibnum, /request for requesting the book, /export to export all records from screen

[[Category: III]]

Innovative Documentation

2009-02-25T18:32:44Z

Edward Vielmetti:

== WebOPAC ==

* [[III Search URL Structure]]
* [[III XRecord]]

== XMLOPAC ==

* [[III Searching the XMLOPAC]]
* [[III Including III Data]]
* [[III Including Attached Item Records]]
* [[III Including Checkin Records]] - for journals, etc
* [[III Reserves]]
* [[III Known Problems]]
* [[III Tips and Tricks]]

[[Category: Documentation]]
[[Category: III]]

OPAC

2009-02-25T18:32:15Z

Edward Vielmetti: /* OPAC Replacements */

== OPAC Replacements ==

* [[Blacklight]]
* [[Helios]]
* [[SolrMarc]]
* [[VuFind]]

* [[Notes from Open Source Discovery Portal Camp]]

VuFind

2009-02-25T18:31:38Z

Edward Vielmetti: New page: : VuFind is a library resource portal designed and developed for libraries by libraries. The goal of VuFind is to enable your users to search and browse through all of your library's resou...

: VuFind is a library resource portal designed and developed for libraries by libraries. The goal of VuFind is to enable your users to search and browse through all of your library's resources by replacing the traditional OPAC.

== More information ==
* [http://vufind.org/ VuFind] home page
* [http://www.librarytechnology.org/ltg-displayarticle.pl?RC=12664 Villanova University releases VUFIND, an open source next generation library catalog], July 2007

Notes from Open Source Discovery Portal Camp

2009-02-25T18:29:40Z

Edward Vielmetti: give VuFind its own project page

== Notes from Open Source Discovery Portal Camp ==

On 6 November 2008, there was a meeting at the Palinet offices in Philadelphia to discuss the future of open source discovery portals. The [[VuFind]] and [http://blacklight.rubyforge.org/ Blacklight] projects had already started cooperating by sharing indexing code in the form of [http://code.google.com/p/solrmarc/ SolrMarc], and as a community we wanted to explore whether there were other ways we could be cooperating, and what our development priorities should be. We discussed the following topics and some people identified themselves as particularly interested in following up on specific topics and doing further work in a given area. Bess took notes, which are pasted here, but please feel free to expand upon these with your own memories of the conversation.

=== Jangle ===

Andrew started by giving us a brief introduction to [http://www.jangle.org/ Jangle], a standard approach to building a toolset for interacting with the ILS. It was kickstarted by the DLF ILS API set. The idea is to create a standard way of interacting with the ILS. Jangle is the first implementation of this, and is planned as the "reference implementation." It's an open source standard approach, and will give us a lot of flexibility.

Gabe points out that the DLF standard and the Jangle standard aren't the same thing exactly, but people seem to agree it's still a good start at standardization. Andrew asks, how do we contribute the VuFind drivers to Jangle? Is there an NCIP driver for Jangle? [http://www.extensiblecatalog.org/ Xtensible Catalog] is using NCIP, for example. One problem with this, though, is that many vendors don't implement NCIP.

Ross Singer is the main developer for Jangle, and he wrote an article about it for the latest code4lib journal. Everyone's homework is to go read that article, available [http://journal.code4lib.org/articles/109 here]. Many institutions are hacking their own ILS, it would be more efficient if we all share this code through something like Jangle, which could then be used by VuFind, Blacklight, [http://code.google.com/p/fac-back-opac/ Helios], or any other project that could talk to Jangle.

Eric Morgan: Jangle is a step in the right direction. DLF came up with a list of API features they want, and then Ross came along and said here's a simple RESTful implementation of a lot of that API, based on ATOM publishing protocol. We need a number of agreed upon shapes of URLs that do things like tell me the status of this book, authority information for a person. To what degree do we want to use something like Jangle in vufind? There aren't a lot of choices right now, and this seems like a good project to explore further.

What about XC? There's a lot of frustration around this project, because they say they are open source but haven't actually made any of their source available. How do we get them to participate with the larger community? There's a growing community of developers around these issues, and XC should be involved. Eric says someone should have explicitly invited them.

(interested in further development: Bess, Andrew, Gabe)

=== Non-catalog content / digital repositories ===

Could we adapt SolrMARC to also include SolrOAI? Yes, Bob, Naomi and Andrew all have ideas about how this could work. Sounds like this is the kernel of our kernel. Solr already has a lot of functionality to allow for this. Do we want a couple of plugins, one for solr and one for OAI? Or do we want an app that handles both?

Lots of little data silos aren't going to work, we need everything in a local catalog. But that doesn't mean we should all try to be google. We still need well-defined collection development policies.

What about social data? SoPAC is neat, and has an independent layer for saving social data.

We also talked about Blacklight and the ways it brings in various data sources and handles behavior for different kinds of objects, e.g., [http://musicbrainz.org/ MusicBrainz] data for music items.

(interested in further development: Bob, Dennis, Peter, Naomi, Bess)

=== solr marc ===

Q: How well is solr marc handling bad data these days?

Bob: I've been adding to marc4j more permissive reading and error correction. It's also reporting errors as it finds them, to make it easier to find bad records. Request for writing to log files instead of standard out. How to handle records with bad leaders? Naomi has some marc test data. We need more test driven development.

Naomi is offering code for parsing OCLC numbers and LC numbers, she'll be working with Bob next week to get that into solrmarc.

Chris from Villanova is going to do some graphic design work for solr marc. Yay!

(Interested in further development: Bob, Naomi, Chris, Bess)

=== Authority control ===

Can we get the LC authority control data, index it locally, and take advantage of that in our searching. Actually getting the authority index data is the problem. It's government monitored data, so why can't we get access to it? We can get snapshots, but there's no method for harvesting it. We need some way to get weekly / monthly updates of authority data. EdSu might have set something up, but it isn't an official service.

Eric says go ahead and implement something, and don't worry about the update method right now. Can we get authority data? Does Open Library have any authority data? Bess will look into this.

"Fred Data" <-- subject authorities

Consensus seems to be that we need a proof of concept first, see how well that scales, and then after that start lobbying LC / OCLC / Palinet / other vendors.

(Interested in further development: Ya'aqov, Daniel, Mark, Bess)

=== Dedupping / FRBR ===

We need to look at Trish Williams' work with hierarchical solr records for implementing FRBR. If we start working with this maybe we can advocate for getting this into the solr trunk.

Do we really need FRBR or will "other editions" do the trick? xISBN and xISSN does a pretty good job from OCLC, and can be implemented in just a few lines of code. No one understands FRBR anyway.

One user group that could really use FRBR is musicians, to tie together recordings and scores. The Variations project at Indiana is working with this. OCLC also made public their algorithm for FRBRizing work. Some libraries have a problem stemming from having digitized versions of an item, and then the digital version has a catalog entry, but then in your VuFind system you index both the digital surrogate and the catalog record about the digital surrogate. You probably want to combine these or suppress

Open Library is also very interested in de-duping research.

=== Serials holdings ===

Marc format for holdings data (MFHD)
xISSN service might be helpful for this, too
Bibliographic records for serials should refer to each other.

How to represent this data for users? There's a summary holdings field, a one-line display, and then there's a detailed holding display. There can be multiple screens of lines with this. Summary holdings are pretty easy, detail holdings are hard. Are they necessary?

Maybe we can handle this the way we're doing "composition era" in blacklight? If we know the range, we can assign values for all possible values of this range.

You can get an extract of all serial holdings from your Open URL database (SFX), harvest your journal holdings through that. Texas A&M is doing this w/ SFX. This seems like an efficient way of getting detailed holdings. Indexing this might be helpful if you don't have marc records for all of your electronic holdings, and it also might help for knowing when you have full text online and when you don't.

(interested in further development: Ya'aqov, Mark)

=== Federated Search / article content ===

Can we partner with LibraryFind? Or should we implement an engine like pazpar2?
IndexData has something called pazpar2, which is a federated search engine.

(Interested in further development: one guy, whose name I didn't catch. Please self identify!)

=== back-end arch / OSS methods ===

We never really discussed this, but Peter and Peter said they were interested in following up on this topic.

=== kernelizing the projects ===

- solrmarc
- solroai
- authority data & merging

=== How do we organize - How do we reach out to libraries and formalize a committment? ===
John, Dennis, Joe, Andrew, Mark, Daniel

[[Category: Meeting agendas]]

Notes from Open Source Discovery Portal Camp

2009-02-25T18:28:36Z

Edward Vielmetti:

== Notes from Open Source Discovery Portal Camp ==

On 6 November 2008, there was a meeting at the Palinet offices in Philadelphia to discuss the future of open source discovery portals. The [http://vufind.org/ VuFind] and [http://blacklight.rubyforge.org/ Blacklight] projects had already started cooperating by sharing indexing code in the form of [http://code.google.com/p/solrmarc/ SolrMarc], and as a community we wanted to explore whether there were other ways we could be cooperating, and what our development priorities should be. We discussed the following topics and some people identified themselves as particularly interested in following up on specific topics and doing further work in a given area. Bess took notes, which are pasted here, but please feel free to expand upon these with your own memories of the conversation.

=== Jangle ===

Andrew started by giving us a brief introduction to [http://www.jangle.org/ Jangle], a standard approach to building a toolset for interacting with the ILS. It was kickstarted by the DLF ILS API set. The idea is to create a standard way of interacting with the ILS. Jangle is the first implementation of this, and is planned as the "reference implementation." It's an open source standard approach, and will give us a lot of flexibility.

Gabe points out that the DLF standard and the Jangle standard aren't the same thing exactly, but people seem to agree it's still a good start at standardization. Andrew asks, how do we contribute the VuFind drivers to Jangle? Is there an NCIP driver for Jangle? [http://www.extensiblecatalog.org/ Xtensible Catalog] is using NCIP, for example. One problem with this, though, is that many vendors don't implement NCIP.

Ross Singer is the main developer for Jangle, and he wrote an article about it for the latest code4lib journal. Everyone's homework is to go read that article, available [http://journal.code4lib.org/articles/109 here]. Many institutions are hacking their own ILS, it would be more efficient if we all share this code through something like Jangle, which could then be used by VuFind, Blacklight, [http://code.google.com/p/fac-back-opac/ Helios], or any other project that could talk to Jangle.

Eric Morgan: Jangle is a step in the right direction. DLF came up with a list of API features they want, and then Ross came along and said here's a simple RESTful implementation of a lot of that API, based on ATOM publishing protocol. We need a number of agreed upon shapes of URLs that do things like tell me the status of this book, authority information for a person. To what degree do we want to use something like Jangle in vufind? There aren't a lot of choices right now, and this seems like a good project to explore further.

What about XC? There's a lot of frustration around this project, because they say they are open source but haven't actually made any of their source available. How do we get them to participate with the larger community? There's a growing community of developers around these issues, and XC should be involved. Eric says someone should have explicitly invited them.

(interested in further development: Bess, Andrew, Gabe)

=== Non-catalog content / digital repositories ===

Could we adapt SolrMARC to also include SolrOAI? Yes, Bob, Naomi and Andrew all have ideas about how this could work. Sounds like this is the kernel of our kernel. Solr already has a lot of functionality to allow for this. Do we want a couple of plugins, one for solr and one for OAI? Or do we want an app that handles both?

Lots of little data silos aren't going to work, we need everything in a local catalog. But that doesn't mean we should all try to be google. We still need well-defined collection development policies.

What about social data? SoPAC is neat, and has an independent layer for saving social data.

We also talked about Blacklight and the ways it brings in various data sources and handles behavior for different kinds of objects, e.g., [http://musicbrainz.org/ MusicBrainz] data for music items.

(interested in further development: Bob, Dennis, Peter, Naomi, Bess)

=== solr marc ===

Q: How well is solr marc handling bad data these days?

Bob: I've been adding to marc4j more permissive reading and error correction. It's also reporting errors as it finds them, to make it easier to find bad records. Request for writing to log files instead of standard out. How to handle records with bad leaders? Naomi has some marc test data. We need more test driven development.

Naomi is offering code for parsing OCLC numbers and LC numbers, she'll be working with Bob next week to get that into solrmarc.

Chris from Villanova is going to do some graphic design work for solr marc. Yay!

(Interested in further development: Bob, Naomi, Chris, Bess)

=== Authority control ===

Can we get the LC authority control data, index it locally, and take advantage of that in our searching. Actually getting the authority index data is the problem. It's government monitored data, so why can't we get access to it? We can get snapshots, but there's no method for harvesting it. We need some way to get weekly / monthly updates of authority data. EdSu might have set something up, but it isn't an official service.

Eric says go ahead and implement something, and don't worry about the update method right now. Can we get authority data? Does Open Library have any authority data? Bess will look into this.

"Fred Data" <-- subject authorities

Consensus seems to be that we need a proof of concept first, see how well that scales, and then after that start lobbying LC / OCLC / Palinet / other vendors.

(Interested in further development: Ya'aqov, Daniel, Mark, Bess)

=== Dedupping / FRBR ===

We need to look at Trish Williams' work with hierarchical solr records for implementing FRBR. If we start working with this maybe we can advocate for getting this into the solr trunk.

Do we really need FRBR or will "other editions" do the trick? xISBN and xISSN does a pretty good job from OCLC, and can be implemented in just a few lines of code. No one understands FRBR anyway.

One user group that could really use FRBR is musicians, to tie together recordings and scores. The Variations project at Indiana is working with this. OCLC also made public their algorithm for FRBRizing work. Some libraries have a problem stemming from having digitized versions of an item, and then the digital version has a catalog entry, but then in your VuFind system you index both the digital surrogate and the catalog record about the digital surrogate. You probably want to combine these or suppress

Open Library is also very interested in de-duping research.

=== Serials holdings ===

Marc format for holdings data (MFHD)
xISSN service might be helpful for this, too
Bibliographic records for serials should refer to each other.

How to represent this data for users? There's a summary holdings field, a one-line display, and then there's a detailed holding display. There can be multiple screens of lines with this. Summary holdings are pretty easy, detail holdings are hard. Are they necessary?

Maybe we can handle this the way we're doing "composition era" in blacklight? If we know the range, we can assign values for all possible values of this range.

You can get an extract of all serial holdings from your Open URL database (SFX), harvest your journal holdings through that. Texas A&M is doing this w/ SFX. This seems like an efficient way of getting detailed holdings. Indexing this might be helpful if you don't have marc records for all of your electronic holdings, and it also might help for knowing when you have full text online and when you don't.

(interested in further development: Ya'aqov, Mark)

=== Federated Search / article content ===

Can we partner with LibraryFind? Or should we implement an engine like pazpar2?
IndexData has something called pazpar2, which is a federated search engine.

(Interested in further development: one guy, whose name I didn't catch. Please self identify!)

=== back-end arch / OSS methods ===

We never really discussed this, but Peter and Peter said they were interested in following up on this topic.

=== kernelizing the projects ===

- solrmarc
- solroai
- authority data & merging

=== How do we organize - How do we reach out to libraries and formalize a committment? ===
John, Dennis, Joe, Andrew, Mark, Daniel

[[Category: Meeting agendas]]