Loans (UXPROD-788)

[UXPROD-3656] Check in - add permission control for checking in claim returned items Created: 04/May/22  Updated: 07/Jul/23

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

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

Issue links:
Cloners
clones UXPROD-3157 Check in - add permission control for... Draft
Defines
is defined by UICHKIN-130 Permissions for checking in items wit... Open
is defined by UICHKIN-131 Claimed returned: permission to check... Open
Epic Link: Loans
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R3
Rank: Mainz (Full TBD): R4
Rank: MTSU: R4

 Description   

Current situation or problem

FOLIO needs to provide permission control over the ability to check in an item that is marked claimed returned. This is because some libraries want to restrict the ability to discharge a claim returned item to specific staff.

In scope

  • Creation of a visible permission that controls the ability to check-in an item that has an item status of Claimed returned ( UICHKIN-131 Open )
  • Development of a modal message that displays if you don't have the ability to check in that item ( UICHKIN-131 Open )
  • Creation of a new permission set that allows check-in, but does not allow the check in of claim returned items ( UICHKIN-130 Open )
  • Adding the new claim returned permission to ui-checkin.all ( UICHKIN-131 Open )
  • Backend work necessary to support the new permission (jiras to be created by dev team)

Out of scope

  • Adjustments to claim returned UI or workflows

Use case(s)

  • A library wants all items that are claim returned to be manually reviewed before being checked in by a specific staff member. Having the permission would allow staff to ensure that claim returned items are not inadvertently returned to the library when it's not appropriate to do so.

Proposed solution/stories

Links to additional info

Early on, there was a project decision that we needed to define a project-wide approach to action based permissions. However, that did not happen, and a further decision was made that individual features should be prioritized and proceed based on their app's individual needs. See the conversation on https://folio-org.atlassian.net/browse/UXPROD-1828

Questions



 Comments   
Comment by Erin Nettifee [ 21/Oct/22 ]

Stephanie Buck Cheryl Malmborg - I think this is ready for development. The UI stories were written by Emma Boettcher but as far as I can tell I think they are still valid.

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