Library Data Platform (LDP) Beta (UXPROD-1128)

[UXPROD-1873] Support for writing ad hoc reports Created: 16/Jan/18  Updated: 16/Sep/20  Resolved: 16/Jul/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Library Data Platform (LDP) Beta

Type: New Feature Priority: P2
Reporter: Michelle Paolillo Assignee: Nassib Nassar
Resolution: Done Votes: 0
Labels: NFR, ldp-platform, mandatory, personal-info, po-mvp, reporting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to REP-140 AdHoc reports in folio Closed
relates to REP-141 Reports linking ILIAD and others Closed
relates to REP-142 AdHoc reports for troubleshooting Closed
relates to REP-140 AdHoc reports in folio Closed
relates to REP-141 Reports linking ILIAD and others Closed
Epic Link: Library Data Platform (LDP) Beta
Back End Estimate: XXL < 30 days
Back End Estimator: Nassib Nassar
Development Team: Reporting
Report ID (pre-May 2019): ID011
Report Contact(s):
Michelle Paolillo, Sharon Beltaine
Report Functional Area(s):
Import and Export
PO Rank: 119.8
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

The goal of the Reporting SIG is to include all of the FOLIO data attributes needed for reporting in the LDP (Library Data Platform). Support for true "ad hoc" reporting cannot be fully realized until all FOLIO applications are developed, as including a data attribute in the LDP requires that the data attribute first exist in a given FOLIO application. Support for ad hoc reporting will grow and mature as each of the FOLIO applications do the same.



 Comments   
Comment by Nassib Nassar [ 16/Jul/19 ]

Support for writing ad hoc reports was among the basic requirements expressed by the Reporting SIG and addressed by the LDP architecture. However, there is some subtlety to this requirement, as it can imply to varying degrees:

1. A flexible query language

2. A flexible data model

3. A comprehensive data model

The LDP supports SQL as a query language, which is extremely flexible. The data model is a (relational) star schema, which is fairly flexible but to some extent balances flexibility with another requirement: ease of use. The comprehensiveness of the data model will be determined by development resources, but in principle the LDP aims to be fairly comprehensive.

Support for ad hoc reports as a platform feature may be considered as already implemented, and this issue can be closed.

The comprehensiveness of the data model can be considered in a separate issue, which should also define what FOLIO apps are to be included in the scope, given that app development is not limited by FOLIO.

Comment by Sharon Beltaine [ 12/Aug/19 ]

Reporting SIG: Some ad hoc reports using data from the LDP may use personal info, making them not compliant with GDPR. We need to consider the impact of this as the LDP software is developed. See closed issues REP-140 Closed , REP-141 Closed , and REP-142 Closed for more information (closed as duplicates).

Comment by Sharon Beltaine [ 12/Aug/19 ]

UXPROD-1873 Closed covers this issues, so they are being closed as duplicates.

Comment by Nassib Nassar [ 12/Aug/19 ]

This issue is in the LDP Beta epic, which means scheduled for development, and it was closed as being completed. If it is being reopened to discuss personal data, let's move it to another epic such as https://folio-org.atlassian.net/browse/UXPROD-1910 or create a new issue for this.

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