Our investigation into a report of “UnknownID” errors in OCLC’s xID services has revealed a problem with the data in the source database going back to May 2012. All three services – xISBN , xISSN, and xOCLCNum – are affected and, while the timeframe in question represents only a small portion of the total data, users will see errors for records added to WorldCat during this period. We apologize for any inconvenience this may cause, as we know that many of you make heavy use of this service in local applications.
We are currently analyzing options for resolving this as quickly possible and will provide an update to the Developer Network community on Monday, July 22nd. In the meantime, the database will remain up, available, and stable, in its current state. As we pursue an expedited solution, the Platform and Data Services teams are also working together to implement procedures to prevent similar problems from occurring in the future.
Working with the teams here to identify and respond to the problem gave me a great opportunity to learn more about our future plans for xID, in which we’re planning to invest increased effort. As the liaison to the Developer Network community, I’d love to gather some input and share your thoughts and needs with my colleagues who will be working on this project. So a few questions to get you thinking…
• Which xIdentifier services are you using and in what contexts?
• What value are they adding for your users?
• What kinds of enhancements would you like to see?
If you’re using (or have evaluated) the xID services, please let us know your thoughts – comment here, respond to the list, or send me a note directly – email@example.com. I’ll summarize the feedback, both for the list and for my colleagues, and keep you posted on our future plans!