OCLC Developer Network

xISBN News Archive

Syndicate content

Introduction to Web Services Webinar scheduled for Thursday, July 28

Heard people talk about "using APIs and Web Services" and not quite sure what they were talking about? Or more likely--been talking about Web Services to your colleagues or manager/director and gotten blank looks?

Join Karen Coombs of the OCLC Developer Network as she demystifies the topic. Send your fellow staff members, to help them understand what you do.

Planned downtime for OCLC services on February 27 to upgrade network storage

On Sunday, February 27 there will be a scheduled service downtime for a number of OCLC services from 1:00 am until at least 6:00 am and, at most, 11:00 am (U.S. Eastern Time). We apologize for any inconvenience this causes. We need to take the following services off-line in order to upgrade the storage systems and capacity for all OCLC services. During this time, the following services will be unavailable:

Daily noncommercial usage limits raised for xISBN and xISSN

Based on feedback from OCLC Developer Network members, OCLC is pleased to announce that basic limits on all xIdentifier Web services have been increased to 1,000 queries per day. This increase is intended to facilitate easier use of the JSON-P format now in place, and is effective immediately. OCLC member libraries who also maintain an OCLC cataloguing subscription still remain eligible for higher usage limits at no charge. All other libraries and/or commercial organizations can select the subscription option that best meets their needs.

Finding the original edition using xISBN services

Another question that was asked at the OCLC Web Services Bootcamp at VALA was "Can I find the earliest edition with xID?" The answer is Yes The getEditions response from xISBN has fields for both edition and year published information. Edition information is sometimes missing so the best way to handle finding the earliest edition is to use the year field. There are a couple different ways one might do this. One could use an XSL to sort the nodes ascending by year and then pull out the ISBN or OCLC Number of the first one.

xISBN Tips and Tricks

One question that was asked at the OCLC Web Services Bootcamp at VALA was if the xISBN service handled both 10 and 13 digit ISBNs. The answer is yes. You can send either a 10 or 13 digit ISBN for the same book to the service and you will get back the same response. Case in point Learning Python has both a 10 and 13 digit ISBN.

xID new features

We added a few new features to xID service: - xISSN now supports ISSN-L and RSSURL field, such as http://xissn.worldcat.org/webservices/xid/issn/1095-9203?method=getMetadata&fl=issnl,rssurl ISSN-L data is obtained from ISSN agency, and rssurl is obtained from ticTOCS. xISSN also adds values to both data set, for example, xISSN automatically adds RSSURL to all ISSNs in same group. - xOCLCNUM now supports OCLC workid, such as: http://xisbn.worldcat.org/webservices/xid/oclcnum/55847258?fl=owi And you can query by workid as well: http://xisbn.worldcat.org/webservices/xid/owi/owi718389 I highly recommend using "owi[0-9]" in its whole format when you came upon workid, this will be very helpful for identifying workid from any web pages and facilitates interoperability and mashup. For more information, please check xISSN and xOCLCNUM API.

New xISBN bookmarklets supports thousands of libraries

xISBN bookmarklets now supports thousands more libraries by integration with Worldcat Registry. The previous xISBN bookmarket supports more than 300 libraries, however, the list was manually maintained and it's challenging to keep these links up-to-date, By ingesting good Registry OPAC information into xISBN bookmarklet, we are able to support thousands more libraries in a more sustainable way. xISBN bookmarklet automatically pulled new information from Worldcat Registry on a monthly basis, so if a library maintains up-to-date information in Registry, its data will be automatically reflected in xISBN bookmarklet. Furthermore, we have also developed mechanisms to validate and improve OPAC linking templates in Registry during the process. The previous xISBN bookmarklet is still maintained in http://xisbn.worldcat.org/liblook/

guessing publisher from ISBN prefix

ISBN number is structured and contains four parts of information: Group or country identifier, Publisher identifier, Title identifier and check digits. Because ISBN are allocated by blocks to publishers, all ISBNs in same block should have same publisher information. So it's possible to guess ISBN's publisher information from its structure, however this will only work well when there is a big database of ISBN-prefix and corresponding publisher name. Incidentally, there are over 19 million ISBNs in xISBN database, from this database, we can actually create a rather comprehensive ISBN-prefix database. Inspired by Publisher Name Server project in OCLC Research, in last data release we count 551,528 ISBN publisher-prefixes, and it is not very far away from ISBN agency's directory ( 880,000 prefixes) . From our ISBN prefix table, we add "guessing" service for xISBN, which tries to guess publisher information of any ISBN, even they are not covered by Worldcat, such as following:
http://xisbn.worldcat.org/webservices/xid/isbn/7806281622.js?method=hyphen
returns
{"stat":"ok",
 "list":[{
	"isbn":["7-80628-162-2"],
	"area":"China, People's Republic",
	"publisher":"San Qin chu ban she",
	"city":"Xi'an Shi"}]}
It will be interesting to see how this information can be used. On the other side, the "guessing" service is still approximate, we don't know all ISBN prefixes, and sometimes one ISBN prefix doesn't neatly identify one publisher, so use with caution.

Better hyphen support in xISBN service

xISBN service used to handle ISBN as a plain number, when a hyphenated ISBN is requested, we normalize it to a plain number internally, and present the response in plain number. However, hyphenated ISBNs carry structure information, and sometimes library OPAC system indexed hyphenated ISBN only. We just deployed a new version of xISBN service with better hyphen support, when requested ISBN is hyphenated, the response ISBNs will be hyphenated as well; we also added additional method of explicitly hyphenating ISBNs, such as: http://xisbn.worldcat.org/webservices/xid/isbn/9780596002817?method=hyphen It is implemented by downloading the ISBN range HTML file, turn it into a lookup table, and when an ISBN should be hyphenated, we use the lookup table to figure out where to add the hyphen. It is trivial to parse the ISBN range HTML file, but it would be great if ISBN agency has a machine-readable format of this file.

Comments

re: Better hyphen support in xISBN service

I recently came across your blog and have been reading along. I thought I would leave my first comment. I don't know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often.

Ruth

http://laptopmessengerbag.info

xISBN JSON callback and a GoogleBooks demo

We added a few more features in xISBN service recently: - JSON callback JSON output is native JavaScript, and callbacks are particularly useful for use with web service requests in client-side JavaScript. see: http://xisbn.worldcat.org/xisbnadmin/doc/api.htm#callback - tab-delimited format dissemination This is useful if you need to do a unix cut: $ curl "http://xisbn.worldcat.org/webservices/xid/isbn/0596002815?method=getEditions&fl=title,year&format=txt" | cut -f 2 - a demo of integrating Googlebooks with xISBN JSON callback http://xisbn.worldcat.org/xisbndemo/index.htm

Follow the OCLC Developer Network:

The OCLC Developer Network supports the use of OCLC Web Services—a set of tools and APIs that expose data and services for WorldCat and our member libraries and partner institutions or companies. learn more »

© 2010 OCLC Domestic and international trademarks and/or service marks of OCLC Online Computer Library Center, Inc. and its affiliates


Powered by Drupal, an open source content management system