Parts need to be more visible on the place holds screen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Consider this my attempt at doing something that will improve the karma of parts in the #evergreen channel.
One issue we frequently find with parts is that users miss the parts selector on the Place Hold screen. If there are non-parted items on the bib record, the select menu defaults to the "All Parts" option, meaning that the resulting hold will be a title-level hold. However, quite often, the title may only have one or two non-parted copies, and there ends up being a long list of title-level holds while there are plenty of parted items that could fill the patron's request.
I'm working on code to increase the visibility of parts on the place holds screen. The code does the following:
* Adds some styling so that the "Select a part" is bold and there is some general padding around the parts selector.
* Adds a config.tt2 option to select a part with radio buttons instead of a select menu. The benefit to this option is that all the parts will immediately display on the place holds screen.
I'll post a work-in-progress working branch as soon as I get an LP number.
tags: | added: needsreleasenote |
Changed in evergreen: | |
status: | Triaged → In Progress |
assignee: | nobody → Kathy Lussier (klussier) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
The work-in-progress branch is available at:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ kmlussier/ lp1422802- more-visible- parts
I'm still working a couple of issues:
* A cleaner display for the parts when the radio button option is enabled.
* A better option to require users to select a part.
For the latter, our preference is to leave all the radio buttons deselected, forcing the user to make an explicit choice when selecting a part. I initially used the HTML5 required attribute to do so, but I now see that the attribute isn't supported in Safari at all and only has support in IE back to IE10 (not sure how far back we should support.)
The only other way I know of to require the field is to use javascript, but I know we want to limit the use of javascript in the public catalog. I'll keep digging, but I'm open to any suggestions.