2018-10-29 Reporting SIG notes

Sharon Beltaine

Cornell University

Peter Murray

Index Data

Elizabeth Berney

Duke University

Erin Nettifee

Duke University

Joyce Chapman

Duke University

Karen Newbery

Duke University

Elizabeth Edwards

University of Chicago

Tod Olson

University of Chicago

Claudius Herkt-Januschek

SUB Hamburg

Scott Perry

University of Chicago

Doreen Herold

Lehigh University

Robert Sass

Qulto

Anne L. Highsmith

Texas A&M

Simona Tabacaru

Texas A&M

Vince Bareau

EBSCO

Mark Veksler

EBSCO

Harry Kaplanian

EBSCO

Kevin Walker

The University of Alabama

Ingolf Kuss

hbz

Charlotte Whitt

Index Data

Lina Lakhia

SOAS

Michael Winkler

OLE

Joanne Leary

Cornell University

Uschi Klute

GBV

Michael Patrick

The University of Alabama

Holly Mistlebauer

Cornell University

Nassib Nassar

Index Data

Angela Zoss

Duke University

Veit Köppen

University Magdeburg

Assign Notetaker, Take Attendance, Review agenda

Sharon

Today's notetaker: Tod Olson

Last week's notetaker: Ingolf Kuss

Special Note Daylight Savings Time impacts on Meeting Times

Ingolf

We will meet on Oct 29, as usual at 9 AM Eastern U.S. time. This will be 2 PM in central Europe (most European countries turn back the clock on Oct 28).

We will meet on Nov 5 as usual at 9 AM Eastern U.S. time (this will then be EST, not daylight saving time EDT, anymore). This will be 3 PM in central Europe (as usual).

Report Prototype Subgroup

subgroup

need to find the best time to meet this week to look at building circ report

Postponed - will schedule time for subgroup to meet this week and take a first pass.

Prioritizing Your Institution's Reports

Sharon Beltaine

In order to determine the order in which we will prototype our reports for the development of data models for the data warehouse, we need to prioritize them within each functional area (e.g., RM, RA, etc.). Please see the Prioritizing Reports page in the wiki for detailed instructions.

-This week, we will review our group's progress on prioritizing reports in the "import and export," "external statistics," and "resource mgmt" worksheets in the Reporting SIG Master Spreadsheet

-Monday November 12, 2018 is our target completion date

Sharon will reach out to the Batch Loading group on whether they are already taking care of the import-export portion.

Questions from Duke via @Angela Zoss (Old):

• If workflow engine is not available in time for batch, will reports have to fill in for some of that functionality to trigger human workflows?

• Given that schemas are changing, should we write reports according to the schema as the data exists now or as it will exist or if the need may no longer exists?

• How to think about reports that will be based on real-time data across different data domains? Will they be in cross-apps, or in the data warehouse. (Good segue to Nassib's topic.)

• Will data warehouse reports be able to be triggered by schedule or by logic?

  • Workflow engine would make it technically possible to construct something that happens by trigger, there is not currently a FOLIO API on the data warehouse, there would need to be something for the workflow to connect to. Could be implemented, question of relative prioritizations.

  • Should probably start collecting requirements that would place these sorts of demands on the system.

  • Actions: @Angela Zoss (Old) will create a page of reporting needs that affect the platform, we can then review and decide which become JIRA tickets.

• Any time a call number is in a report we would want to have a sortable call number?

  • Best to define that in each report.

Practical responses:

For next week: focus on metadata management, resource access, and user management. Also focus on identifying reports that require real-time data which have not been identified as in-app, and bring those forward.

"Real-Time" Reporting Changes

Nassib, Sharon

We will revisit the subject of "real-time" reporting in light of FOLIO technical infrastructure to support a reporting data warehouse environment. It is important to understand the difference between data coming from the AES (Asynchronous Event Service) as logs of transactions and "data at rest." This may require a "reset" of our expectations for "close to real-time" data for our reports.

Have been discussions before Nassib came in about in-app reports, and more recent about how to flow data into. Streaming updates will require platform support, and this will

Would like to reorganize this to focus on things we need to support requirements of this group. These reqs are focused around creating large variety of reports. Friday, completed first end-to-end prototype of an initial report.

Thinking about when and whether to implement streaming update. Foresee that the biggest technical challenge will be to handle updates from distributed microservices arrive out of order. Question for this group: how to think about prioritizing this?

A: Close to real-time reports will be hard to implement. This requires to look at the priorities of the reports. We need to review the reports, which ones require real-time data. Can they be turned into an in-app report ? Have been implementing the daily-refresh first.

NB: not all in-app reports are confined to a single data domain, some are being developed that have dependencies on other apps. Looking at these on case-by-case basis. Critical to work with POs on this.

One critical distinction: unlike data warehouse reports, the in-app reports will be coded into the apps after being defined by the SIGs and not be customizable (with some exceptions in aquisitions). In practice this is working well, take the case of fees/fines, where the SIGs are having an easy time agreeing on what data are in the report, the data will be downloadable as a spreadsheet and manipulable.

In the case of in-app reports that may be delated, Important that we know from the functional groups if some of those will be shifted to the data warehouse.

Assigning Yourself to JIRA Reports

Holly Mistlebauer

Holly walked us through the process of assigning ourselves to our reports in the FOLIO JIRA System. Instructions are provided on this wiki page, which will also contain other JIRA info:  Working on a JIRA Issue

-review of JIRA report assignments

-Monday November 12, 2018 is our target completion date

Topics for Future Meetings

All

Review and update Topics for Future Reporting SIG Meetings

Other Topics?

All

Any other topics to discuss today?