Ordering functionality that FOLIO needs to stay competitive (UXPROD-3440)

[UXPROD-4510] Restrict fund use by location Created: 13/Oct/23  Updated: 17/Jan/24

Status: Analysis Complete
Project: UX Product
Components: None
Affects versions: None
Fix versions: Quesnelia (R1 2024)
Parent: Ordering functionality that FOLIO needs to stay competitive

Type: New Feature Priority: P3
Reporter: Joseph Reimers Assignee: Joseph Reimers
Resolution: Unresolved Votes: 0
Labels: loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File 1-fund-locations (2).png     PNG File 2-modal-locations (1).png    
Issue links:
Defines
is defined by MODFIN-337 Add locationIds to fund schema Closed
is defined by MODFIN-342 Add restictByLocations flag to Fund i... Closed
is defined by MODORDERS-968 BE: Location-restricted funds in POLs Closed
is defined by MODORDERS-969 Opening and editing POs with location... Closed
is defined by UIF-482 Designate funds as location use restr... Closed
is defined by UIF-484 Assign locations to restricted funds Closed
is defined by UIF-492 Make location association required wh... Closed
is defined by UIOR-1166 Location-restricted funds in POLs Closed
is defined by UISACQCOMP-171 Create location select modal Closed
is defined by UISACQCOMP-177 Support location-restricted funds in ... Closed
is defined by UIOR-1184 Opening and editing POs with location... Blocked
Potential Workaround: Acquisition units
Release: Quesnelia (R1 2024)
Epic Link: Ordering functionality that FOLIO needs to stay competitive
Front End Estimate: XL < 15 days
Front End Estimator: Alisher Musurmonov
Front-End Confidence factor: 70%
Back End Estimate: Medium < 5 days
Back End Estimator: Serhii_Nosko
Back-End Confidence factor: 80%
Development Team: Thunderjet
UX Lead: Joseph Reimers
PO Rank: 0

 Description   

Current situation or problem: Libraries often associate funds with specific locations (including campuses, libraries, and library locations.) Additionally, many FOLIO users are members of consortia or similar shared systems and need to associate funds with their collections.

Acquisitions units provide an alternative, but can be overly complex and cumbersome and apply more restrictions than needed

In scope

  • Designate funds as being use restricted by location
  • Assign locations to funds
  • (ECS) Assign tenants to funds
  • Error handling when there is a fund-location mismatch

Out of scope

  • Receiving
  • Acquisition units
  • Permissions

Use case(s)

Library has funds exclusively designated to be used in specific places or collections (e.g. Architecture funds exclusively for Architecture purposes). Library wishes to avoid mis-application of Architecture funds to non-Architecture locations, so library location-restricts these funds to the Architecture library.

Library consortium on shared system needs to align their own funds with their own institutions but each institution requires additional, more complex uses of acquisition units. Associating funds to institutions will help streamline overall management while respecting institutional autonomy.

Existing records should not be impacted

Proposed solution/stories

  • Designate funds as location use-restricted.
  • Allow restriction by tenant, institution, campus, library and/or location.
  • Allow a given fund to have multiple allowable locations
  • Enforce location-fund matching during order placement via warning messages when attempting to save
  • Respect Acquisition units: if an Acq unit is involved, then both Acq Unit and Location requirements must be met for save.

Links to additional info

https://miro.com/app/board/uXjVMh40l4w=/?moveToWidget=3458764566655555829&cot=14

Questions


Generated at Fri Feb 09 00:40:28 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.