Apologies for not chiming in sooner. Just got back from a whirlwind Washington visit.
Generally, we've been trying to collect Edition-level IDs since the redesign. The list of available identifiers is itself editable, although I'm the first to admit the UI isn't working (doesn't check for duplicates, tricky to communicate that we'd also like a URL pattern so we can auto-link in the UI, and that session-based URLs aren't useful). You can see what we've got so far here: http://openlibrary.org/config/edition.yml API - You can use the Books API today to make requests using certain keys. The API supports ISBNs, LCCNs, OCLC numbers and OLIDs (Open Library IDs). In an ideal world, you could use any key that's written in that config file to hit the API, and retrieve all the other IDs. (I think that idea of "concordance" would be profoundly useful.) OPDS - We just released a V1 of OPDS for Edition records, in addition to RDF & JSON. The OPDS attempts to provide a series of links, identifers and "bibo" numbers. E.g. http://openlibrary.org/books/OL5880820M.opds http://openlibrary.org/books/OL5800131M.opds (note LibraryThing ID treatment) Sadly, the RDF, JSON and OPDS versions of our edition records don't match today. We're aware of that. ID sets for other objects I agree that Freebase, DBPedia, Wikipedia IDs for Works AND Authors would be useful. So, the ideal, in response to James' initial thoughts... "One problem we run up against frequently is that while it's trivial to get the OL ID for a given ISBN, it's harder for other identifiers - such as Amazon ASINs." ... would be to ensure that any/all IDs OL knows about for an Edition (or Work or Author) are presented in the response from OL. And, you can build a request with more ID types than are currently supported. g On 3/16/11 1:38 AM, frankie roberto wrote: > On 15 Mar 2011, at 22:33, Edward Betts<[email protected]> wrote: > >> On 03/15/2011 05:30 AM, Frankie Roberto wrote: >>> Being able to add third party identifiers for works would be great. I can't >>> currently see a way of doing that? >> >> Right now there are no identifiers associated with works. It sounds like >> there is a demand for them, I'm keen that we add them. > > That seems the main upshot of this discussion, yes. If you could add a > similar 3rd party identifiers interface to Works that you already have > for editions, that would be fantastic. > > Also, if there was a way of doing reverse lookups (ie searching for an > OL Work or Edition matching a given third party identifier) via the > API, that would be really useful (for me at least) too. > > (this may already be possible, but I couldn't see how to do it.) > > Frankie > _______________________________________________ > Ol-discuss mailing list > [email protected] > http://mail.archive.org/cgi-bin/mailman/listinfo/ol-discuss > To unsubscribe from this mailing list, send email to > [email protected] _______________________________________________ Ol-discuss mailing list [email protected] http://mail.archive.org/cgi-bin/mailman/listinfo/ol-discuss To unsubscribe from this mailing list, send email to [email protected]
