Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.





Attendance & NotesSharon

Attendance & Notes

  • Today's attendance-taker: Linda Miller
  • Today's note-takers:  Team Leads for project updates
Test Data Updates (Reminder)All

FOLIO Reporting developers and Reporting SIG members are encouraged to use this new page to share test data cases they have entered into FOLIO reference environments to keep us all aware of what data to expect when we test our queries.

Report Ranking (Reminder)


New Report Clusters are added on a regular basis, so it is important to make sure your institution is reviewing these clusters and ranking them to establish report development priorities. If you rank reports for your institution, please follow the instructions below. If someone else ranks, please pass this information along to that person so your institution's vote can be included.

  • Action =>> Please review Reporting SIG-All Report Clusters (55 issues) in JIRA and RANK each report cluster for your institution (R1-R5)
  • For reporting, institutions only need to rank the UXPROD Report Cluster JIRA issues. All reporting requirements, which are captured in REP-XXX issues, roll up to the UXPROD Report Clusters. Report clusters cover one or more report (REP-XXX issue) requirements.

Excel Views Follow-upNassib, Stefan

Excel Views: follow-up from Nassib on presentation by Stefan last week on Excel views

  • generally, using Excel as a database tool with LDP is fine with the LDP
  • LDP guide explains that using views with LDP is not recommended, however
  • LDP is not a data warehouse, it provides software that you can deploy on your own to run a data warehouse
  • Views run the query again, and can present performance issues in layered reporting queries with large tables
  • Materialized views store the query result
  • Views introduce dependencies that can block database schema changes
  • With Metadb (the next version of LDP), schema changes can potentially be made at any time
  • Derived tables are similar to materialized views

Other approaches to automating report distribution:

  • creating local derived tables that you update automatically on your LDP may be a better way to provide a group of users with a specific report dataset
  • your institution can create its own local schema(s) in addition to the "local" schema

Updates and Query Demonstrations from Various Reporting Related Groups and EffortsCommunity & Coordination, Reporting Subgroup Leads

Project updates

Reporting development is using small subgroups to address priorities and complete work on report queries.  Each week, these groups will share reports/queries with the Reporting SIG.  Reporting development team leads are encouraged to enter a summary of their work group activities below.

Reporting SIG Documentation Subgroup

FOLIO Reporting development

  • Daily Snapshots will only be kept for 2 weeks
    • Starting to keep folio snapshots for  2 weeks now; contact Nassib if you want specific dates saved off
    • Be sure to ask Nassib to save off a snapshot (in advance, before data are entered) of a particular dataset you entered on a particular day; he will probably use a naming convention such as “_save” for these custom snapshots
    • Sharon asked Nassib to save the datasets documented on the Test Data Updates to FOLIO Snapshot Environments page in the Reporting SIG wiki
  • Track progress via recent pull requests, featuring contributions by members of the reporting community:

RA/UM Working Group

MM Working Group

  • No news to report this week.
  • Working group uses this spreadsheet to track JIRA issues, priority, and reports needed.

ERM Working Group

RM Working Group

  • report development planned for FOLIO-Analytics Release 1.1
    • ACRL expenditures, title count, volume count, e-resources count
    • subscriptions query
    • fund query
    • claims query
  • for latest updates, see RM Prototype and Query Development Status

External Statistics Working Group

  • ACRL query set to be targeted for FOLIO-Analytics 1.1 release
  • new organizational/tracking scheme for JIRA, with pointers to queries in folio-analytics repository
  • New organizational structure for External Statistics reports
    • external statistics reports (e.g., ACRL) typically require running queries from different functional reporting areas
    • these reports will be captured in JIRA under one UXPROD-XXXX report cluster issue, then the descriptions will point to each of the queries required to run them on the folio-analytics repository
    • institutions will need to rank each of these 8 new UXPROD-XXXX report cluster issues
    • each reporting development team will take responsibility for the queries in their area for the external statistics clusters

Topics for Future MeetingsAll

Next meeting: Would one or two members be able to share their institution's Reporting Rollout Plan?

Review and update Topics for Future Reporting SIG Meetings 

  •  A test Action Item (Ingolf)