LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  June 2011

CODE4LIB June 2011

Subject:

Re: JHU integration of PD works

From:

Jonathan Rochkind <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 15 Jun 2011 12:07:27 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (82 lines)

On 6/15/2011 9:31 AM, Eric Hellman wrote:
> Clearly, Jonathan has gone through the process of getting his library to think through the integration, and it seems to work.

Thank you!

> Has there been any opposition?

Not opposition exactly, but it doesn't work perfectly, and people are 
unhappy when it doesn't work. It can sometimes find the _wrong_ match on 
a 'foreign' site like Amazon etc.  Or avoid finding a right one of course.

Or the definition of right/wrong can be not entirely clear too -- on a 
bib record for a video of an opera performed, is it right or wrong to 
supply a link to the print version of the opera? What if the software 
isn't smart enough to _tell_ you it's an alternate format (it's not), 
and the link is just in the single flat list of links?

Also issues with avoiding duplicate double URLs when things are in bib 
records AND in SFX kb AND maybe looked for otherwise by Umlaut. (we have 
_some_ HathiTrust URLs in our bib records, that came that way from OCLC, 
who knew?)

These things get really complicated, quickly.  I am constantly finding 
time to do more tweaking, but it'll never be perfect, so people have to 
get used to lack of perfection. Still when I ask, okay, this 
HathiTrust/Amazon/Google linking feature is not going to be perfect, 
would you rather keep it with imperfections we may not be able to fix, 
or eliminate it -- nobody says eliminate.

> What are the reasons that this sort of integration not more widespread? Are they technical or institutional? What can be done by producers of open access content to make this work better and easier? Are "unified" approaches being touted by vendors delivering something really different?

I think they are mostly technical.  This stuff is _hard_, because of the 
(lack of) quality of our own metadata, the lack of quality of third 
party metadata, the lack of sufficient APIs and Services, and the lack 
of a local technical infrastructure to support tying everythign together.

So on the one hand, I'm trying to find time for an overhaul of Umlaut to 
make it easier for people to install and maintain, and I'm hoping I can 
get some more adoption at that point.  To at least provide some open 
source "local technical infrastructure". Umlaut is intentionally 
designed to be as easy as possible to integrate with your existing 
catalog or other service points, as well as to provide 'just in time' 
services from third party external searches -- that's it's mission, this 
kind of just-in-time service. ("easy as possible" -- or as easy as I can 
make it, which sometimes still isn't easy enough, especially if you 
don't have local technical resources).

But still, it's metadata, metadata, metadata.  So what can producers of 
open access content do to make this work better and easier?

1) Have good metadata for their content, especially including as many 
identifiers as possible -- ISBN, OCLCnum, LCCN.   Even if you aren't an 
OCLC member and don't have an "OCLC record", if you can figure out what 
OCLC record represents this thing you've got, list it in the metadata.  
Even if the ISBN/OCLCnum/LCCN doesn't represent the _exact_ same thing, 
list it -- ideally somehow identified as 'an alternate manifestation'.  
Also have author, title, publisher, publication year  metadata.  If you 
can have author metadata as an NAF/VIAF controlled form or identifier, 
even better.  Metadata is expensive, but metadata is valuable, the 
better it is, the better Umlaut's approach can work.

Share the metadata publically, in case someone wants to do something 
with it.

2) Provide an API that allows lookup of your open access content, 
searching against the good metadata from #1. Including identifier 
searches.  The thing is, each of (dozens, hundreds, thousands) of open 
access content providers having such an API --- it's a burdensome 
expense for each of them, but it's also unrealistic for client software 
to talk to dozens/hundreds/thousands of APIs.

So this stuff needs to be aggregated in fewer major service points.  It 
could be an aggregator of just metadata that links to content hosted on 
individual hosts, or it could be an aggregator of content itself. Either 
way, it needs a good API based on good metadata. "Google" doesn't work 
as such an aggregator, the APIs it has are too limited functionally and 
by ToS, and the results do not have sufficient metadata.  Maybe the 
Internet Archive does -- although IA's API's and metadata are sometimes 
a bit sketchy (If you do put it in IA, make sure it somehow shows in the 
"Open Library" section and it's APIs -- the OL API's IA has are 
sufficient for Umlaut's use, but general Internet Archive APIs are 
not).  Or maybe a new aggregator(s) have to be collectively created.

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager