OCLC enhanced content & 856 tag
Some of the records we copy catalog via OCLC have URL's in 856 for enhanced content (covers, sample text, etc.), which don't lead anywhere. I presume this is because of an invalid key. Is there a work-around? Are we better off simply deleting the field & relying on Koha's Amazon/ Google services for enhanced content? Here's how a typical 856 would be structured: http://firstsearch.oclc.org/WebZ/DECRead?standardNoType=1 &standardNo=0764005065 &sessionid=0 &srcdbname=worldcat &key=72a7beb35042d2bc25d11fe85b6bb7db92925155ffefd95c11ba52379d04bad4 &ectype=MOREINFO$xOCLC EC$3More Info Many thanks, Cab Vinton, Director Sanbornton Public Library Sanbornton, NH
Hi, On Thu, Feb 12, 2009 at 12:17 PM, Cab Vinton <bibliwho@gmail.com> wrote:
http://firstsearch.oclc.org/WebZ/DECRead?standardNoType=1 &standardNo=0764005065 &sessionid=0 &srcdbname=worldcat &key=72a7beb35042d2bc25d11fe85b6bb7db92925155ffefd95c11ba52379d04bad4 &ectype=MOREINFO$xOCLC EC$3More Info
That URL works for me after removing the $x and $3 and directs me to a page containing a brief summary. I don't know if you have to pay anything extra to get this sort of enhanced content from FirstSearch, but if so, it strikes me that it's worth at least trying to use it. If there's a glitch with the key, perhaps OCLC can help. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt
Thanks, Galen. That does seem to be the trick. I tried deleting the $x, $3 subfields for a number of other records & that also worked fine. It's interesting, however, that not all records actually have a string input for the "key". The 856's for cover art, for example, don't require it ... Thanks again, Cab Vinton, Director Sanbornton Public Library Sanbornton, NH
participants (2)
-
Cab Vinton -
Galen Charlton