Page Comparison

• Considerations:

• • Key requirements:
    • Reporting SIG members have repeatedly communicated the need for access to all FOLIO data for reporting purposes.
    • Unlike traditional ILS systems, FOLIO will not support SQL access to its internal operational database.  Even if it did, there is no requirement that FOLIO modules use the same database, which means that table joins on the operational database(s) may not work or may break severely in the future.
    • Reporting analysts want an easy and familiar query model, and one that works with common reporting tools.
    • Reporting analysts will want queries to run efficiently.
    • Many reports have been ranked by institutions for "go live (MVP)", which means that they will have to be written and debugged within the next few months.
  • Challenges and constraints:
    • The number of interfaces/tables in FOLIO has now grown to more than 180 and continues to increase.  Although ETL for most of them is relatively simple, synchronizing such a large number of tables reliably on schema changes requires very active coordination with FOLIO, which so far has not proved to be possible.
    • LDP critical dependencies on FOLIO core development which have been requested and flagged as critical beginning in late 2018 will likely not be addressed until mid-2020 or beyond, based on discussions with the FOLIO capacity planning and project management groups.
    • FOLIO is requesting that "go live (MVP)" features be

• • • completed by January 2020, to be released in Summer 2020.
    • Future developer resources appear to continue to be roughly

• • • 1 FTE or less on average, consisting of several part-time developers.
• LDP 1.0 proposed core features, for "go live (MVP)":
  • Support for ad hoc, cross-domain queries for all, or a very large proportion, of FOLIO data extracted from storage modules.  We would ask this working group to help us determine, in the near future, the definition of "all FOLIO data" required for inclusion in the LDP.
  • Include MARC records extracted from FOLIO SRS and transformed for easier querying.
  • Historical data will be retained in the LDP but not transformed into a single schema.
  • LDP database recommended to be refreshed once per day from the FOLIO operational database.
  • Support for optional anonymization of personal data.
  • Implementation guidelines (documentation) for local tables.
  • Support for PostgreSQL and Redshift database systems.
  • Proposed data model design for LDP 1.0.
• (1) Historical queries using a single schema, (2) ETL, and (3) full relational or star schema are tentatively planned for later releases of the LDP but are dependent on the identified critical dependencies and availability of developer resources.
• The test database is currently using the proposed data model design for LDP 1.0.  Additional tables will soon be added to support writing the prioritized report queries.  Our developers will try to assist with writing report queries where needed.

Demonstration of how to contribute a new SQL report query--or a modification of an existing query--using the shared community space in GitHub that has been set up for this purpose.

Refer to Contributing report queries to ldp-analytics for written instructions.

Shall we build these reporting data models next?

1. Circ Item Detail:https://wiki.folio.org/display/RPT/Circulation+Item+Detail+Report+Prototype
2. Services Usage:https://wiki.folio.org/display/RPT/Services+Usage+Report+Prototype
3. Shelf List Location: https://wiki.folio.org/display/RPT/Shelf+List+Location+Report+Prototype

Questions:

• What do RPWG members think of these (above) as our current highest priorities?
• Would the prototype developers like to develop the SQL queries for each of these?

Future Topics:

• Definition of "all FOLIO data" required for inclusion in the LDP.
• Evaluate the data model of the LDP's MARC implementation.
• Identify representative report queries on MARC records.

Next meeting date: