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

[UXPROD-338] Improve Transactional Data Tracking (RAML, JSON, version) Created: 05/Mar/18  Updated: 19/Jan/19  Resolved: 19/Jan/19

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

Type: Story Priority: P3
Reporter: VBar Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: analytics, transactdata
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-331 Okapi Transactional Data Extraction Closed
relates to UXPROD-335 Shape Okapi Transaction Data for Extr... Closed
Epic Link: Reporting: Analytics and Audit Data Logging for External Reporting
Front End Estimator: VBar
Back End Estimate: Medium < 5 days
Back End Estimator: VBar
Development Team: EBSCO - FSE

 Description   

Ensure that captured transactions are connected to data definitions (i.e RAML interface definitions and JSON Schema defnitions). Including versioning of the data definitions.
When included in historical reporting at a later time, the data definition of the captured transactions may no longer match the current data definitions. Therefore, it is essential to capture data definitions in order to be able to make use of data in the future.



 Comments   
Comment by VBar [ 19/Jan/19 ]

Closed as not needed at this time. Covered elsewhere as data dictionary

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