Reporting Team Goals for 2025

• Resolve Derived Tables Issues 
  • created modified versions of derived tables, automated them to run daily, and modified queries

• Test Reporting App for Metadb 
  • wrote and published new query for Acquisitions staff to use to manage orders
  • determined permission settings not meeting our needs, so submitted https://folio-org.atlassian.net/browse/UILDP-178 for a new Reporting App User role, scheduled to be released in Trillium
  • working on proposal to develop functionality to create user roles that map to github repository directories

• Explore New Data Sources for Library Analytics 

• • ERM (Electronic Resource Management)   
  • worked with Tom Trutt and Pete Stergion to automate process of cleaning ERM files for use with Tableau and publishing new data quarterly

• Optimize our collection of queries on the cul-folio-analytics GitHub repository
  • modified XX queries
• Created new queries as needed and updated the code in existing queries
  • XX queries created
  • XX queries updated

• Improved report automation, e.g. test Temporal application
  • waiting on automation team

• Consider new reporting applications over DBeaver EE 

• Set achievable goals within reporting team by minimizing project scope creep 

• Contribute to Metadb Software Improvements 

• • Worked with Mike Gorrell from Index Data on data extraction project for Metadb version 1.4 
  • Derived Table updates for each FOLIO software release

• Work with hosting team to optimize data synchronization efficiency (reducing number of tables) for Metadb

• Review and Update Documentation for Queries and Dashboards 

• Update documentation on FOLIO Reporting Confluence website  

• Review and refine supported reports and dashboards with stakeholders 

• Offer CUL Reporting User Group meetings 
  • offered meetings on these topics in 2025
    • Wolfcon 2025 updates

• Co-convene Reporting SIG Meetings 
  • worked with Reporting SIG co-convener to arrange topics and host weekly Reporting SIG meetings for the FOLIO community throughout 2025

• Create standard testing procedures for queries (e.g., verify that it matches data in FOLIO apps); identify certain queries that can identify possible problems; use metadb log; keep records of problems found 

• Create standard testing procedures to verify accuracy of data and reasonableness before and after each reporting database update; (e.g., do record counts fall within expected parameters?); identify certain queries that could be used as test cases before and after an upgrade, coming from various functional areas 
• Test, support, learn more about the Lists App
• PowerBI
• Metadb Data Privacy

Reporting Team Accomplishments for 2024

• LDP to LDP 2.1.0 Update 

• Fiscal Year 24 to 25 Updates 

• Derived Table updates for Folio-Analytics for FOLIO Reporting SIG 

• LDP to Metadb Transition 

• See Metadb Rollout Plan for more details  

• Revising, updating, streamlining all queries and dashboards for Metadb 

• CUL FOLIO Reporting User Group Meetings, Trainings, etc. 

• Retire LDP 

• Retire Virtual DBeaver 

• Assess and Implement CloudBeaver as Virtual DBeaver alternative 

• FOLIO Reporting App Testing with LDP 
• New Data Sources for Library Analytics   
  • Lost Items (FBO) Dashboard 

• • Eusage Dashboard (EBSCO COUNTER Data) 

• • Elaine Dashboards 

• • Springshare (data for reference librarians) data dashboard