Change Tracker
(UXPROD-782)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Trillium (R1 2025) | Parent: | Change Tracker |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Dennis Bridges | Assignee: | Dennis Bridges |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | acquisitions, lc-priority4, loc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Release: | Trillium (R1 2025) | ||||||||||||
| Epic Link: | Change Tracker | ||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||
| Front End Estimator: | Khalilah Gambrell | ||||||||||||
| Front-End Confidence factor: | 20% | ||||||||||||
| Back End Estimate: | XL < 15 days | ||||||||||||
| Back End Estimator: | Khalilah Gambrell | ||||||||||||
| Back-End Confidence factor: | 20% | ||||||||||||
| Development Team: | Thunderjet | ||||||||||||
| PO Rank: | 118 | ||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||
| Description |
|
Current situation or problem: When records are deleted from the system there is no way for the user to know they once existed or who deleted them. This means the library looses information that could be required by auditors Essentially a "request for deletion" function In scope TBD Out of scope TBD Use case(s)
Proposed solution TBD - Possibly allow user to request deletion of record from other user or allow other system to request deletion of record from other user by leveraging the task manager application Links to additional info Questions |
| Comments |
| Comment by Khalilah Gambrell [ 14/May/23 ] |
|
Raman Auramau - I assume the delete record approach we have discussed could be leveraged to support this feature? |
| Comment by Dennis Bridges [ 08/Sep/23 ] |
|
It might be a more complete solution to use a task manager application to deliver this workflow. There is a separate feature for being able to identify what has been deleted. This feature is focused on how things get deleted in the first place. Currently FOLIO provide specific delete permission for acq records. Meaning the library can already strictly limit the number of users that can perform this funciton. Secondly it could more advantageous to invest in task manager funcitonality for accommodating delete requests. This has been assigned to Ramsons but may not actually be that high a priority given the workarounds that exist. |