[OPEN-ILS-GENERAL] ***SPAM*** Re: ***SPAM*** Re: Why is Placing a Hold on Volume Level not possible in the OPAC ?
Repke de Vries
repke at xs4all.nl
Mon Jun 7 16:55:24 EDT 2010
Thanks Bill for the hint to make the Volume Hold conditional by
taking a cue from record and/or call number - the call number idea
in particular.
Jason, your idea to
>> 2) have the main Place Hold link for the record prompt the user
>> for a specific volume
is very attractive from a usability point of view (with tens and tens
of bound volumes, the Copy Information list quickly grows too long)
and ties in well with experimental work Laurentian University did on
their Search Results page which has the Place Hold button straight in
the middle of the screen:
http://laurentian-test.concat.ca/opac/en-CA/skin/btresult/xml/
rresult.xml?rt=keyword&tp=keyword&t=Journal%20unesco&l=105&d=1&f=&av=
however: our library's scenario of use is more complicated than
"prompting the user for a specific volume" if Place Hold is clicked:
evaluating Evergreen we are struggling with a situation where we have
printed journals with bound volumes (highest level in the hierarchy)
but also article level bibliographic descriptions (lowest level of
the hierarchy); at the article level a MARC 773 $g points to the
highest level - like "Vol. 13, No. 2, p. 273-287"
It is well possible to make that 773 a clickable link and help the
user jump to the printed journal where he can Place the Volume Hold
but both in Bill's approach and in your single action Place Hold With
Dialogue, the user has to remember from the previous step which
Volume to pick: "O, yes, I believe it was in Volume 13 .. or was it
twelve ?"
Somehow you want the user to
- either arrive at the level where he can place a Volume Hold with
Evergreen remembering the right Volume (would probably need
additional information in the 773 at article level)
- or stay at the level of the search result and have a Place Volume
Hold right there; the physical copy however is not at that article level
While at it: having a journal article bibliographic description show
up at all in the OPAC, we need a 852 with "dummy barcode" and other
fake information. It would be very interesting to extend the "non
barcoded resource" discussion in the Evergreen community to resources
like journal articles (or Twin Peaks reviews as in Bill Ott's) and
instead of a 773 / 852 combo, use the 856 which gives you both OPAC
visibility *and* a clickable link for jumping to the right level for
Place Volume Hold - be it with usability issues as explained above.
Appreciating your or anyone's comments,
Repke de Vries, PPL
Op 7-jun-2010, om 1:29 heeft Bill Ott het volgende geschreven:
> On 6/4/10 12:06 PM, Jason Etheridge wrote:
>> On Fri, Jun 4, 2010 at 11:28 AM, Repke de Vries<repke at xs4all.nl>
>> wrote:
>>
>>> while it is possible from the Staff Client. Or did we miss
>>> something ?
>>>
>> I believe this may be a case of overprotectiveness. However, IMO,
>> ideally, if were to allow patrons to place volume level holds, we
>> would:
>>
>> 1) only do it for volumes where it made sense (where the items are
>> indeed different), and not for any volume on any record. How to
>> designate this, I don't know.
>> 2) have the main Place Hold link for the record prompt the user for a
>> specific volume (based on the same designations mentioned above)
>>
>>
>>> Any suggestions or advice ? Change the OPAC code ?
>>>
>> It appears you can do the following without adverse effects:
>>
>> 1) add the VOLUME_HOLDS permission to the User (or equivalent)
>> permission group
>> 2) modify /openils/var/web/opac/skin/default/js/rdetail.js (even if
>> you're using the craftsman skin) by searching the file for
>> 'hold_div',
>> and changing the preceding "if (isXUL()) {" line to "if (true) {"
>>
>> Better would be to replace the if condition with a permission check
>> against the owning library of the volume, and again, it would be nice
>> if we could somehow allow this for some volumes and not others.
>>
>
>
> We do allow patrons to place volume holds. Just as Jason notes, in
> many cases there's no reason, so I take a cue from the record and/
> or call number. If there is series data or a call number ending in
> a "v.#', I turn on the link in the opac.
>
> Here's an example:
> http://grpl.michiganevergreen.org/opac/en-US/skin/default/xml/
> rdetail.xml?r=5235487&ol=9&t=twin%
> 20peaks&tp=keyword&l=9&d=1&hc=13&rt=keyword
>
More information about the Open-ils-general
mailing list