Reporting: Analytics and Audit Data Logging for External Reporting
(UXPROD-330)
|
|
| Status: | Open |
| 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: | Unresolved | Votes: | 0 |
| Labels: | analytics, transactdata | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| 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 |
|
Implement the mechanism through which transactions are intercepted within Okapi and redirected to the appropriate message stream/queue. This is one of the key elements of AES: Message Stream processor. Specifically, initial development of AES will utilize the existing Okapi post-filter mechanisms to extract data, to allow development without introducing dependencies to Okapi. This particular story is essentially the refactoring of the AES post-filter implementation into an internal Okapi module. |