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  March 2008

CODE4LIB March 2008

Subject:

more musing/clarification on oca apiRe: [CODE4LIB] oca api?

From:

Tim Shearer <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 7 Mar 2008 15:50:47 -0500

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (284 lines)

> Tim,
>
> It sounds like you want to be able to search on standard identifiers and
> are frustrated that the Internet Archive's access doesn't allow it
> (although it looks like they do have an ISBN search)? And I'm curious,
> why would you want or need to pull down only records that have OCLC
> numbers of ISBNs in particular? What is it you need to do that makes
> only those records useful?

Because I have no imagination?  :)

Levels of engagement with OCA:

We're a scanning participant (as are y'all).  There are three levels of
opac engagement I can think of:

*Link to your digitized materials.

*Link to all materials that have been digitized that you have already
selected for your collection.

*Link to all materials that have been digitized.

The catalog:

Sure it's outdated and hopelessly linked to dead tree resources.  But a
significant number of my patrons still use it.  Faceted browsing only
encourages them.  Will it go away?  Probably.  Will there be a whole lot
of people who use it to their benefit until it goes away?  Probably.  In
the mean time I'd just as soon let them have direct access to a digital
copy for those who want it and discover it in our opac.

What I want to do:

I'm aiming for the second level of engagement.  We've got to do the first
for obvious reasons.

I think the third level is a nice idea.  But it's going to involve:

*The Library having a discussion about what that means for our catalog.
*Importing full records.  Based on what I've seen these records will
        need to be massaged somewhat (not the least of which is to put an
        856 into the participant provided marc records, and/or provide all
        the opac useful data from those provided records into what the oca
        stores and makes accessible via some soon to come API).

Both of these will take some time and significant effort.  I'm hoping, as
well, that all this work can happen at a much higher level.  OCA/Open
Library + OCLC work out some arrangement or something.  Then any library
can download an "oca collection."  I hope something like this kind of
upper level coordination happens, so that tens/hundreds of libraries
aren't out there trying to solve the "how do I put them all in my catalog"
issue and duplicating effort.

Why do the second level:

I think it will be good and timely bang for the buck.  I'm estimating that
a fairly modest development investment can get me (and others) there
quickly and without having to do much navel gazing about the nature of
collection development/role of the catalog.

Caveat: I'm coming at this from a "what's available at oca, do I have it?"
rather than an "I've got it, does oca have it?" perspective.

Development involves finding a way to connect oca unique ids to
matchpoints in our catalog (that would be the oclc numbers, lc numbers,
issns, isbns).  Searching those matchpoints in our catalog.  Adding an 856
for matches.  Lather, rinse, repeat (as their collection grows).

Will that offer perfect coverage in the catalog:

Nope.  There is a whole lot of fuzz in these "unique identifiers."  I
still think there's be a huge bang for the buck, though.

Why the desire for all the unique ids:

Because my experience with the catalog says that checking as many as
possible will get me the greatest recall and looking up a few doesn't cost
too much more than looking up one.  More match points, more likely to get
best coverage.

Why not add an xISBN hook:

Trying for speedy development/lazy/hoping someone else would.

How long would such a service be useful:

No idea.  But if five academic libraries could use it for 18 months, that
would probably be a pretty decent roi.

I emailed the list because I'm lazy and wanted feedback.

If someone else if offering this (soonish), I'd just as soon piggy back.
If there's a decent proxy for what I'd like (say, that third level gets
        worked out in 3 months), I'd just as soon wait.
If I do do it, laziness leaves me wanting to prove that my investment
        wasn't wasted effort.  I.e. I do it the "best" way for the most
        people (with the caveat that laziness may trump laziness should
        feature creep get the best of things).

My questions remain (I guess):

Anyone know of something coming that will do what I want or be a good
enough proxy to avoid this? (nothing clear so far)

If not, would you like to have something like I describe? (some "yes")

Would having these features be enough?
    search that enables combinations of:
        oca unique id
        oclc number
        isbn
        issn
        lc number
        participant's unique database number (e.g. iii bnum)
        participant's alias (<scanningcenter>chapelhill</scanningcenter>)
        addeddate (so you can get new stuff)

    returns: oca identifier, other unique id(s)

And, if such a service were available:
    How would you like it?  I've not built a queryable webservice and am
        going on record as ignorant.  Is there a query language I should
        lean toward?  A return data structure that I should adopt?


All this stems from the my belief that what I can see of the architecture
indicates a split between what the participating library sends and what
the oca system uses.  It appears that their index/record of record simply
ignores all those hooks people have been adding to bib records.  If both
parts were wrapped and offered up with a Solr interface I could get on
with putting links into my catalog.

Still, they make both their record (with their identifier) available, and
my record (with the rest) available.  So, like I said in an earlier post,
I'm glad for the opportunity to be frustrated.

Whew.  If I'd been hacking instead of writing I'd have something to show
and y'all would be less bored.

Thanks!
-t


> Like Karen and Bess and others have said, I recommend that you
> coordinate this with the Open Library project. At the meeting last
> Friday, it did sound like they would be interested in providing
> identifier disambiguation types of service - give them an ISBN, and
> they'll give you the records associated with it.
>
> Also, there was discussion about building an Open Librar yAPI (to enable
> some cool integration with wikipedia), and I suggested a that libraries
> using an API would want the search results to include information about
> whether the title has a digitized copy. So I would hope the service that
> you're envisioning is something that would be provided by an Open
> Library API (but we don't know when that might come about).
>
> As OCA moves forward, folks may well be digitizing identical books. So
> there may not be a one to one relationship between unique catalog
> identifier, unique oca identifier, and isbn/lccn/oclc number.
>
> -emily
>
>
>> ----------------------------------------------------------------------
>>
>> Date:    Thu, 6 Mar 2008 08:47:04 -0500
>> From:    Tim Shearer <[log in to unmask]>
>> Subject: musing on oca apiRe: [CODE4LIB] oca api?
>>
>> Howdy folks,
>>
>> I've been playing and thinking.  I'd like to have what amounts to a unique
>> identifier index to oca digitized texts.  I want to be able to pull all the
>> records that have oclc numbers, issns, isbns, etc.  I want it to be
>> lightweight, fast, searchable.
>>
>> Would anyone else want/use such a thing?
>>
>> I'm thinking about building something like this.
>>
>> If I do, it would be ideal if wouldn't be a duplication of effort, so
>> anyone
>> got this in the works?  And if it would meet the needs of others.
>>
>> My basic notion is to crawl the site (starting with "americana", the
>> American
>> Libraries.  Pull the oca unique identifier (e.g. northcarolinayea1910rale)
>> and
>> associate it with
>>
>> unique identifiers (oclc numbers, issns, isbns, lc numbers)
>> contributing institution's alias and unique catalog identifier
>> upload date
>>
>> That's all I was thinking of.  Then there's what you might be able to do
>> with
>> it:
>>
>>         Give me all the oca unique identifiers that have oclc numbers
>>         Give me all the oca unique identifiers with isbns that were
>>                 uploaded between x and y date
>>         Give me the oca unique identifier for this oclc number
>>
>> Planning to do:
>>
>>         keep crawling it and keep it up to date.
>>
>> Things I wasn't planning to do:
>>
>>         worry about other unique ids (you'd have to go to xISBN or
>>                 ThingISBN yourself)
>>         worry about storing anything else from oca.
>>
>> It would be good for being able to add an 856 to matches in your catalog.
>> It
>> would not be good for grabbing all marc records for all of oca.
>>
>> Anyhow, is this duplication of effort?  Would you like something like this?
>> What else would you like it to do (keeping in mind this is an unfunded pet
>> project)?  How would you want to talk to it?  I was thinking of a web
>> service,
>> but hadn't thought too much about how to query it or how I'd deliver
>> results.
>>
>> Of course I'm being an idiot and trying out new tools at the same time
>> (python
>> to see what the buzz is all about, sqlite just to learn it (it may not work
>> out)).
>>
>> Thoughts?  Vicious criticism?
>>
>> -t
>>
>>
>> ------------------------------
>>
>> Date:    Thu, 6 Mar 2008 11:05:41 -0500
>> From:    Jodi Schneider <[log in to unmask]>
>> Subject: Re: musing on oca apiRe: [CODE4LIB] oca api?
>>
>> Great idea, Tim!
>>
>> The open library tech list that Bess mentions is [log in to unmask],
>> described at
>> http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech
>>
>> -Jodi
>>
>> Jodi Schneider
>> Science Library Specialist
>> Amherst College
>> 413-542-2076
>>
>>
>
>> ------------------------------
>>
>> Date:    Thu, 6 Mar 2008 08:32:43 -0800
>> From:    Karen Coyle <[log in to unmask]>
>> Subject: Re: musing on oca apiRe: [CODE4LIB] oca api?
>>
>> We talked about something like this at the Open Library meeting last
>> Friday. The ol list is [log in to unmask] (join at
>> http://mail.archive.org/cgi-bin/mailman/listinfo/ol-lib). I think of
>> this as a (or one or more) translate service between IDs. It's a
>> realization that we will never have a unique ID that everyone agrees on,
>> that most bibliographic items are really more than one thing, but that
>> since we have data about the bibliographic item we have many
>> opportunities to make connections even though people have used different
>> identifiers. So we could use an "ID-switcher" to move among data stores
>> and services. Is that the kind of thing you are thinking of?
>>
>> kc
>>
>>
>>
> --
> Emily Lynema
> Systems Librarian for Digital Projects
> Information Technology, NCSU Libraries
> 919-513-8031
> [log in to unmask]
>

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

May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
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