*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
| 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
- work with EBSCO and Index Data to submit tickets for, test, and support FOLIO Reporting App software development
- expand the number of reports delivered through the CUL FOLIO Reporting App to users
- 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
- documentation pages for both queries and dashboards created, reviewed, updated, and archived on the FOLIO Reporting Confluence site on an ongoing basis
- documentation for SQL queries created, reviewed, and updated in Markdown README.MD files on the CUL FOLIO Analytics GitHub repository on an ongoing basis
- 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
...