Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] Matching print and electronic editions of the same book)

2015-12-14 Thread Richard Wallis 
@Sara:
You can lookup using OCLCNumber based and ISBN based URIs.  Note I am not
using the word ’search’.  You are not searching an index for references to
a number string, you asking for a description of the thing with identifier ‘
http://worldcat.org/oclc/##’.  May seem a little pedantic, but it is
fundamental to linked data.

As far as I am aware there is no direct access to lccn via this route. That
*would* be more of a search operation: ‘return me the Thing(s), and their
unique URI(s), that are sameAs the thing this identified by this’ lccn.

@Cindy:
All this data is openly available, as Linked Data under an Open Data
Commons Attribution License ,
in the way I described so you do not need an account key, or an API to
access it.

OCLC have APIs that also makes some of this data available via other
routes.  I will leave it to folks at OCLC to comment on those and any
limits, or not, associated with the Linked Data.

~Richard.

Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Linkedin: http://www.linkedin.com/in/richardwallis
Twitter: @rjw

On 14 December 2015 at 15:11, Harper, Cynthia  wrote:

> My question - is there a limit of number of requests, or request rate?  Is
> this done with an account key?
>
> Thanks,
> Cindy Harper
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> sara amato
> Sent: Monday, December 14, 2015 9:57 AM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re:
> [CODE4LIB] Matching print and electronic editions of the same book)
>
> One last question on this - I see that I can search
> worldcat.org/oclc/##  and worldcat.org/isbn/#- is there any
> way to search the lccn?
>
>
>
> > On Dec 12, 2015, at 3:52 PM, Richard Wallis <
> richard.wal...@dataliberate.com >
> wrote:
> >
> > Sara,
> >
> > The canonical URI you are looking for is
> http://worldcat.org/oclc/8410511  <
> http://worldcat.org/oclc/8410511 >
> which silently redirects [via a http 303] to where the data is currently
> stored (experiment.worldcat.org  <
> http://experiment.worldcat.org/ >).
> This approach enables the canonical WorldCat identifiers to be maintained
> over time in a fixed namespace, whilst providing flexibility as to where
> the actual data is stored.
> >
> > You can use http content-negotiation to get the serialisation [html,
> rdfxml, triples, turtle] that you require, or as an option you can suffix
> the url with .jsonld etc.  - See my blogpost <
> http://dataliberate.com/2013/06/content-negotiation-for-worldcat/ <
> http://dataliberate.com/2013/06/content-negotiation-for-worldcat/>> for a
> longer explanation.
> >
> > The same pattern occurs when you follow the exampleOfWork triple to get
> the work id.  The data references the canonical
> http://worldcat.org/entity/work/id/3357516 <
> http://worldcat.org/entity/work/id/3357516> <
> http://worldcat.org/entity/work/id/3357516 <
> http://worldcat.org/entity/work/id/3357516>> URI.  Accessing that
> redirects, via a http 303, to the description of that resource at
> http://experiment.worldcat.org/entity/work/data/3357516 <
> http://experiment.worldcat.org/entity/work/data/3357516> <
> http://experiment.worldcat.org/entity/work/data/3357516 <
> http://experiment.worldcat.org/entity/work/data/3357516>>.
> >
> > The moral of this is always use the canonical URIs to look things up.
> >
> > You ask if ‘experiment.worldcat.org  <
> http://experiment.worldcat.org/ >’ is
> going to be around for a while.  From the above you can infer that it is
> the wrong question to ask.WorldCat itself maintains the canonical URIs,
> for Works, OCLCNUMS, and other entities.  By using those in your code, you
> will be protected against any architectural and or system changes behind
> the scenes.
> >
> > Then, as Terry suggests, following the relationships in the Linked Data
> is the way to achieve many of the same ends as using xID.
> >
> > ie. Using an OCLCNUM, generate the URI of the associated WorldCat entity
> ‘http://worldcat.org/oclc/x  <
> http://worldcat.org/oclc/x >'.  From
> that entity description extract the schema:exampleOfWork triple. Use the
> URI from that to obtain the Work URI.  Obtain the description of the Work
> from that URI and the extract the values of the contained
> schema:workExample triples.
> >
> > ~Richard.
> >
> >
> >
> > Richard Wallis
> > Founder, Data Liberate
> > http://dataliberate.com 
> > >
> > Linkedin: http://www.linkedin.com/in/richardwallis
> >

Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] Matching print and electronic editions of the same book)

2015-12-12 Thread Richard Wallis 
Sara,

The canonical URI you are looking for is http://worldcat.org/oclc/8410511
which silently redirects [via a http 303] to where the data is currently
stored (experiment.worldcat.org).  This approach enables the canonical
WorldCat identifiers to be maintained over time in a fixed namespace,
whilst providing flexibility as to where the actual data is stored.

You can use http content-negotiation to get the serialisation [html,
rdfxml, triples, turtle] that you require, or as an option you can suffix
the url with .jsonld etc.  - See my blogpost
 for a
longer explanation.

The same pattern occurs when you follow the exampleOfWork triple to get the
work id.  The data references the canonical
http://worldcat.org/entity/work/id/3357516 URI. Accessing that redirects,
via a http 303, to the description of that resource at
http://experiment.worldcat.org/entity/work/data/3357516.

The moral of this is always *use the canonical URIs to look things up*.

You ask if ‘experiment.worldcat.org’ is going to be around for a while.
>From the above you can infer that it is the wrong question to ask. WorldCat
itself maintains the canonical URIs, for Works, OCLCNUMS, and other
entities. By using those in your code, you will be protected against any
architectural and or system changes behind the scenes.

Then, as Terry suggests, following the relationships in the Linked Data is
the way to achieve many of the same ends as using xID.

ie. Using an OCLCNUM, generate the URI of the associated WorldCat entity ‘
http://worldcat.org/oclc/x'.  From that entity description extract the
schema:exampleOfWork triple. Use the URI from that to obtain the Work URI.
Obtain the description of the Work from that URI and the extract the values
of the contained schema:workExample triples.

~Richard.



Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Linkedin: http://www.linkedin.com/in/richardwallis
Twitter: @rjw

On 12 December 2015 at 22:47, Sara Amato  wrote:

> In thinking about using worldcat.org as a bridge to a works record, I'm
> wondering about using 'experiment.worldcat.org', e.g.
> http://experiment.worldcat.org/oclc/841051199.jsonld as an easy way to get
> the work id. I'm having trouble finding out any info about exactly what
> 'experiment.worldcat.org' is.   Is it likely to be around for a while?  Is
> it up to date and just reformatting the www.worldcat.org data???  Anybody
> know?
>
>
>
>
> On Fri, Dec 11, 2015 at 2:17 PM, Terry Reese  wrote:
>
> > I think the best replacement at this point as a single API is to look at
> > Librarythings api though I'm not sure if it would work in all cases --
> > otherwise, I think using worldcat.org as a bridge to their works records
> > probably is your best bet.
> >
> > --tr
> >
> > -Original Message-
> > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> > Brian Riley
> > Sent: Friday, December 11, 2015 5:14 PM
> > To: CODE4LIB@LISTSERV.ND.EDU
> > Subject: Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re:
> > [CODE4LIB]
> > Matching print and electronic editions of the same book)
> >
> > Does anyone know if OCLC is recommending an alternate solution that will
> > provide the same or at least similar functionality?
> >
> > I had played around with the Worldcat Discovery API when it was in beta
> but
> > am not sure of its present status or if its the most logical replacement
> > for
> > xID.
> >
> >Brian
> >
> > 
> > From: Code for Libraries  on behalf of Eric
> > Hellman 
> > Sent: Friday, December 11, 2015 1:31 PM
> > To: CODE4LIB@LISTSERV.ND.EDU
> > Subject: Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re:
> > [CODE4LIB]
> > Matching print and electronic editions of the same book)
> >
> > Users of xID services would be wise to check the termination clauses of
> > their usage agreements to see whether they are permitted to keep and
> reuse
> > the data they have cached.
> >
> > Think about it. The world outside of 43017 has invented all sorts of new
> > techniques to update and maintain metadata cooperatively.
> >
> > Eric
> >
> >
> >
> > Eric Hellman
> > President, Free Ebook Foundation
> > Founder, Unglue.it https://unglue.it/
> > https://go-to-hellman.blogspot.com/
> > twitter: @gluejar
> >
>

Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] Matching print and electronic editions of the same book)

2015-12-12 Thread Sara Amato 
In thinking about using worldcat.org as a bridge to a works record, I'm
wondering about using 'experiment.worldcat.org', e.g.
http://experiment.worldcat.org/oclc/841051199.jsonld as an easy way to get
the work id. I'm having trouble finding out any info about exactly what
'experiment.worldcat.org' is.   Is it likely to be around for a while?  Is
it up to date and just reformatting the www.worldcat.org data???  Anybody
know?




On Fri, Dec 11, 2015 at 2:17 PM, Terry Reese  wrote:

> I think the best replacement at this point as a single API is to look at
> Librarythings api though I'm not sure if it would work in all cases --
> otherwise, I think using worldcat.org as a bridge to their works records
> probably is your best bet.
>
> --tr
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Brian Riley
> Sent: Friday, December 11, 2015 5:14 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re:
> [CODE4LIB]
> Matching print and electronic editions of the same book)
>
> Does anyone know if OCLC is recommending an alternate solution that will
> provide the same or at least similar functionality?
>
> I had played around with the Worldcat Discovery API when it was in beta but
> am not sure of its present status or if its the most logical replacement
> for
> xID.
>
>Brian
>
> 
> From: Code for Libraries  on behalf of Eric
> Hellman 
> Sent: Friday, December 11, 2015 1:31 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re:
> [CODE4LIB]
> Matching print and electronic editions of the same book)
>
> Users of xID services would be wise to check the termination clauses of
> their usage agreements to see whether they are permitted to keep and reuse
> the data they have cached.
>
> Think about it. The world outside of 43017 has invented all sorts of new
> techniques to update and maintain metadata cooperatively.
>
> Eric
>
>
>
> Eric Hellman
> President, Free Ebook Foundation
> Founder, Unglue.it https://unglue.it/
> https://go-to-hellman.blogspot.com/
> twitter: @gluejar
>

[CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] Matching print and electronic editions of the same book)

2015-12-11 Thread William Denton 

Rachel's message evidently prompted this:

http://www.oclc.org/developer/news/2015/change-to-xid-services.en.html

"OCLC offers an array of APIs that provide additional access points to WorldCat 
and the WorldShare platform, allowing libraries and partners to use the data 
inside applications in new and creative ways.  While we add APIs at times, we 
also must retire some.  The xID product, including xISBN, xISSN and xOCLCNum, 
has experience low usage and will be retired from the OCLC API offering. No new 
keys are being issued, and the service will be unavailable beginning March 15, 
2016."


OCLC people:  how about releasing the data behind the xID services?  A big 
static dump of all of the numbers (ISBN, LCCN, OCLCnum) and how they're related. 
It'll be out of date the next day, but it'll still be very, very useful.


When you needed them, the xID services were EXTREMELY helpful.  Perhaps part of 
the cause of low usage was the access restrictions, both of number of requests 
and commercial use.  If the data had been open, many more uses would have 
arisen.  I say make it open now, under something like an Open Data Commons 
Attribution License.


Bill


On 10 December 2015, Maderik, Rachel A wrote:


Just a warning about OCLC's xID API: a few weeks ago I requested an access 
token to bypass the rate limit, and was told that they are no longer giving 
these out. I was also told that the data in xID has not been updated for some 
time (I don't know when they stopped, but I think the rep told me it was at 
least a year out of date). It was very disappointing to learn this; if the 
project is essentially dead, this fact should be advertised (at the very least, 
they should take down the pricing list!).


-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of William 
Denton
Sent: Wednesday, December 09, 2015 5:40 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Matching print and electronic editions of the same book

Thanks!  That opens things up.  We do have a lot of OCLC numbers.  For my 
example book, there's an 035 with three of them, including 841051199. If I look 
at

http://worldcat.org/oclc/841051199

it takes me to the human-readable page, but

http://worldcat.org/oclc/841051199.rdf

shows it all in RDF, and I can see a lot of things like

http://experiment.worldcat.org/entity/work/data/1613596711#Place/japan;>

so I can pick out the work ID and look it up.  (Perhaps the work ID be 
specified directly there?)

So that would work, but aha, I just noticed I could make it a little simpler by 
using xOCLCNUM to get the work ID, which is the owi field here:

http://xisbn.worldcat.org/webservices/xid/oclcnum/841051199?method=getMetadata=json=*

And then I can go to

http://experiment.worldcat.org/entity/work/data/1613596711.rdf

and get all the workExample links, and use those OCLC numbers.

(Which I'm sure you knew, Roy, but perhaps didn't mention because of the 
rate-limiting, but as far as I know our subscription means I can get an access 
token so I can do some larger queries.)

A first run of something like this would take a while to process everything, 
but I'd store locally what I need to know, and then incremental updates for a 
month's worth of news ebooks wouldn't take long.  Thanks!

Bill

On 9 December 2015, Roy Tennant wrote:


Do you have an OCLC number in your records? If so, you could call it
at WorldCat like this:

http://worldcat.org/oclc/XXX

scrape the structured linked data on the page, looking for the
"Example of Work" link, then follow it to the Work Record:

http://experiment.worldcat.org/entity/work/data/1613596711

That then will give you all of the OCLC numbers that we consider are
part of that work (under the "WorkExample" tab).

I know, not an optimal solution even if you have the OCLC number. But
it could work if you do.
Roy

On Wed, Dec 9, 2015 at 1:37 PM, William Denton  wrote:


I'm looking at how to match print (p) and electronic (e) editions of
the same book in our collection.  There is no connection between them
in our system (VuFind in front of Symphony).

For example, two catalogue entries for two versions of COMPOSING
JAPANESE MUSICAL MODERNITY, entirely separate:

+ https://www.library.yorku.ca/find/Record/3238132
+ https://www.library.yorku.ca/find/Record/3311584

I want know they're the same book so I can do more usage and
collection analysis.  I've been looking at two ways of doing it with
data available right now:

1 a) MARC 020 (ISBN) can list multiple ISBNs. We have e books where
the p editions are listed.

1 b) MARC 776 (additional physical form entry) for e books can list a
p ISBN or other control number. If we have that edition, great. If
not, need to go from e -> p-we-don't-have -> p-we-do-have, which I
could do with xISBN.

2) OCLC's xISBN. When it reports other editions of the same work, it
can include e versions.

There is also:

3) Vendors supplying data.  For example, YBP

Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] Matching print and electronic editions of the same book)

2015-12-11 Thread Fleming, Jason 
As a heavy user of the xID service I would look forward to a discussion about 
what alternatives there might be. 

Thank you Bill for the link t to that announcement.


-Jason

Jason Fleming
Information Technology Librarian
 
601 South College Road | Wilmington, NC  28403-5990
T: 910-962-2675 | flemi...@uncw.edu
http://library.uncw.edu



-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of William 
Denton
Sent: Friday, December 11, 2015 11:44 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] 
Matching print and electronic editions of the same book)

Rachel's message evidently prompted this:

http://www.oclc.org/developer/news/2015/change-to-xid-services.en.html

"OCLC offers an array of APIs that provide additional access points to WorldCat 
and the WorldShare platform, allowing libraries and partners to use the data 
inside applications in new and creative ways.  While we add APIs at times, we 
also must retire some.  The xID product, including xISBN, xISSN and xOCLCNum, 
has experience low usage and will be retired from the OCLC API offering. No new 
keys are being issued, and the service will be unavailable beginning March 15, 
2016."

OCLC people:  how about releasing the data behind the xID services?  A big 
static dump of all of the numbers (ISBN, LCCN, OCLCnum) and how they're 
related. 
It'll be out of date the next day, but it'll still be very, very useful.

When you needed them, the xID services were EXTREMELY helpful.  Perhaps part of 
the cause of low usage was the access restrictions, both of number of requests 
and commercial use.  If the data had been open, many more uses would have 
arisen.  I say make it open now, under something like an Open Data Commons 
Attribution License.

Bill


On 10 December 2015, Maderik, Rachel A wrote:

> Just a warning about OCLC's xID API: a few weeks ago I requested an access 
> token to bypass the rate limit, and was told that they are no longer giving 
> these out. I was also told that the data in xID has not been updated for some 
> time (I don't know when they stopped, but I think the rep told me it was at 
> least a year out of date). It was very disappointing to learn this; if the 
> project is essentially dead, this fact should be advertised (at the very 
> least, they should take down the pricing list!).
>
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf 
> Of William Denton
> Sent: Wednesday, December 09, 2015 5:40 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Matching print and electronic editions of the 
> same book
>
> Thanks!  That opens things up.  We do have a lot of OCLC numbers.  For 
> my example book, there's an 035 with three of them, including 
> 841051199. If I look at
>
> http://worldcat.org/oclc/841051199
>
> it takes me to the human-readable page, but
>
> http://worldcat.org/oclc/841051199.rdf
>
> shows it all in RDF, and I can see a lot of things like
>
>  rdf:about="http://experiment.worldcat.org/entity/work/data/1613596711#
> Place/japan">
>
> so I can pick out the work ID and look it up.  (Perhaps the work ID be 
> specified directly there?)
>
> So that would work, but aha, I just noticed I could make it a little simpler 
> by using xOCLCNUM to get the work ID, which is the owi field here:
>
> http://xisbn.worldcat.org/webservices/xid/oclcnum/841051199?method=get
> Metadata=json=*
>
> And then I can go to
>
> http://experiment.worldcat.org/entity/work/data/1613596711.rdf
>
> and get all the workExample links, and use those OCLC numbers.
>
> (Which I'm sure you knew, Roy, but perhaps didn't mention because of 
> the rate-limiting, but as far as I know our subscription means I can 
> get an access token so I can do some larger queries.)
>
> A first run of something like this would take a while to process everything, 
> but I'd store locally what I need to know, and then incremental updates for a 
> month's worth of news ebooks wouldn't take long.  Thanks!
>
> Bill
>
> On 9 December 2015, Roy Tennant wrote:
>
>> Do you have an OCLC number in your records? If so, you could call it 
>> at WorldCat like this:
>>
>> http://worldcat.org/oclc/XXX
>>
>> scrape the structured linked data on the page, looking for the 
>> "Example of Work" link, then follow it to the Work Record:
>>
>> http://experiment.worldcat.org/entity/work/data/1613596711
>>
>> That then will give you all of the OCLC numbers that we consider are 
>> part of that work (under the "WorkExample" tab).
>>
>> I know, not an optimal solution even if you have the OCLC number. But 
>> it could work if you do.
>> Roy
>>
>> On Wed, Dec 9, 2015 at 1:37 PM, William Denton  wrote:
>>
>>> I'm looking at how to match print (p) and electronic (e) editions of 
>>> the same book in our collection.  There is no connection between 
>>> them in our system (VuFind in front of Symphony).
>>>
>>> For example,

Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] Matching print and electronic editions of the same book)

2015-12-11 Thread Brian Riley 
Does anyone know if OCLC is recommending an alternate solution that will 
provide the same or at least similar functionality? 

I had played around with the Worldcat Discovery API when it was in beta but am 
not sure of its present status or if its the most logical replacement for xID.

   Brian 


From: Code for Libraries  on behalf of Eric Hellman 

Sent: Friday, December 11, 2015 1:31 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] 
Matching print and electronic editions of the same book)

Users of xID services would be wise to check the termination clauses of their 
usage agreements to see whether they are permitted to keep and reuse the data 
they have cached.

Think about it. The world outside of 43017 has invented all sorts of new 
techniques to update and maintain metadata cooperatively.

Eric



Eric Hellman
President, Free Ebook Foundation
Founder, Unglue.it https://unglue.it/
https://go-to-hellman.blogspot.com/
twitter: @gluejar

Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] Matching print and electronic editions of the same book)

2015-12-11 Thread Terry Reese 
I think the best replacement at this point as a single API is to look at
Librarythings api though I'm not sure if it would work in all cases --
otherwise, I think using worldcat.org as a bridge to their works records
probably is your best bet.

--tr

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
Brian Riley
Sent: Friday, December 11, 2015 5:14 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB]
Matching print and electronic editions of the same book)

Does anyone know if OCLC is recommending an alternate solution that will
provide the same or at least similar functionality? 

I had played around with the Worldcat Discovery API when it was in beta but
am not sure of its present status or if its the most logical replacement for
xID.

   Brian 


From: Code for Libraries  on behalf of Eric
Hellman 
Sent: Friday, December 11, 2015 1:31 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB]
Matching print and electronic editions of the same book)

Users of xID services would be wise to check the termination clauses of
their usage agreements to see whether they are permitted to keep and reuse
the data they have cached.

Think about it. The world outside of 43017 has invented all sorts of new
techniques to update and maintain metadata cooperatively.

Eric



Eric Hellman
President, Free Ebook Foundation
Founder, Unglue.it https://unglue.it/
https://go-to-hellman.blogspot.com/
twitter: @gluejar

Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] Matching print and electronic editions of the same book)

2015-12-11 Thread Karen Coombs 
OCLC has been unable to update the xID API for several months.  We strive
to provide accurate and up-to-date information for all of our users. OCLC
will continue to run xID through March 2016 to allow those who use it to
search for alternate solutions for their specific needs. Although we
appreciate the suggestions, the product in “frozen state” would become less
and less effective over time and the data it provides increasingly
outdated. We believe continuing to offer that product would not be a
service to the community.

Karen

Karen A. Coombs
OCLC · Senior Product Analyst, WorldShare Platform
6565 Kilgour Place, Dublin, OH USA 43017
T +1-800-848-5879 ext. 4068
Skype librarywebchic

On Fri, Dec 11, 2015 at 2:42 PM, Ross Singer  wrote:

> Rachel, for what it's worth, it had nothing to do with your email (we were
> notified of it a couple of weeks ago, I guess because we were one of the
> few paying customers of the service).
>
> -Ross.
>
> On Fri, Dec 11, 2015 at 2:08 PM, Maderik, Rachel A 
> wrote:
>
> > Yes, thanks Bill for pointing that out, and now of course I'm regretting
> > my initial email. Regardless of the rate limit and lack of updates, this
> > API still has enormous value, and I'm sorry to see they're responding by
> > shutting it down (instead of keeping it on in a "frozen" state, if
> nothing
> > else).
> >
> >
> > -Original Message-
> > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> > Fleming, Jason
> > Sent: Friday, December 11, 2015 12:06 PM
> > To: CODE4LIB@LISTSERV.ND.EDU
> > Subject: Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re:
> > [CODE4LIB] Matching print and electronic editions of the same book)
> >
> > As a heavy user of the xID service I would look forward to a discussion
> > about what alternatives there might be.
> >
> > Thank you Bill for the link t to that announcement.
> >
> >
> > -Jason
> >
> > Jason Fleming
> > Information Technology Librarian
> >
> > 601 South College Road | Wilmington, NC  28403-5990
> > T: 910-962-2675 | flemi...@uncw.edu
> > http://library.uncw.edu
> >
> >
> >
> > -Original Message-
> > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> > William Denton
> > Sent: Friday, December 11, 2015 11:44 AM
> > To: CODE4LIB@LISTSERV.ND.EDU
> > Subject: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB]
> > Matching print and electronic editions of the same book)
> >
> > Rachel's message evidently prompted this:
> >
> > http://www.oclc.org/developer/news/2015/change-to-xid-services.en.html
> >
> > "OCLC offers an array of APIs that provide additional access points to
> > WorldCat and the WorldShare platform, allowing libraries and partners to
> > use the data inside applications in new and creative ways.  While we add
> > APIs at times, we also must retire some.  The xID product, including
> xISBN,
> > xISSN and xOCLCNum, has experience low usage and will be retired from the
> > OCLC API offering. No new keys are being issued, and the service will be
> > unavailable beginning March 15, 2016."
> >
> > OCLC people:  how about releasing the data behind the xID services?  A
> big
> > static dump of all of the numbers (ISBN, LCCN, OCLCnum) and how they're
> > related.
> > It'll be out of date the next day, but it'll still be very, very useful.
> >
> > When you needed them, the xID services were EXTREMELY helpful.  Perhaps
> > part of the cause of low usage was the access restrictions, both of
> number
> > of requests and commercial use.  If the data had been open, many more
> uses
> > would have arisen.  I say make it open now, under something like an Open
> > Data Commons Attribution License.
> >
> > Bill
> >
> >
> > On 10 December 2015, Maderik, Rachel A wrote:
> >
> > > Just a warning about OCLC's xID API: a few weeks ago I requested an
> > access token to bypass the rate limit, and was told that they are no
> longer
> > giving these out. I was also told that the data in xID has not been
> updated
> > for some time (I don't know when they stopped, but I think the rep told
> me
> > it was at least a year out of date). It was very disappointing to learn
> > this; if the project is essentially dead, this fact should be advertised
> > (at the very least, they should take down the pricing list!).
> > >
> > >
> > > -Original Message-
> > > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf
> > > Of William Denton
> > > Sent: Wednesday, December 09, 2015 5:40 PM
> > > To: CODE4LIB@LISTSERV.ND.EDU
> > > Subject: Re: [CODE4LIB] Matching print and electronic editions of the
> > > same book
> > >
> > > Thanks!  That opens things up.  We do have a lot of OCLC numbers.  For
> > > my example book, there's an 035 with three of them, including
> > > 841051199. If I look at
> > >
> > > http://worldcat.org/oclc/841051199
> > >
> > > it takes me to the human-readable page, but
> > >
> > > http://worldcat.org/oclc/841051199.rdf

Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] Matching print and electronic editions of the same book)

2015-12-11 Thread Eric Hellman 
Users of xID services would be wise to check the termination clauses of their 
usage agreements to see whether they are permitted to keep and reuse the data 
they have cached.

Think about it. The world outside of 43017 has invented all sorts of new 
techniques to update and maintain metadata cooperatively.

Eric



Eric Hellman
President, Free Ebook Foundation
Founder, Unglue.it https://unglue.it/
https://go-to-hellman.blogspot.com/
twitter: @gluejar

Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] Matching print and electronic editions of the same book)

2015-12-11 Thread Maderik, Rachel A 
Yes, thanks Bill for pointing that out, and now of course I'm regretting my 
initial email. Regardless of the rate limit and lack of updates, this API still 
has enormous value, and I'm sorry to see they're responding by shutting it down 
(instead of keeping it on in a "frozen" state, if nothing else). 


-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of 
Fleming, Jason
Sent: Friday, December 11, 2015 12:06 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] 
Matching print and electronic editions of the same book)

As a heavy user of the xID service I would look forward to a discussion about 
what alternatives there might be. 

Thank you Bill for the link t to that announcement.


-Jason

Jason Fleming
Information Technology Librarian
 
601 South College Road | Wilmington, NC  28403-5990
T: 910-962-2675 | flemi...@uncw.edu
http://library.uncw.edu



-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of William 
Denton
Sent: Friday, December 11, 2015 11:44 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] 
Matching print and electronic editions of the same book)

Rachel's message evidently prompted this:

http://www.oclc.org/developer/news/2015/change-to-xid-services.en.html

"OCLC offers an array of APIs that provide additional access points to WorldCat 
and the WorldShare platform, allowing libraries and partners to use the data 
inside applications in new and creative ways.  While we add APIs at times, we 
also must retire some.  The xID product, including xISBN, xISSN and xOCLCNum, 
has experience low usage and will be retired from the OCLC API offering. No new 
keys are being issued, and the service will be unavailable beginning March 15, 
2016."

OCLC people:  how about releasing the data behind the xID services?  A big 
static dump of all of the numbers (ISBN, LCCN, OCLCnum) and how they're 
related. 
It'll be out of date the next day, but it'll still be very, very useful.

When you needed them, the xID services were EXTREMELY helpful.  Perhaps part of 
the cause of low usage was the access restrictions, both of number of requests 
and commercial use.  If the data had been open, many more uses would have 
arisen.  I say make it open now, under something like an Open Data Commons 
Attribution License.

Bill


On 10 December 2015, Maderik, Rachel A wrote:

> Just a warning about OCLC's xID API: a few weeks ago I requested an access 
> token to bypass the rate limit, and was told that they are no longer giving 
> these out. I was also told that the data in xID has not been updated for some 
> time (I don't know when they stopped, but I think the rep told me it was at 
> least a year out of date). It was very disappointing to learn this; if the 
> project is essentially dead, this fact should be advertised (at the very 
> least, they should take down the pricing list!).
>
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf 
> Of William Denton
> Sent: Wednesday, December 09, 2015 5:40 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Matching print and electronic editions of the 
> same book
>
> Thanks!  That opens things up.  We do have a lot of OCLC numbers.  For 
> my example book, there's an 035 with three of them, including 
> 841051199. If I look at
>
> http://worldcat.org/oclc/841051199
>
> it takes me to the human-readable page, but
>
> http://worldcat.org/oclc/841051199.rdf
>
> shows it all in RDF, and I can see a lot of things like
>
>  rdf:about="http://experiment.worldcat.org/entity/work/data/1613596711#
> Place/japan">
>
> so I can pick out the work ID and look it up.  (Perhaps the work ID be 
> specified directly there?)
>
> So that would work, but aha, I just noticed I could make it a little simpler 
> by using xOCLCNUM to get the work ID, which is the owi field here:
>
> http://xisbn.worldcat.org/webservices/xid/oclcnum/841051199?method=get
> Metadata=json=*
>
> And then I can go to
>
> http://experiment.worldcat.org/entity/work/data/1613596711.rdf
>
> and get all the workExample links, and use those OCLC numbers.
>
> (Which I'm sure you knew, Roy, but perhaps didn't mention because of 
> the rate-limiting, but as far as I know our subscription means I can 
> get an access token so I can do some larger queries.)
>
> A first run of something like this would take a while to process everything, 
> but I'd store locally what I need to know, and then incremental updates for a 
> month's worth of news ebooks wouldn't take long.  Thanks!
>
> Bill
>
> On 9 December 2015, Roy Tennant wrote:
>
>> Do you have an OCLC number in your records? If so, you could call it 
>> at WorldCat like this:
>>
>> http://worldcat.org/oclc/XXX
>>
>> scrape the structured linked data on the page, looking for the 
>> "Example of Work" link, then follow

Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB] Matching print and electronic editions of the same book)

2015-12-11 Thread Ross Singer 
Rachel, for what it's worth, it had nothing to do with your email (we were
notified of it a couple of weeks ago, I guess because we were one of the
few paying customers of the service).

-Ross.

On Fri, Dec 11, 2015 at 2:08 PM, Maderik, Rachel A 
wrote:

> Yes, thanks Bill for pointing that out, and now of course I'm regretting
> my initial email. Regardless of the rate limit and lack of updates, this
> API still has enormous value, and I'm sorry to see they're responding by
> shutting it down (instead of keeping it on in a "frozen" state, if nothing
> else).
>
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Fleming, Jason
> Sent: Friday, December 11, 2015 12:06 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] OCLC shutting down xISBN and xID (was Re:
> [CODE4LIB] Matching print and electronic editions of the same book)
>
> As a heavy user of the xID service I would look forward to a discussion
> about what alternatives there might be.
>
> Thank you Bill for the link t to that announcement.
>
>
> -Jason
>
> Jason Fleming
> Information Technology Librarian
>
> 601 South College Road | Wilmington, NC  28403-5990
> T: 910-962-2675 | flemi...@uncw.edu
> http://library.uncw.edu
>
>
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> William Denton
> Sent: Friday, December 11, 2015 11:44 AM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: [CODE4LIB] OCLC shutting down xISBN and xID (was Re: [CODE4LIB]
> Matching print and electronic editions of the same book)
>
> Rachel's message evidently prompted this:
>
> http://www.oclc.org/developer/news/2015/change-to-xid-services.en.html
>
> "OCLC offers an array of APIs that provide additional access points to
> WorldCat and the WorldShare platform, allowing libraries and partners to
> use the data inside applications in new and creative ways.  While we add
> APIs at times, we also must retire some.  The xID product, including xISBN,
> xISSN and xOCLCNum, has experience low usage and will be retired from the
> OCLC API offering. No new keys are being issued, and the service will be
> unavailable beginning March 15, 2016."
>
> OCLC people:  how about releasing the data behind the xID services?  A big
> static dump of all of the numbers (ISBN, LCCN, OCLCnum) and how they're
> related.
> It'll be out of date the next day, but it'll still be very, very useful.
>
> When you needed them, the xID services were EXTREMELY helpful.  Perhaps
> part of the cause of low usage was the access restrictions, both of number
> of requests and commercial use.  If the data had been open, many more uses
> would have arisen.  I say make it open now, under something like an Open
> Data Commons Attribution License.
>
> Bill
>
>
> On 10 December 2015, Maderik, Rachel A wrote:
>
> > Just a warning about OCLC's xID API: a few weeks ago I requested an
> access token to bypass the rate limit, and was told that they are no longer
> giving these out. I was also told that the data in xID has not been updated
> for some time (I don't know when they stopped, but I think the rep told me
> it was at least a year out of date). It was very disappointing to learn
> this; if the project is essentially dead, this fact should be advertised
> (at the very least, they should take down the pricing list!).
> >
> >
> > -Original Message-
> > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf
> > Of William Denton
> > Sent: Wednesday, December 09, 2015 5:40 PM
> > To: CODE4LIB@LISTSERV.ND.EDU
> > Subject: Re: [CODE4LIB] Matching print and electronic editions of the
> > same book
> >
> > Thanks!  That opens things up.  We do have a lot of OCLC numbers.  For
> > my example book, there's an 035 with three of them, including
> > 841051199. If I look at
> >
> > http://worldcat.org/oclc/841051199
> >
> > it takes me to the human-readable page, but
> >
> > http://worldcat.org/oclc/841051199.rdf
> >
> > shows it all in RDF, and I can see a lot of things like
> >
> >  > rdf:about="http://experiment.worldcat.org/entity/work/data/1613596711#
> > Place/japan">
> >
> > so I can pick out the work ID and look it up.  (Perhaps the work ID be
> > specified directly there?)
> >
> > So that would work, but aha, I just noticed I could make it a little
> simpler by using xOCLCNUM to get the work ID, which is the owi field here:
> >
> > http://xisbn.worldcat.org/webservices/xid/oclcnum/841051199?method=get
> > Metadata=json=*
> >
> > And then I can go to
> >
> > http://experiment.worldcat.org/entity/work/data/1613596711.rdf
> >
> > and get all the workExample links, and use those OCLC numbers.
> >
> > (Which I'm sure you knew, Roy, but perhaps didn't mention because of
> > the rate-limiting, but as far as I know our subscription means I can
> > get an access token so I can do some larger queries.)
> >
> > A first run of something like this would take a while to process
>