[UXPROD-330] Reporting: Analytics and Audit Data Logging for External Reporting Created: 05/Mar/18  Updated: 17/May/19

Status: In Progress
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2019

Type: Epic Priority: P3
Reporter: VBar Assignee: VBar
Resolution: Unresolved Votes: 0
Labels: analytics, auditing, mandatory, reporting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-943 Reporting: Build Misc Functionality t... Open
Epic Name: Reporting: Analytics and Audit Data Logging for External Reporting
Development Team: EBSCO - FSE
Score: 33.75
Start date (migrated):
End date:
Epic Color: ghx-label-2

 Description   

Functionality needed to capture folio data and audit trail to feed external data lake. Institutions will need to host own data lake and reporting/bi solution, but once they do, they will have access to all FOLIO data plus information about changes (e.g. who changed what and when). This epic is a pre-requisite for the Reporting SIG Data Warehouse Reference Implementation ( UXPROD-943 Open ).

The audit-data component of this is distinct from the in-FOLIO Change Tracker ( UXPROD-782 Open ).

----------------
In Madrid, it was decided that we would prioritize analytics over in-app reporting.



 Comments   
Comment by Cate Boerema (Inactive) [ 06/Jun/18 ]

VBar, per your suggestion, I made audit trail and analytics a single epic again. Please adjust wording as-needed.

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