 |
 |
@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 <http://www.oclc.org/data/attribution.en.html>, 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 <[log in to unmask]> 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:[log in to unmask]] On Behalf Of > sara amato > Sent: Monday, December 14, 2015 9:57 AM > To: [log in to unmask] > 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 < > [log in to unmask] <mailto:[log in to unmask]>> > wrote: > > > > Sara, > > > > The canonical URI you are looking for is > http://worldcat.org/oclc/8410511 <http://worldcat.org/oclc/8410511> < > 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/> < > http://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/> < > http://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/xxxxx <http://worldcat.org/oclc/xxxxx> < > http://worldcat.org/oclc/xxxxx <http://worldcat.org/oclc/xxxxx>>'. 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 <http://dataliberate.com/> > > <http://dataliberate.com/ <http://dataliberate.com/>> > > Linkedin: http://www.linkedin.com/in/richardwallis > > <http://www.linkedin.com/in/richardwallis> > > <http://www.linkedin.com/in/richardwallis > > <http://www.linkedin.com/in/richardwallis>> > > Twitter: @rjw > > > > On 12 December 2015 at 22:47, Sara Amato <[log in to unmask] <mailto: > [log in to unmask]> <mailto:[log in to unmask] <mailto: > [log in to unmask]>>> wrote: > > In thinking about using worldcat.org <http://worldcat.org/> > > <http://worldcat.org/ <http://worldcat.org/>> as a bridge to a works > record, I'm wondering about using 'experiment.worldcat.org < > http://experiment.worldcat.org/> <http://experiment.worldcat.org/ < > http://experiment.worldcat.org/>>', e.g. > > http://experiment.worldcat.org/oclc/841051199.jsonld < > http://experiment.worldcat.org/oclc/841051199.jsonld> < > http://experiment.worldcat.org/oclc/841051199.jsonld < > 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 <http://experiment.worldcat.org/> < > http://experiment.worldcat.org/ <http://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 > > <http://www.worldcat.org/> <http://www.worldcat.org/ < > http://www.worldcat.org/>> data??? Anybody know? > > > > > > > > > > On Fri, Dec 11, 2015 at 2:17 PM, Terry Reese <[log in to unmask] <mailto: > [log in to unmask]> <mailto:[log in to unmask] <mailto:[log in to unmask]>>> > 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 <http://worldcat.org/> > >> <http://worldcat.org/ <http://worldcat.org/>> as a bridge to their > works records probably is your best bet. > >> > >> --tr > >> > >> -----Original Message----- > >> From: Code for Libraries [mailto:[log in to unmask] > >> <mailto:[log in to unmask]> <mailto:[log in to unmask] > >> <mailto:[log in to unmask]>>] On Behalf Of Brian Riley > >> Sent: Friday, December 11, 2015 5:14 PM > >> To: [log in to unmask] <mailto:[log in to unmask]> > >> <mailto:[log in to unmask] <mailto:[log in to unmask]>> > >> 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 <[log in to unmask] > >> <mailto:[log in to unmask]> <mailto:[log in to unmask] > >> <mailto:[log in to unmask]>>> on behalf of Eric Hellman > >> <[log in to unmask] <mailto:[log in to unmask]> <mailto:[log in to unmask] > >> <mailto:[log in to unmask]>>> > >> Sent: Friday, December 11, 2015 1:31 PM > >> To: [log in to unmask] <mailto:[log in to unmask]> > >> <mailto:[log in to unmask] <mailto:[log in to unmask]>> > >> 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 <http://unglue.it/> https://unglue.it/ > >> <https://unglue.it/> <https://unglue.it/ <https://unglue.it/>> > >> https://go-to-hellman.blogspot.com/ > >> <https://go-to-hellman.blogspot.com/> > >> <https://go-to-hellman.blogspot.com/ > >> <https://go-to-hellman.blogspot.com/>> > >> twitter: @gluejar >