Change Tracker (UXPROD-782)

[UXPROD-4125] Inventory app | Audit log/Change tracker v1 Created: 13/Mar/23  Updated: 29/Jan/24

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: Sunflower (R3 2024)
Parent: Change Tracker

Type: New Feature Priority: P3
Reporter: Khalilah Gambrell Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: LC-priority2, SolutionArchitecture, cataloging, galileo, loc, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-910 Change Tracker Open
relates to UXPROD-3215 Display a history of edits for the Or... Closed
relates to UXPROD-4126 MARC authority app | Audit log/Change... Open
Epic Link: Change Tracker
Front End Estimate: XXL < 30 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: Jumbo: > 45 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Spitfire
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1

 Description   

As a cataloger I want to be able to view/track updates to 

  • Instance record 
  • Bib record 
  • Holdings (MARC) 
  • Holdings (FOLIO) 
  • Item record 

Changes should include any updates

  • made a.) by a user manually, b.) via bulk-edit, c.) via data import, d.) another app/module (i.e. Orders) 
  • AND if the connected SRS is updated then record changes too 

v1 expectations

 



 Comments   
Comment by Erin Nettifee [ 15/Mar/23 ]

Khalilah Gambrell can these get labeled in such a way to allow an implementing library to track change tracker work across apps? I know at Duke we have a requirement for this in multiple different apps and record types.

Comment by Khalilah Gambrell [ 15/Mar/23 ]

Hey Erin Nettifee. What about these two options? 

  1. Link to the Change Tracker epic
  2. Add a label
Comment by Ann-Marie Breaux (Inactive) [ 16/Mar/23 ]

I definitely vote for labels. I could go either way on linking to the Change tracker Epic

Comment by Erin Nettifee [ 16/Mar/23 ]

I would lean towards a label since if this is being broken out to be done by individual POs for their apps rather than managed by one PO then I think that provides more flexibility for how each PO manages their team's work.

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