Circ Rules and Loan Policies (UXPROD-789)

[UXPROD-3455] Allow opening of circulation policy directly from circulation rule editor Created: 15/Dec/21  Updated: 13/Jun/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Circ Rules and Loan Policies

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: enettifee-reviewed, ui-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Circ Rules and Loan Policies
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

Current situation or problem:
When a librarian is reviewing active circulation rules, they often find a policy (loan, request, notice, overdue or lost item) that they'd like to be able to edit.

Current functionality means that when the librarians find the policy they'd like to edit, they have to leave the circulation rule pane, go to the relevant area of Settings > Circulation, locate the policy, make the appropriate edits, and then return to the circulation rule editor if desired.

Desired functionality is that the librarian can click the name of the relevant policy from the circulation rule editor and have it immediately open the policy in an edit view. That way the librarian could click the policy, make the edits, save the policy and then immediately return to the circ rule editor.

In scope

  • Adjusting circulation rule editor behavior - currently, any click in the editor presents the circulation policies insert modal, including clicking on the name of a valid policy in an existing rule.

Out of scope

Use case(s)

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Erin Nettifee [ 15/Dec/21 ]

Note that this feature needs a lot of work before it could be potentially considered for development - just capturing it now to reflect a convo in Slack with an adopter who found this in Felix's circ rule design proposal from 2017. It doesn't appear to have ever made it into Jira for discussion.

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