Re: [IUG] How to make the 856 field visible in Opac
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Date: Wed, 11 Jan 2012 12:56:11 -0500
- From: Bob Duncan <duncanr at lafayette dot edu>
- Subject: Re: [IUG] How to make the 856 field visible in Opac
At 09:00 AM 1/11/2012, Margaret wrote:
There is a web option you need to set as true, e.g., DISPLAY_856=z|true
On 1/11/2012 6:06 AM, Nas Yakubu wrote:
Hi,
Can anyone tell me how to make the 856 field (URL for electronic resources)
visible on our OPAC.
The true value in the DISPLAY_856 wwwoption controls whether or not
the link opens in a new window. The links themselves display
automagically -- no wwwoption is needed to make them display. (If
using bib_display.html, you need to use the "URLS" token in order for
the links to display.)
If the question is how to make the URL itself display as the link
text, you can alter the first parameter of the display_856 wwwoption
to use the subfield where the URL is located as the link text (presumably $u).
If the question is how one can make the content of an 856 field
display in the same way that content from other MARC fields display,
AFAIK, the answer is that as long as the fields are y-tagged, you
can't. Most y-tagged fields can be made to display by accounting for
them in webpub.def and bib_display.html (assuming you're using one or
both), but the 856 field appears to have a mind of its own in this
regard -- I have not been able to get a y-tagged 856 to display this
way. If you change an 856 field's field group tag in the MARC record
to something other than y, you can get its content to display, but
then you lose the link table.
You could always duplicate the 856$u in a notes field, or use
Javascript to grab the URL from the source and write it somewhere
else in the record.
Bob Duncan
~!~!~!~!~!~!~!~!~!~!~!~!~
Robert E. Duncan
Integrated Technologies Librarian
Lafayette College
Easton, PA 18042
duncanr at lafayette dot edu
http://library.lafayette.edu/
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.