[ List Archives Home ] [ Thread index for 2008 ]
[ Date index for 2008 ]
[ Author index for 2008 ]
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
At 03:18 PM 06/12/2008, you wrote:
> Adam asked:
> Out of curiosity, what is the token being used to pull the ISBN in the
> bibdisplay?
Hi Adam,
As far as I know, this is the crux of the problem. Can someone write
back if I'm missing something obvious? I'm working with OCLC# but the
issue is the same as for ISBN...
On briefcit, the token <!--{fieldspec:Vbo}--> outputs just the OCLC #.
On bib_display, that token is not supported. You have to use this token
<!--{recordinfo:o}--> which outputs all this and which does not work
with the LibX GBS classes:
. . .
No token is involved on the bib record display. Various folks who
have reported to this list code they've developed for the Google Book
Viewability API on the bib record display (Michael Kreyche at Kent
State and Beth Bradley at Canisius), are using Javascript to grab a
standard number value by virtue of the number itself being the
innerHTML value of an HTML element. (Michael does it one way; Beth
does it another.)
The LibX GBS classes approach depends on the standard number being
easily isolated within its own identifiable HTML element (which the
briefcit token makes possible).
I haven't yet tried Beth's code, but as far as I can tell, using it
for both record and search result displays looks like the only
all-in-one solution offered to this list so far, plus it includes
code to strip out extraneous information in the standard number
field, which results in a better return from GBS. (I'm sure Michael
will get around to adding this to his code at some point.)
Bob Duncan
~!~!~!~!~!~!~!~!~!~!~!~!~
Robert E. Duncan
Systems Librarian
Editor of IT Communications
Lafayette College
Easton, PA 18042
duncanr at lafayette dot edu
http://www.library.lafayette.edu/
Home
Mailing list