2019-07-08 Reporting SIG Meeting notes

Sharon Beltaine

Cornell University

Sara Colglazier

Mount Holyoke College/Five Colleges

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

Stefan Stadtherr

MPIL Heidelberg

Anne L. Highsmith

Texas A&M

Simona Tabacaru

Texas A&M

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

Vandana Shah

Cornell University

Nassib Nassar

Index Data

Angela Zoss

Duke University

Veit Köppen

University Magdeburg

Lisa DeCarolis

Smith College/Five Colleges

Linda Miller

Cornell University

Elena O'Malley

Emerson

Matt Harrington

Duke University

Holly Mistlebauer

Cornell University

Eric Pennington

Texas A&M

Andi Bihler

Munich Technical University Library

Attendance

Sharon

Today's Attendance Taker: Linda Miller

Today's notetaker:  Tod Olson

Last week's notetaker: Vandana Shah

Custom Fields

Angela 

A small workgroup is needed to refine the requirements for the Custom Fields reporting feature, Store custom fields from apps in LDP (LDP-55). Here is the description from JIRA:

FOLIO apps are being designed with custom fields, in part to allow institutions to tailor their experience, but also potentially to correct problems arising from certain features not being available for go-live. At Duke, for example, I believe we will be using custom fields to track additional patron identifiers past the maximum set by the UM app.

These custom fields may well include fields that will be important for the reporting needs of institutions. I have had a request that the LDP be set up to be responsive to custom fields in the various apps. It was suggested that this might logically connect to thinking about how to have the LDP accommodate new apps developed in the future.

Notes:

Need some specific user stories to generate specific, real-world examples. Do not currently know how each module will implement custom fields. @Angela Zoss (Old) has mainly heard this through Resource Access SIG. Looking for people to join small working group to develop use cases for LDP.

Small group: @Angela Zoss (Old),  Sharon to ask @Joanne Leary if she can join this group

Updates from Various Reporting Related Groups and Efforts

Various

The Reporting SIG is using small work groups to address priorities and complete our work. Each week, we will provide updates to the Reporting SIG from these various reporting-related groups and efforts:

• Community and coordination

  • spoke about data dictionary and glossary idea, still clarifying direction

  • plan to start with prototype, get feedback, move from there

  • generating test data dynamically is taking too long, considering static test data set

  • Naming conventions for reports and queries, how do we differentiate, name consistently.

    • Report names will be based on data

    • Query names will be based on how query is made

    • See notes in FOLIO Face-to-Face DC Conference Reporting Session Notes

• LDP Report Working Group

  • Data Dictionary (@Vandana Shah)

  • Right now not taking everything from the APIs, but from the LDP schemas

  • Four categories: users, items, ...

  • Have initial Google doc, will share

  • Please see notes at Library Data Documentation and Google doc at https://drive.google.com/drive/folders/1EFTaxyaTnBVHm0S8QWJtDMJ4pp3b70P_

• LDP Data Privacy Working Group

  • Results of initial review of LDP reports for privacy: Flagged FOLIO reports - privacy (@Joyce Chapman )

    • First pass on all LDP reports that seem to include personal data

    • Will send to Reporting SIG and solicit clarification on each questioned report and record in JIRA with a label

    • Question of privacy of staff information, what set of staff actions are protected by GDPR? Would prefer not to bring those into LDP.

      • Are there use cases other than audit trails?

• LDP SysOps Working Group

  • Currently consists of @Kevin Walkerand @Sharon Markus, would others like to join?

  • Cornell has basic setup, planning to open to local users this week

• Software development

• Others?

• Report clustering: Need someone to look at Metadata Management reports 

Additional Topics?

All 

Topics for Future Meetings

All

Review and update Topics for Future Reporting SIG Meetings