Loans
(UXPROD-788)
|
|
| Status: | Draft |
| 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: | circ_po_small | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||
| Epic Link: | Loans | ||||||||||||||||||||||||||||
| Development Team: | Vega | ||||||||||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R3 | ||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||
| Rank: Mainz (Full TBD): | R4 | ||||||||||||||||||||||||||||
| Rank: MTSU: | 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. There are two needed permissions for loans / checkin that do not have associated endpoints:
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 This feature encompasses the first need - a permission control for backdating checkins. In scope
Out of scope{} Use case(s)
Proposed solution/stories
Links to additional info
Questions
|
| Comments |
| Comment by Thomas Trutt [ 25/Jul/22 ] |
|
Id would suggest adding a separate key for backdating on the check-in-by-barcode API. Re: is you could record the actual check-in date/time in the circ log and use the backdated entry for the circ record. This information was helpful in voyager when we had student employees abuse the backdate function, having both pieces of information available. |
| Comment by Erin Weller [ 28/Sep/23 ] |
|
At training, we are telling our students and staff not to back date while checking in. However, we are seeing this misused a lot (staff backdating to avoid late fees). While, we can retrain/discipline staff, it would be wonderful to just have a permission strictly for back dating. The select staff who need it can have it, and everyone else just won't have the option to backdate. Creating a UI solution would be just fine. |