Hold pickup library defaults to consortium; hold placement fails

Bug #1669580 reported by Andrea Neiman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Invalid
Undecided
Unassigned

Bug Description

EG 2.12-beta

When placing a hold, the holds placement screen defaults the pickup location to "Example Consortium" which is not a valid pickup location (OU type doesn't allow users or copies/volumes). If you click "submit" without changing this to a valid hold pickup location, nothing happens & the hold is not placed. Console gives an uncaught type error.

If you click the "pickup location" dropdown, "Example Consortium", "Example System 1", and other invalid pickup locations are grayed out and can't be selected in the list. Similarly you can't key through the list and select an invalid pickup location.

This occurs in both XUL and Webby.

Tested on the MLNC 2.12-beta server. Not able to reproduce on 2.11.

Revision history for this message
Terran McCanna (tmccanna) wrote :

I only see this when I log in with the admin account (which I expect because that account doesn't have a home library). When I log in with another user, it defaults to the user's preferred pickup location or home library as I expect it to.

Revision history for this message
Kathy Lussier (klussier) wrote :

I think this is probably related to / a duplicate of https://bugs.launchpad.net/evergreen/+bug/1167541. The underlying problem is that it looks at the logged-in account's home library, not the workstation library.

I also thought there was an existing bug about the silent failure when defaulting to the CONS library, but I couldn't find anything.

As somebody who uses the admin account all the time, I can confirm that this has been a problem in previous releases.

Revision history for this message
Andrea Neiman (aneiman) wrote :

A detail that eluded me... thanks Terran. On non-admin accounts I also see the expected results. Will mark this invalid.

Changed in evergreen:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.