Need the Ability to Configure the Context Org Unit Scope Depth for Funds and Providers

[Erica Rohlfs]

Evergreen version 2.4.6 and 2.5.2

Currently in Evergreen, the Funds (Admin->Server Administration->Acquisitions->Funds) and Providers (Admin->Server Administration->Acquisitions->Providers) Context Org Unit scoping options default to the workstation’s library. For example, if my staff client workstation is logged in at HQ, then the Context Org Unit automatically defaults to HQ. For library systems that perform centralized acquisitions tasks, the constant need to scope out to the system level each time they access the Funds and Providers interfaces can be tiresome.

The Funds and Providers interfaces should be configurable to define the scoping depth of the Context Org Unit.

Thank you!

[Jennifer Pringle (jpringle-u)]

It would also be good to be able to specify the default org unit to use for the purchase orders and invoices. Our multi-branch libraries have to scope out to the system level every time they create purchase order and invoice.

Jennifer

[Leslie St. John (lstjohn-deactivatedaccount)]

In 2.9.0;
Admin->Acquisitions Administration->Funds - the context org unit appears to be sticky but the year is not.
Admin->Acquisitions Administration->Providers - acts very oddly - spinner goes but data does not appear until one of the links, Back or Next are clicked. Then the Providers grid appears (as well as it can considering that it can't display a complete list), however nothing ever appears in the context org unit dropdown although you can click on it and choose. It does appear to scope to the system level.

Our libraries have to scope out to the library system level to order and for invoices also. If these screens were sticky or if a default could be set it would be extremely beneficial.

[Kyle Huckins (khuckins)]

This still appears to be the case in 3.6, though I may be missing something. It sounds like adding a YAOUS would be the way to go for addressing the issue, something like admin.acq.default_context_org. Either one for the whole of the acquisitions admin UI, or separate settings for each desired UI for more granular control.

It's possible future Angular UIs may resolve the issue, though an individual fix would be ideal as it would be easily backportable.

[Tiffany Little (tslittle)]

Just noting that this bug is still valid in the new angular funds/funding sources interface that was merged and targeted to 3.8.

[Galen Charlton (gmc)]

In the context of the new Angular UI, would it suffice to make the OU selector sticky?

[Tiffany Little (tslittle)]

Having a YAOUS for it might make it more consistent, especially with the option to assign that from a higher level rather than relying on individuals.

But having said that, I would be thrilled if they were sticky as an interim solution. Working with the funds/funding sources UI yesterday, the org selector flips back to the workstation each time you change in-page tabs so you're constantly resetting it.

Re: the stickiness -- it was discussed in bug 1873322 as sort of a "part 2" to that bug, but I think only part 1 ended up being committed. So there's some comments over there too if that's helpful.

[Jennifer Pringle (jpringle-u)]

The lack of stickiness/defaults is a significant usability issue in 3.8 for multi-branch libraries. As Tiffany noted the org selector flips back to the workstation every time you move between the in-page tabs.

[Jennifer Pringle (jpringle-u)]

Confirmed still an issue in 3.11

[Jennifer Pringle (jpringle-u)]

This should also apply to the admin interfaces for Distribution Formulas and Claiming