Reporting: Analytics and Audit Data Logging for External Reporting (UXPROD-330)

[UXPROD-1707] Data Change Audit Trail Report Created: 17/May/19  Updated: 08/Nov/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Reporting: Analytics and Audit Data Logging for External Reporting

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: VBar
Resolution: Unresolved Votes: 0
Labels: reporting, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Reporting: Analytics and Audit Data Logging for External Reporting
Development Team: EBSCO - FSE
PO Rank: 28
PO Ranking Note: CB: Leaving rank at calculated
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R5
Rank: Lehigh (MVP Summer 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Data changes are captured by the system and can be reported on a weekly basis that can be viewable by individual users. Date and user who changed it.

We already have some audit trail infrastructure. The scope of this feature is to bring that to completion so that it provides value to FOLIO users.

NOTE: This is distinct from the Change tracker feature ( UXPROD-910 Open ) in that it is more of a report (not clear if it will be an in-FOLIO or data lake/warehouse report)



 Comments   
Comment by Kristin Martin [ 12/Jul/19 ]

The most critical part of this feature is the logging of data. If FOLIO does not log data, there's no way in the future to run reports on it.

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