[UXPROD-3169] In Circulation settings, do not allow deletion of loan policies that have already been used in open, closed and/or anonymized loans Created: 08/Jul/21  Updated: 13/Oct/22

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to CIRC-179 in-use loan policies may be deleted Closed
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2

 Description   

Current situation or problem: As adopters are testing and beginning to implement FOLIO, they are finding that they may create loan policies that are used for loans but then should no longer be used.

While those policies that are no longer in use can be indicated as such by naming, changing a loan policy name can break a circulation rule, and could potentially lead to a messy loan policy list.

Libraries can currently delete loan policies, but there is no check to see if that loan policy has been used in a loan. So if you delete a loan policy while the item is checked out, and the item is then returned, parts of the circulation workflow can break.

So ideally, we'd have functionality that looks like this, once a library decides a policy should no longer be used.

  • Deleting: a library can choose to delete a policy. FOLIO checks to see if the loan policy is referenced in any loan records.
    • If not referenced in any loan records (open, closed, anonymized,), then FOLIO deletes the policy.
    • If referenced in any loan records (open, closed, anonymized,) then FOLIO returns an error message and does not delete the policy.
    • If referenced in any circulation rules, FOLIO returns an error message and does not delete the policy.

The circulation rules editor does tell you if a policy no longer exists, but ideally we would prompt the FOLIO user to edit the circulation rules to remove the policy they want to delete, before deletion occurs.

]In scope

Out of scope

Use case(s)

Proposed solution/stories

Links to additional info

Questions

  • How would a library then get rid of a loan policy that they no longer want to see in Settings? Should we have some sort of "archive policy" function?

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