Hi Karen,

Absolutely, the function to get the work id is designed to take any
key/value to pass to the query API exactly for this purpose.  We only have
a public function for ISBNs right now, because that's the only use case we
have currently for the project I wrote this for.

But, yeah, it would be trivial to either add explicit functions for LCCN,
OCLC number, etc. or a very general "getEditionsByKeyValue" where you
specify what you want manually.  We will probably eventually have a need to
do this on other kinds of identifiers, as well, at some point.

The reason that we didn't do that with ISBNs, is that because there is a
mix of ISBN10s and ISBN13s in OL, we needed to parse the ISBN and search
for both, so some preprocessing was required.

Also, obviously this client could use some documentation... :)  I'll get on
that next week.

-Ross.


On Sat, Mar 9, 2013 at 11:19 AM, Karen Coyle <[email protected]> wrote:

> Great, Ross. Would there be a use case to have a similar program that
> takes a different identifier as input, e.g. LCCN? I'm thinking about how
> one might reach those books that never had an ISBN....
>
> kc
>
> On 3/8/13 7:06 PM, Ross Singer wrote:
> > Since we're announcing things :)
> >
> > I've also made a node.js client for the 'editions' service, based on
> > xISBN. [*]
> >
> > Basically, you give it an ISBN and it gives you the editions associated
> > with the relevant work(s).
> >
> > -Ross.
> > * https://github.com/talis/node-openlibrary-editions
> >
> > On Friday, March 8, 2013, John Shutt wrote:
> >
> >     Hey y'all,
> >
> >     Over the past week, Jay Fajardo and I have been doing a lot of work
> >     on the openlibrary gem <https://github.com/jayfajardo/openlibrary>.
> >     We've added a shiny new client for the REST API
> >     <http://openlibrary.org/dev/docs/restful_api>, which can:
> >
> >     * Find books and authors by their OLIDs
> >     * Get the revision history of any object
> >     * Get an array of recent changes to Open Library
> >     * Create Ruby pseudo-objects to easily grab OL object data
> >     * Log in to Open Library programmatically
> >
> >     There's still more to add, like broader support for the Query API,
> >     but we're near the point where people can write advanced crawlers
> >     and bots in Ruby. If any of your friends and loved ones are Rubyists
> >     and want to contribute to Open Library, point them toward this
> project!
> >
> >     Speaking of bots, how does one become a member of the API usergroup
> >     <http://openlibrary.org/usergroup/api>? Does the bot have to be
> >     written and get its code vetted before it can make PUT requests?
> >
> >     John Shutt
> >
> >
> >
> > _______________________________________________
> > Ol-tech mailing list
> > [email protected]
> > http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech
> > To unsubscribe from this mailing list, send email to
> [email protected]
> >
>
> --
> Karen Coyle
> [email protected] http://kcoyle.net
> ph: 1-510-540-7596
> m: 1-510-435-8234
> skype: kcoylenet
> _______________________________________________
> Ol-tech mailing list
> [email protected]
> http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech
> To unsubscribe from this mailing list, send email to
> [email protected]
>
_______________________________________________
Ol-tech mailing list
[email protected]
http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech
To unsubscribe from this mailing list, send email to 
[email protected]

Reply via email to