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

[UXPROD-335] Shape Okapi Transaction Data for Extraction Created: 05/Mar/18  Updated: 06/Nov/18  Resolved: 06/Nov/18

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: Hongwei Ji
Resolution: Done Votes: 0
Labels: analytics, transactdata
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-1287 Advanced Message Queue Business Logic... Open
blocks UXPROD-343 Partition Transactions into Kafka Topics Closed
Relates
relates to UXPROD-331 Okapi Transactional Data Extraction Closed
relates to UXPROD-338 Improve Transactional Data Tracking (... 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   

This is the first level pre-processing of transaction data.

The following criteria are to be applied.

  • sensitive (e.g. authentication transactions) are to be excluded.
  • the tenant context of the transaction so that it can easily and efficiently be used to partition data by tenant if required.

The implementation is agnostic as to whether the transactions are managed externally to Okapi (e.g. post- filters) or internally (OKapi AES).

Deliverables may include normalized metadata to be associated with each transaction.



 Comments   
Comment by Hongwei Ji [ 06/Nov/18 ]

Per team discussion, mask the password within AES.

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