Loans (UXPROD-788)

[UXPROD-1985] Loans: Permissions (Action-based) Created: 12/Aug/19  Updated: 15/Apr/22  Resolved: 15/Apr/22

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

Type: New Feature Priority: P3
Reporter: Emma Boettcher Assignee: Cheryl Malmborg
Resolution: Won't Do Votes: 0
Labels: round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-2527 Item status: Permissions to change it... Open
blocks UXPROD-2528 Item status: Permissions to change th... Open
Defines
is defined by UIU-582 Permissions for change due date Closed
is defined by UICHKIN-152 Permission to backdate check ins Closed
Relates
relates to UXPROD-1828 action-based permissions Closed
relates to UXPROD-1251 Loans: Permissions (Advanced) Closed
relates to UXPROD-3157 Check in - add permission control for... Draft
relates to UXPROD-3158 Users App and Loans - New/Expanded P... Draft
Epic Link: Loans
Development Team: Vega
Kiwi Planning Points (DO NOT CHANGE): 3
PO Rank: 69
PO Ranking Note: Needed in order to have permissions for backdating check ins, checking in claimed items, etc.
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R2
Rank: Grand Valley (Full Sum 2021): R2
Rank: hbz (TBD): R2
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Current situation or problem:
FOLIO provides some loans permissions (view loans, renew loans, change due date, check out, overrides, etc.) based on existing endpoints. Other loans actions do not have their own endpoints and can only be controlled through action-based permissions:

  • Viewing open loans and viewing closed loans (as opposed to the current view loans permission, which makes no distinction if loans are open or closed)
  • Change due date to a date in the past or after a user's expiration date (as opposed to the current change due date permission, which allows any user with that permission to do those things)
  • Backdate check ins (as opposed to the current check in permission, which allows all users with that permission to backdate check ins)
  • check in claimed returned items (as opposed to the current check in permission, which allows all users with that permission to check in claimed returned items)

In scope

  • Determine approach for action-based permissions (if not previously determined)
  • Apply that approach to the above needs

Out of scope

Use case(s)

Proposed solution/stories

Links to additional info

Questions

  • Are there additional permissions needed for loans that are action-based?


 Comments   
Comment by Emma Boettcher [ 12/Aug/19 ]

Feature was split from UXPROD-1251 Closed .

Comment by Erin Nettifee [ 27/Jan/20 ]

Not sure why we didn't rank this, but Duke would rank it as go-live.

Comment by Erin Nettifee [ 17/Mar/21 ]

Changing this from blocked by 1828 to relates to 1828 - we are not waiting for a project-level decision on approach to action-based permissions, so this can and should be ranked and developed as appropriate. Also changed jira status from Blocked to Open.

Comment by Stephanie Buck [ 13/Apr/22 ]

Cheryl Malmborg & Erin Nettifee, the stories defining this feature have been closed. Can this feature be closed as done?

Comment by Erin Nettifee [ 14/Apr/22 ]

I wouldn't close this as done, because the two defining features that are listed were closed as duplicates - there wasn't actually work done.

The root discussion to understand what this (if that's even possible at this point) is in https://folio-org.atlassian.net/browse/UXPROD-1828 - that's the feature for action-based permissions. Way back when, the project had the idea that we would implement "action-based permissions" that are discussed in the comments there. However, it seems to have pretty much died in 2019 and no progress was made, and with Cate leaving the project, no PO that I've talked to has a good sense even of how to define what an "action based permission" is.

The discussion on 1828 essentially led to the acknowledgement that the project has moved away from pushing a central approach to technical design questions towards one where individual teams approach a challenge, propose a design solution, and then other teams can that solution for other feature needs.

I think that all of the stories that are listed as related to this feature should be tied to 3157 and 3158 - so it makes sense to close this, and maybe to even remove those relations just to not add more confusion, and then to prioritize and work those two features. That is my recommendation.

Comment by Stephanie Buck [ 15/Apr/22 ]

Thank you, Erin Nettifee. That is very helpful. I'll close this ticket. Can you help link the related issues to 3157 and 3158?

Comment by Erin Nettifee [ 15/Apr/22 ]

I think they already are, but I will double-check Stephanie Buck

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