Reporting: Build Misc Functionality to Support Reporting (UXPROD-943)

[UXPROD-945] Reporting: Reporting SIG Data Warehouse Reference Implementation Created: 13/Jun/18  Updated: 16/Sep/20  Resolved: 31/Aug/18

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Reporting: Build Misc Functionality to Support Reporting

Type: New Feature Priority: P2
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: reporting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-971 Reporting tools confirmed for use wit... Closed
Duplicate
is duplicated by UXPROD-864 Create a reference data warehouse Closed
Epic Link: Reporting: Build Misc Functionality to Support Reporting
Analysis Estimate: XXL < 30 days
Analysis Estimator: Holly Mistlebauer
Front End Estimate: XXL < 30 days
Front End Estimator: Holly Mistlebauer
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
Back End Estimator: Holly Mistlebauer
Estimation Notes and Assumptions: New development team will be put together to do this work.
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R3
Rank: Lehigh (MVP Summer 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

The Reporting SIG has submitted a proposal for a Reporting SIG Data Warehouse Reference Implementation.

The first step (Phase I) of this project is represented by another epic, so the scope of this feature is the remaining work outlined in the proposal:

  • Phase I: Data Lake
    • OKAPI changes to flow data into Data Lake - This is changes to the folio code base and is represented by epic UXPROD-330 In Progress
    • Reference implementation of flow into Data Lake
    • Functioning project test environment for Data Lake
  • Phase II: Data Warehouse
    • Reference implementation: load from Data Lake to Data Warehouse
    • Decision - data structure for warehouse:
      • Does the JSON support in PostgreSQL allow us to manipulate data as we need for reports?
      • Or must we convert to normalized relational structures?
      • Trade-off involves large amount of implementation time.
    • Confirm reporting tools working with Data Warehouse (or Data Lake if we are really lucky)
      • Which reporting tools can make use of the JSON extensions in PostgreSQL?


 Comments   
Comment by Sharon Beltaine [ 21/Jun/18 ]

The Reporting Data Warehouse is an overall higher priority than in-app reports because it can be used to create ALL reports at Go Live. This is a core part of FOLIO infrastructure.

Comment by Holly Mistlebauer [ 24/Jul/18 ]

Description from UXPROD-864 Closed , which was a duplicate of this issue

Proposal: https://docs.google.com/document/d/10UveyHmMOUGyFjW36C8bK3NBEqoxKzDR7Pb9hDvDfy8/edit?usp=sharing

Includes:
-Structure JSON documents into format that can be used by reporting applications (e.g. BIRT). The most common format for data analysis is SQL.
-Other tasks as defined in proposal.

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