Page tree
Skip to end of metadata
Go to start of metadata

This is a list of topics the Reporting SIG is considering for future meetings.

StatusPossible DateTopicContactsNotes
ScheduledJune 8July Reporting FOLIO Forum Demos of Report Querys from RA, MM, and RM subgroup teamsSubgroup LeadsAs part of our July Reporting FOLIO Forum presentation, we would like to provide some nice demonstrations of running queries against the LDP Reference Environment. Specifically, we would like to demonstrate running one query from each of these reporting areas: RA/UM, MM, and RM (ERM is not yet ready for demos). To prepare for this presentation, we'd like someone from each of these subgroups to do a trial run of showing a sample query at the Reporting SIG meeting on Monday, June 8.
ScheduledJune 15Recategorizing REP IssuesSharon

We'll review reports that have been categorized as External Statistics to move them into existing Reporting Subgroups for development. Import/Export and Consortia Reports also need to be reviewed this way.

TBDJune 22Schedule "Quick Demo" meeting for Reporting Tools Analysis
requested by Tod Olson
TBDTBDEntity Relationship DiagramsAngelaJean Pajarek has reqested a demonstration showing how the entity-relationship diagrams are built
Developing a Reporting FAQ page

Several basic questions about reporting came up during the WolfCon 2020 sessions. It would be helpful to have an FAQ page we can refer people to when these questions come up, e.g.,

  • what is the data loading speed of the LDP?

TBD1/6/20How to show data from repeatable fields in the LDPChristie Thomas
  • repeatable fields will be served to the LDP as arrays in the data column that preserves the original Javascript object in FOLIO; a JSON extract path is used to extract this data; we will review this to discuss possible alternate ways to show this information in the LDP in a future Reporting SIG meeting
TBD1/13/20Ranking for New UXPROD Reporting Cluster issuesSharon, Vandana, AngelaWe have several new JIRA issues we have created for Reporting Clusters that we need re-rank for the next round of MVP. 
TBDTBDGDPR requirements and LDP or In App ReportsIngolf

The Data Privacy Group is taking another look at reports that have been identified as needing to be developed in the apps because there is new information on GDPR requirements that may allow some of them to be LDP reports. They will update the Reporting SIG on their findings

TBDTBDLDP SysOps Group: UpdatesLDP SysOps Group MembersUpdates from members on how it is going to have the LDP hosted versus setting it up on one's own.
TBD9/30/19Integrations and ReportsAllIntegrations - What do we do about reports that involve integrations like Ares, ILL, and Borrow Direct?
Scheduled9/30/19MM Cluster ReviewVandana, Vandana will talk about MM clusters
TBD8/12/19Metadata ManagementScott Perry, Laura Wright, Charlotte WhittReview Metadata Management under consideration for moving from in-app to LDP data warehouse.

Stray Reporting Features

Vince Bareau

Sharon and Nassib will provide an update on the following stray reporting features.

Stray Features

UXPROD-1100: CQL Support for Audit Module

UXPROD-358: Edge API for Acquisition Data Enhancement

7/15/197/15/19Review and Prioritize LDP Reporting Feature Requests in JIRAAll
7/15/197/15/19Custom fieldsVandana

Custom Fields

-need use cases

DONE7/1/19RA In App Vs DW Reports UpdateAngela, Joanne

review recommendation for RA in app vs DW reports

DONE7/1/19Data Privacy UpdateIngolf, Nassib

-need to consider data privacy when evaluating in app vs dw reports

-what personally identifiable information is needed in any LDP reports?

-who from Reporting SIG can help review reports for personally identifiable information?

ongoingall meetingsCommunication of and Agreement on Report Development Order for RPWGALL
ongoingall meetingsIn-App Reports: Refine Requirements, Confirm DevelopmentPO and Report Requester for each in-app report

This will be an ongoing part of Reporting SIG meetings until in-app report definition is clearer and both PO and report requester have a shared understanding of who will complete the report and what it will do.

DONETBDAdding Reporting Features to JIRASharon, Nassib, Holly

Review process for adding reporting features to JIRA (see wiki page)

Review all items on Reporting Functionality worksheet and move them into the appropriate location in JIRA

DONE4/15/1FOLIO Face-to-Face meeting plansAll

FOLIO Face-to-Face meeting plans -  

June 17-19 in DC, $100 registration fee

120 attendees is the target

-hotel registration must be done by May 11

-Location of June meeting: DoubleTree by Hilton Hotel Washington DC - Crystal City,

300 Army Navy Drive, Arlington, VA 22202

-large WolfCon Conference is planned for January 2020

Working document for the Face to Face meeting:

Goals for PC/Conveners -

  • Settle on what groups/individual should plan to attend

  • Discuss and decide on meeting times/organization

  • Identify any significant gaps in the program

Confirmed4/29/19Data Privacy for FOLIO ReportingAll

Data Privacy for the LDP Data Warehouse

-need to form a subgroup of the Reporting SIG to work on Data Privacy for Reporting

-capture "Reporting Data Privacy" requirements and issues in the Reporting SIG wiki

-what data should be removed from extraction as we build the LDP Reporting Data Warehouse?

-request that Reporting SIG make a set recommendations on approach to anonymizing data

-European standard for GDPR

-capture in JIRA as an LDP feature?

-build survey about current practices

-may need interaction with UM and Privacy SIGs

-may need to bring to Product Council

Confirmed4/29/19Impact of Custom Fields in Apps on Data warehouse DevelopmentAngela, Nassib

SMEs in our functional areas are asking how we will report on custom fields that are being included in FOLIO applications. Let's explore how to do this.

-process of building up data model works for standard reports, but what about new apps

-hoping that this group will continue, that reporting efforts will continue beyond Phase 1 day

-but it seems to have implications for both database schema and data load scripts

DONE12/17/18FOLIO reporting database for eUsage and ERM dataAnnika Schroer

FOLIO eUsage App

-application will enable harvesting, entering, storing, and providing COUNTER Usage Data

-Bjorn Muschall, Kirstin Kemner-Heek

TBDOrganization of reporting tickets in JIRA: 5 EpicsSharonWe'll review the 5 Epics that form the umbrella for all reporting-related tickets in JIRA to better understand what they cover and to consider whether or not there's more to add (e.g., reporting functionality goes where?)
to be confirmed1/21/19Remaining In-App JIRA issues to reviewHolly, Sharon

In-app reports for Scott Perry at UChicago.

Sharon update on discussing ARES reporting with UI developer Darcy Brancini.

Confirmed1/7/19Report Candidates for Reporting FunctionalitySharonSharon will review list of candidates to recategorize as "reporting functionality" instead of individual reports on the Reporting SIG Master Spreadsheet.
to be confirmed1/14/19Review of In App reporting with Filip, UI designer
-discuss possible candidate for a pilot area to implement in app reporting functionality, such as user management; discuss timing, scope, etc.; best to look for an area where ad hoc reporting is needed
to be confirmed1/21/19Next update from the Reporting Prototype Subgroup


FOLIO Export Function for Tables: recheck on progress

  • in what apps will it be implemented in FOLIO?
  • will the "Export to CSV" functionality be consistent in the UI?
  • demo of progress

In-App Report Review

-do they meet our expectations?

-are the priorities correct?


Oct 1 Reporting SIG meeting

-How to Assign yourself to your reports in JIRA

-Holly's overview of the upload

-Holly's review of how to use JIRA filters to find your reports

-next steps for Report Protypes

??New schedule for Data Warehouse

DONE8/27/18?JIRA interface to and tagging for data warehouse reports ("dwreports") and Consortia SIG reports.Holly, David Dahla new interface to the data warehouse reports in JIRA is being drafted, and we are looking at ways to include the Consortia SIG reports; in this meeting, we will look for Reporting SIG feedback on both of these
??Develop reporting requirements checklist for Product Owners to detail data structure needs for data warehouse; related to Microservice Certification standards; Accessibility SIG is using this approach

Review dwreports in production JIRAHollyreview
??Reports and the MARCcat AppTiziana

Sept 10update on Report PrototypingWorkgroup

Sept 10Reporting DataWare Design updateNassib
?8/27/18?Updates on reporting JIRA ticketsNassib, Vince

Nassib Nassab - Reporting: Reference Implementation UXPROD-943

Vince Bareau - Reporting: Data Lake UXPROD-330

??Prioritize all Data Warehouse reports ("dwreports")Holly, Sharonafter determining how we will track the progress on our reports that use the data warehouse, we will need to add criteria to capture the priority of each report
??ERM Reporting

Kirstin Kemner-Heek

ERM Reporting
to be scheduledto be scheduledWhiteboarding session with Metridoc to design Data WarehouseJoe Zucca, Nassib Nassar


will require several meetings

Data Warehouse Design RequirementsAll

The next step for the Reference Data Warehouse is to bring our request to Technical Council for their thoughts on design of the infrastructure to build it. We'll need to communicate our design requirements, so we'll take a look at what's most important to include.



will require several meetings

Reporting Data Element VerificationPOs and SIGs in RM, RA, and MMMeetings with POs and SIGs to verify availability of data elements for all reports in the Reporting SIG Master Spreadsheet. If Data Elements not available, work with PO for that functional area to generate user story and JIRA ticket to include gaps and/or missing data elements.
To be scheduled?Reporting Certification for Microservices
consider what microservices architecture needs to be present to "certify" it for reporting
To be scheduled?Capturing Historical Data for ReportingData Migration SubgroupHow do we approach the issue of data migration for historical reporting purposes? Do we add historical data to the data lake as a separate data warehouse? Do we bring historical data into Folio?
Best Reporting Tools to use for FolioAll
To be scheduled
Tags Subgroup UpdateSimona Tabacaru
To be scheduled
Changes to ARL annual reportingTod Olson
To be scheduled
Data Dictionary for Folio Reporting
data storage units define their JSON schema; may be able to generate dictionary automatically (Tod Olson); consider Lunrjs to get JSON; talk to POs about data dictionaries for their areas (e.g., loans)


Oct 1 Reporting SIG meeting

-How to Assign yourself to your reports in JIRA

-Holly's overview of the upload

-Holly's review of how to use JIRA filters to find your reports

-next steps for Report Protypes


Prioritizing Reports

Assigning Yourself to Reports in JIRA


FOLIO Export function for tables of data

  • Holly gave a demo of current state of "Export to CSV" function for Loans and Fine/Fees
Holly-check in with Holly on the status of this
DONE10/22/18Overview of GlintNassib Nassar
DONE8/6/18Reporting Needs for Consortia SIGDavid DahlDavid Dahl and other members of the Consortia SIG will attend the Reporting SIG meeting to discuss consortial reporting needs.
DONE8/13/18Review of University of Penn Libraries Metridoc Data Farm Project: Open Source Data WarehousingJoe Zucca, UPennSee
DONE7/23/18Review of JIRA Tickets for ReportingHolly, SharonHolly and Sharon to walk through current reporting-related tickets being created in and being migrated to the FOLIO JIRA Ticket system
DONE6/25/18Feature Prioritization and Gap analysisHollyWe will review results for gap analysis on reporting-related topics on the Feature Prioritization spreadsheet being ranked by first implementers this week. We will focus on in app reports, data warehouse, and data elements for the data model.
DONE6/18/18Next Steps for In-app ReportingHolly MistlebauerHolly is stepping in as Interim Product Owner for Reporting until Product Council assigns a permanent Reporting PO. She will be joining us for Reporting SIG meetings and working with other Product Owners on reporting issues. Today, she will discuss next steps for in-app reporting.
DONE6/18/18Add reporting example links to Reporting Requirements SpreadsheetSharon, HollyPlease take a second look at the reports you have identified in the Reporting Requirements spreadsheet to make sure there is an example report linked. The examples are proving quite useful for the development of JIRA tickets to generate reporting functionality in FOLIO.
DONE6/11/18BibControlIngolf Kuss, Klaus Hoverath

June 11th- A presentation on BibControl will be given by Klaus Hoverath of Triangle Solutions, a company specializing in providing data warehouse, ETL, OLAP and Business Intelligence Solutions. . Their clients are 70% to 80% libraries and that he has currently between 30 and 40 libraries as clients, which are part of the GBV or hbz network . With BibControl, he is a partner of OCLC. See Triangle Solutions flyer for more information.

DONE6/4/18Draft Data Warehouse Proposal ReviewSharon BeltaineJune 4th - We will review and discuss the draft of the Data Warehouse Proposal to be presented to Product Council on Thursday, June 7.
DONE5/14/18Indepth review of session notes from WolfConAll
DONE4/30/18Inventory Data Elements and ReportingChristie Thomas (MM SIG)

Review data elements identified by MM SIG and Data Migration Subgroup from a Reporting perspective. What's missing? How does the data mapping work? What's been identified so far?

DONE5/7/18Data Lake JIRA Ticket Conclusions

Jeremy Huff (TAMU Dev) and Frances Webb (Cornell Dev) joined the Reporting SIG meeting on 4/9/18 to discuss JIRA ticket OKAPI-570 , which had been entered into the Folio Issue Tracker to capture recent discussions about concerns related to the approach taken in JIRA tickets UX-PROD-331 and UX-PROD-332. These are development tickets for building the technical infrastructure to support Folio Data Lake environments. OKAPI-570 details concerns and offers alternative proposals for the implementation of reporting features residing in OKAPI’s core, dereferencing at the time of report generation, the impact of schema mutation on report creation, and implementing message queues as an internal component of reporting and/or OKAPI core.

Since then, Vince Bareau has made comments on each of the issues raised in JIRA ticket OKAPI-570, the developers have discussed these issues, and Jeremy Huff has added Conclusions as a follow-up to each of the issues raised in the Google Doc associated with JIRA ticket OKAPI-570

We will review these Conclusions and see if there are any additional questions.

DONE4/23/18Loan Reports with Loan PO Emma BoettcherEmma BoettcherReview reports related to loans to identify gaps, increase understanding, etc. Please attend if you have Circ Loan Reports in the requirements list.
DONE4/9/18, 4/16/18Reporting Topics for WolfCon
  • we are working on enabling SIG members to join the conference by calling into sessions via ZOOM
  • gather input on reporting topics for WolfCon
DONEConfirmed for 9am on 4/9/18New Strategies for Folio Development to Support Data Lake Reporting: Discussion with Texas A&M and Cornell Developers on new FOLIO JIRA TicketsJeremy Huff, Frances WebbThis needs to be at the top of the agenda.
DONE3/26/18UXPROD-331 and UXPROD-332 JIRA Tx Review - Reporting SIG to review tickets entered in JIRA to support development of the external reporting environment (Data Lake/Store/Warehouse)AllDONE
DONE2/26/18Data Lake POC (Proof of Concept) Project UpdateAnne Highsmith, Ryan, Chris, Mark, Matt, TodDONE
DONE3/5/18BIRT Report Demo for POC ProjectChris CreswellDONE
DONE3/5/18Updates on POC Data Lake ProjectMatt, Mark, Tod, Anne, Chris, SharonDONE
DONE3/12/18Tags WorkgroupAnne-Marie BreauxDONE
DONE3/26/18Data Elements definition in Data Migration SubgroupAnne HighsmithDONE

4/2/18, 4/9/18, 4/16/18

Translating Reporting Requirements into Reporting DeliverablesSharon Beltaine
DONE4/2/18Review of Folio Feature Backlog with Updates for Data Lake SupportHarry KaplanianSee
DONEDONECall for Tags App Subgroup from PO Ann-Marie BreauxSharon, IngolfDONE - Simona Tabacuru has joined the Tags App Subgroup

  • No labels