Acq: Multi-Branch Libraries Can't See All Their Branch Funds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.11 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Evergreen 3.11.1
Unfortunately the fix for https:/
Library staff can only see the funds for the branch they are logged in at and the ancestors.
There are a few bugs around this issue with possible solutions:
https:/
https:/
We'd like to suggest another possible solution. For selection lists and purchase orders, have Evergreen decide what funds to display in the drop down for the batch item updater and the Items page based on what the user picks for Item Owning Library. Once you enter a value for Item Owning Library you would then be given a list of funds belonging to that library/branch and its ancestors. (This should also apply when setting up distribution formula.)
We couldn't think of a case where you'd want to pay for an item for one branch with funds for another. (If you overspend in one fund and under spend in another other you should transfer money from one fund to the other.)
I think this bug is a blocker for future releases (we've had to revert the fix so our multi-branch libraries can use acquisitions).
description: | updated |
Changed in evergreen: | |
status: | New → Confirmed |
tags: | added: signedoff |
Changed in evergreen: | |
milestone: | none → 3.12.2 |
importance: | Undecided → Medium |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
I have a pullrequest here: https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ tlittle/ LP2040637_ Viewbranchfunds
The fix for bug 1999544 relied on the ancestors of the workstation where the user was logged in as. Dojo relied on the permissions of the user and their available depth. Specifically, the fund selector for line items checked MANAGE FUND, CREATE_ PURCHASE_ ORDER, and CREATE_PICKLIST. The fund selector for PO direct charges checked MANAGE_FUND and CREATE_ PURCHASE_ ORDER.
This new branch now should behave the same way as Dojo, where it's checking the perms available to the user and where they can use them.