Table of Contents

Reporting Team Goals for 2026

  • Move to Metadb software version 1.4
    • once Metadb version 1.4 is released, work with hosting team to set up plans for testing new version on a separate Metadb Test database
    • support reporting users as CUL moves to Metadb 1.4
    • implement new data privacy features available in Metadb 1.4
    • provide information sessions on new features 
  • Test, Develop, and Support Reports for Reporting App for Metadb 
  • Support New Data Sources for Library Analytics 
    • work with Tom Trutt and Pete Stergion to automate process of cleaning ERM (Electronic Resource Management) files for use with Tableau and publishing new data quarterly
  • Expand and Maintain CUL's collection of reporting queries on the cul-folio-analytics GitHub repository
    • create new queries as needed and updated the code in existing queries
    • update queries to reflect updates to Metadb tables after Sunflower and Trillium releases
    • optimize query code to improve performance and reduce dependency on derived tables where possible
    • create modified versions of derived tables for CUL report needs and automate them to run daily
  • Migrate Report Automation
    • waiting on developers to be assigned to a Spring 2026 software development sprint so Reporting Team can test Temporal for report automation
    • continue to support 30+ reports currently automated through DBeaver application
  • Contribute to Metadb Software Improvements 
    • Create Index Data tickets for Metadb software issues as they arise
    • Assess derived table updates needed for each FOLIO software release
    • Work with EBSCO hosting team to optimize data synchronization efficiency (reducing number of tables via table exclusions) for Metadb
    • Work with Lauren Seney, Reporting PO from Index Data, to develop software development plans to support patron privacy and data anonymization in Metadb software development
  • Create, Review, and Update Documentation for Queries and Dashboards
  • Review and refine supported reports and dashboards with small groups of stakeholders 
    • schedule reviews with stakeholder groups in early 2026
  • Offer CUL Reporting User Group meetings 
    • continue to offer CUL FOLIO Reporting User group meetings
  • 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 2026
  • Employ standard testing procedures for code developed when FOLIO and/or Metadb production environments are upgraded
    • For example, verify Metadb data accuracy and make sure it matches data in FOLIO apps, run certain queries that can identify possible problems, use metadb log, and keep records of problems found, and identify certain queries coming from various functional areas that could be used as test cases before and after an upgrade
  • Create and share reports for CUL users using the FOLIO Lists App
    • create lists for users to across various functional areas of reporting
    • create naming conventions for Reporting Team lists so users know they are actively supported and maintained
  • Continue to support Tableau Dashboards for Reporting Users
    • maintain existing dashboards with updates in data fields as new versions of FOLIO are released
    • update queries used as data sources in dashboards as needed
    • update dashboards in response to feedback from users
    • create new dashboards as requested
  • Explore PowerBI Data Dashboard Infrastructure and Test Application
    • get access to Power BI Pro for creating and publishing data dashboards
    • set up workspace for users to gain acccess to CUL PowerBI data dashboards on central Fabric server 
    • create some initial PowerBI reports and dashboards to gain familiarity with this new tool
  • Metadb Data Privacy
    • manage the Metadb Data Privacy subgroup of the FOLIO Reporting SIG, where representatives from several FOLIO institututions, EBSCO, and Index Data are working to improve support for Metadb data privacy
    • work with Reporting PO Lauren Seney on proposal to develop functionality to create Reporting App user roles that map to github repository directories
    • work with Reporting PO Lauren Seney on proposal to develop Metadb software development requirements to support data anonymization, GDPR, and other data privacy feature
    • provide updates on Metadb Data Privacy projects to CUL FOLIO Governance committee


Reporting Team Goals and Accomplishments for 2025

  • Test and Develop Reports for Reporting App for Metadb 
    • wrote and published new query that CUL Acquisitions staff now use to manage purchase orders
    • published demo query for Reporting App and provided training, support, and documentation for creating Reporting App
    • 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
  • Explore New Data Sources for Library Analytics 
    • worked with Tom Trutt and Pete Stergion to automate process of cleaning ERM (Electronic Resource Management) files for use with Tableau and publishing new data quarterly
    • worked with Pete Stergion and reference staff to connect to SpringShare API and provide a new Tableau dashboard on Reference Interactions 
  • Expand and Maintain CUL's collection of reporting queries on the cul-folio-analytics GitHub repository
    • created new queries as needed and updated the code in existing queries
    • updated queries to reflect updates to Metadb tables after Ramsons
    • reduced dependence on derived tables by revising queries to use JSON code extracts
    • optimized query code to improve performance
    • created modified versions of derived tables for CUL report needs and automated them to run daily
  • Expand Report Automation
    • waiting on developers to be assigned to a software development sprint so Reporting Team can test Temporal for report automation
    • delayed by Temporal migration, so will start in spring 2026
    • continue to support 30+ reports currently automated through DBeaver application
  • Consider new reporting applications over DBeaver EE 
    • considered other options, but agreed this is still the best tool for our team to use to create and manage code for report queries, derived tables, and dashboards
  • Contribute to Metadb Software Improvements 
    • Worked with Mike Gorrell from Index Data on data extraction project for Metadb version 1.4 
    • Review hosting team tickets
    • Derived Table updates for each FOLIO software release
    • Work with hosting team to optimize data synchronization efficiency (reducing number of tables via table exclusions) for Metadb
    • Worked with Lauren Seney, Reporting PO from Index Data, to develop software development plans to support patron privacy and data anonymization
  • Create, Review, and Update Documentation for Queries and Dashboards
  • Review and refine supported reports and dashboards with small groups of stakeholders 
    • schedule reviews with stakeholder groups in early 2026
  • 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 code developed when FOLIO and/or Metadb production environments are upgraded
    • For example, verify Metadb data accuracy and make sure it matches data in FOLIO apps, run certain queries that can identify possible problems, use metadb log, and keep records of problems found, and identify certain queries coming from various functional areas that could be used as test cases before and after an upgrade
  • Test, support, learn more about the FOLIO Lists App
    • created and shared 3 lists for Acquisitions staff to use: duplicate holdings, pending orders, and purchase order line notes
  • Set up PowerBI Data Dashboard Infrastructure
    • get access to Power BI Pro for creating and publishing data dashboards
    • set up workspace for users to gain acccess to CUL PowerBI data dashboards on central Fabric server
    • complete PowerBI training
  • Metadb Data Privacy
    • set up the Metadb Data Privacy subgroup of the FOLIO Reporting SIG, where representatives from several FOLIO institututions, EBSCO, and Index Data are working to improve support for Metadb data privacy
    • working with Reporting PO Lauren Seney on proposal to develop functionality to create Reporting App user roles that map to github repository directories
    • working with Reporting PO Lauren Seney on proposal to develop Metadb software development requirements to support data anonymization, GDPR, and other data privacy feature
    • provide updates on Metadb Data Privacy projects to CUL FOLIO Governance committee
  • Accomodating Losses in Reporting Team Staff
    • Reporting Team staff continues to cover work for 2 FTEs whose positions will not be replaced due to austerity measures
    • Reporting Team staff work together to set achievable goals within reporting team by minimizing project scope creep
  • Wolfcon 2025 Conference

    • Presented "Got Data? Introduction to FOLIO Reporting Applications" pre-conference, half-day training session with Scott Perry, University of Chicago

    • Presented "Welcome to the Wide World of FOLIO Reporting" 50-minute information session with Scott Perry, University of Chicago



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 
  • 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


 

  • No labels