Circ Rules and Loan Policies (UXPROD-789)

[UXPROD-3629] Add metadata object to circulation rules Created: 07/Apr/22  Updated: 08/Feb/24  Resolved: 29/Jun/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)
Parent: Circ Rules and Loan Policies

Type: New Feature Priority: P2
Reporter: Erin Nettifee Assignee: Erin Nettifee
Resolution: Done Votes: 0
Labels: LC-priority1, LC1, enettifee-reviewed, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines CIRCSTORE-410 BE | Add metadata object information ... Closed
defines UICIRC-858 Update record metadata object when sa... Closed
defines UICIRC-790 Add metadata object information (last... Closed
Release: Poppy (R2 2023)
Epic Link: Circ Rules and Loan Policies
Front End Estimate: Large < 10 days
Front End Estimator: Priyanka Terala
Front-End Confidence factor: 90%
Back End Estimate: Large < 10 days
Back End Estimator: Gurleen Kaur1
Back-End Confidence factor: 90%
Development Team: Volaris
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2

 Description   

Current situation or problem:

The circulation rules JSON object does not store a metadata object.
https://github.com/folio-org/mod-circulation-storage/blob/master/ramls/circulation-rules.json

That means that there is currently no way to tell when the circulation rules were last modified, and by what logged-in user. This is a significant concern for larger libraries who may have multiple staff editing circulation rules, especially during initial FOLIO implementation.

In scope

  • Adding the record metadata object to the circulation rules object.
  • Adding functionality in Settings > Circulation > Circulation rules such that clicking Save updates the metadata object
  • Adding any additional functionality needed so that an API update to the circulation rules (PUT /circulation/rules) updates the metadata object
  • Updating the UI such that the metadata object displays. ( UICIRC-790 Closed )
    • Importantly, we only want last update date / last updated by to display - this is because a circ rules object is created when FOLIO circulation modules are enabled, so the creation date / created by information will never be of real use to a library. (E.g., it will always be whatever user account was used for initial system install.)

Out of scope

  • Changes to the circ rule editor itself, other than updating the UI per UICIRC-790 Closed

Use case(s)

  • A large library is implementing FOLIO and has three staff members working on writing circulation rules. Staff member A wants to work on the rules but doesn't want to overwrite staff member B's work. They can see staff member B updated the rules 5 minutes ago, so they know staff member B is likely working on the rules, and they reach out to that person to coordinate work so they don't overwrite each other.
  • A smaller library is implementing FOLIO and has one staff member working on writing circulation rules. That staff member is engaged with their work and then gets pulled away for an IT emergency. When the staff member comes back, they can see on their screen that the last save was several hours ago, and that helps them remember where they were in their work before they were pulled away.

Proposed solution/stories
UICIRC-790: Add metadata object information (last update and by whom) to circ rules editor screen
UICIRC-858: Update record metadata object when saving circulation rules
CIRCSTORE-410: BE | Add metadata object information to circ rules editor screen

Links to additional info

Questions



 Comments   
Comment by Khalilah Gambrell [ 04/Apr/23 ]

Hey Stephanie Buck and Tim Auger. Can we give this feature to Volaris? And to Irina to define requirements?

Comment by Tim Auger [ 10/Apr/23 ]

Khalilah Gambrell yes, we can do that. She is familiar with circulation rules. 

 

Comment by Tim Auger [ 10/Apr/23 ]

Irina Pokhylets we can review and update together to get this to an Open state.

Comment by Erin Nettifee [ 11/Apr/23 ]

Irina Pokhylets Tim Auger I'm glad to see this is getting prioritized. I did leg work on this already and it should basically be ready to go from the UI perspective. There is no backend ticket since you all create those. Kimie did a mockup that I attached to UICIRC-790 Closed . The only step that didn't happen with this was a SIG discussion. I can flag to the SIG that this ticket is being planned for Quesnelia and ask them to provide input if desired.

Comment by Irina Pokhylets [ 12/Apr/23 ]

Thanks, Erin Nettifee
I added BE story CIRCSTORE-410 Closed , not sure that we need input from SIG so far.

Comment by Erin Nettifee [ 29/Jun/23 ]

Tested on Snapshot and looks great - thank you Volaris for getting this done!

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