Pickup library defaults to Home OU of staff, instead of patron when placing holds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.11 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Evergreen 2.3.4 (TPAC OPAC forced)
Postgres 9.1.8
Ubuntu 12.04
OpenSRF 2.1.2
When staff attempt placing a hold on behalf of a patron via the "Holds" tab in the patron account, the "Pickup Location" defaults to the home library of the currently logged in staff member, not the home library of the patron.
When the patron has set their pickup library preference, this isn't a problem, but when placing holds for users who haven't yet configured this setting this strange default is troublesome.
This is easily tested by attempting to place a hold for a patron who's home ou is different than that of the currently logged in staff member. You'll notice the default pickup location is the home ou of the staff member, not of the patron.
Changed in evergreen: | |
status: | Triaged → Confirmed |
importance: | Undecided → Medium |
Changed in evergreen: | |
assignee: | nobody → Jeff Godin (jgodin) |
milestone: | none → 2.5.2 |
status: | Confirmed → In Progress |
no longer affects: | evergreen/2.3 |
Changed in evergreen: | |
milestone: | 2.5.2 → 2.6.0-alpha1 |
Changed in evergreen: | |
milestone: | 2.6.0-alpha1 → 2.6.0-beta1 |
Changed in evergreen: | |
milestone: | 2.6.0-beta1 → 2.6.0-rc1 |
Changed in evergreen: | |
milestone: | 2.6.0-rc1 → none |
no longer affects: | evergreen/2.4 |
no longer affects: | evergreen/2.5 |
no longer affects: | evergreen/2.6 |
Changed in evergreen: | |
assignee: | Mike Rylander (mrylander) → nobody |
status: | In Progress → Confirmed |
Changed in evergreen: | |
milestone: | 2.12-rc → 2.12.1 |
Changed in evergreen: | |
assignee: | nobody → Galen Charlton (gmc) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
This doesn't seem to occur in master for our production environment, so I'm guessing that all the changes that were made to place hold recently for 2.4 might have changed how the lookup occurs and setting various options.
Marking as affecting 2.3 presently, but needs further testing by someone on 2.3 to confirm.