2018-06-11 Reporting SIG notes

Today's notetaker: Sharon Beltaine

Last week's notetaker: Ingolf Kuss

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. http://www.triangle-solutions.de/ . 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.

-BibControl has these desirable features for data analysts:

• import data from many different systems,
• automatic distribution of reports,
• reports for different target groups,
• flexibility to add or change existing reports

-BibControl integrates, converts, filters, and standardizes data transferred into data warehouse

-OLAP Online Analytical Processing allows you fast report creation

-Application Builder, data mining functional

-distribution of reports is done through a web portal, can use Online Cockpit and Report Viewer

-based on Progress database format

-can read JSON data and is stored as a relational database, can then be queried in SQL

-offers hosted solutions with partners, has not set up on Amazon Web Services yet

-OLAP tool features drag and drop fields to create your report, specify various output types

-Online Cockpit shows report which can added to interact to be run at any time

-Report Viewer allows interactive manipulation of fields in your report, similar to Pivot Table functionality in Excel

-Data Mining feature allows you to summarize data, then show patterns in the data visually

Holly 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.

-all Product Owners are trying to get in app reports identified for upcoming gap analysis

-Holly added a new "in app report" worksheet to Reporting SIG Master Spreadsheet, which lists each in app report with its associated JIRA ticket and gets crossreferenced with the original report listed in the rest of the spreadsheet

-Holly is working with the rest of the Product Owners to turn our in app report candidates into JIRA tickets for developers to build within the appropriate microservice; the Product Owners are reviewing the Reporting SIG Master Spreadsheet to identify in app reports and document them in JIRA tickets for development

-We will continue to discuss In App reports in our upcoming Reporting SIG meetings so Holly can bring questions Product Owners may have as they work through our list of reports

-It is important that in app reports are identified and documented for the FOLIO project gap analysis that is underway; we need to understand how much work needs to be done to build the FOLIO release

-Holly will gray out any items that are not candidates for in app reports

Important Note to Reporting SIG members:

Please drop copies of any remaining reports you have identified in the spreadsheet in the appropriate functional area folder in the Library Stats folder in the Reporting SIG Google Drive folder and link them to the "Link to Sample" column in the Reporting SIG Master Spreadsheet. It really helps Product Owners to have a report to view to understand what is needed for a given in app report.

Please note that 3 new FOLIO JIRA tickets have been added to describe tasks for the Reporting SIG:

UXPROD-862 Create a Reporting Dashboard

UXPROD-863 Identify Data Elements Needed for Reporting

UXPROD-865 Build a Data Dictionary for Reporting

Laura Wright from the MM SIG has requested feedback from the rest of the SIGs on this working definition of Inventory:

https://discuss.folio.org/t/folio-inventory-a-working-definition/1861

Sharon presented the Reporting SIG's Reference Data Warehouse Environment Proposal to Product Council on 6/7/18:

See the full written proposal: Reporting SIG Proposal to FOLIO Product Council for a Reference Data Warehouse

See the presentation slides: Data Ware House Proposal Presentation

-presentation was well received and generated some additional questions

-the data warehouse will need developer and other resources so Product Council decided that this will be prioritized in the Epic process and resources will be assigned according to priorities and the Technical Council should review the Reporting SIG’s proposal

-New JIRA ticket created for Data Warehouse development: see UXPROD-864

-Cate Boerema suggested a development team be assembled right away; Sharon to follow up with Mike Winkler

-questions on distinction between data lake vs data warehouse, proof of concept vs "reference" environment

-questions about the source of the data for the data warehouse

-Christopher Spaulding suggested bringing the technical design to the new Technical Council

-reps from participating institutions in support of data warehouse development

-more discussion on next steps during next Reporting SIG meeting

Next week's meeting focus: More about In App Reports and Continued Discussion on the Data Warehouse

Review and update Topics for Future Reporting SIG Meetings