I'm not sure there's any good way to include a DDC or LCC in an SAP1 OpenURL for COinS. Same with subject vocabularies. Really, I'm pretty sure there is NOT, in fact. But if there is, sure, throw them in, put in anything you've got.

But this re-affirms my suggestion that there might be a better microformat-ish way to embed information in the page in addition to OpenURL. COinS/OpenURL is important because we have an established infrastructure for it, but it's actually pretty limited and not always the easiest to work with.

Jonathan

Karen Coyle wrote:
Thanks for the specifics. I'll definitely include those. We also have things like DDC and LCC -- I'm not sure those help in the OpenURL world although I'm always hoping that someone will find a good use for them since they are rich bits of information. And we have lots of subjects, but I guess I should just think in terms of the traditional bibliographic identification. Anyway, I'll try some out and let people know when there's something to see.

And thanks to all for the enthusiastic response. I thought it would be a good idea, but wasn't really sure. Now I am.

kc

Jonathan Rochkind wrote:
Yes. A COinS object could/would allow users using LibX to be directed to my link resolver, to find an alternate licensed ebook copy of that book, to issue an ILL request for a print version, or to find a print version on the local libraries shelves.

It is important that the COinS object includes ISBN, LCCN and/or OCLCnum, if those identifiers are available for a given record. It is also useful it it contains a rfr_id identifying Open Library as the source.

Jonathan

Karen Coyle wrote:
I have a question to ask for the Open Library folks and I couldn't quite figure out where to ask it. This seems like a good place.

Would it be useful to embed COinS in the book pages of the Open Library? Does anyone think they might make use of them?

Thanks,
kc





--
Jonathan Rochkind
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
410.516.8886 rochkind (at) jhu.edu

Reply via email to