Skip to end of banner
Go to start of banner

2019-07-08 Reporting SIG Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Date

Attendees

Present?

Name

Organization

Present?

Name

Organization

xSharon BeltaineCornell University
Sara ColglazierMount Holyoke College/Five Colleges

Elizabeth BerneyDuke University
Erin NettifeeDuke University
xJoyce ChapmanDuke University
Karen NewberyDuke University

Elizabeth EdwardsUniversity of ChicagoxTod OlsonUniversity of Chicago
xClaudius Herkt-JanuschekSUB Hamburg
Scott PerryUniversity of Chicago

x

Doreen HeroldLehigh University
Stefan StadtherrMPIL Heidelberg

Anne L. HighsmithTexas A&M
Simona TabacaruTexas A&M

Harry KaplanianEBSCOxKevin WalkerThe University of Alabama

Ingolf Kusshbz
Charlotte WhittIndex Data

Lina LakhiaSOAS

Michael Winkler

OLE

Joanne LearyCornell University
Uschi KluteGBV
xMichael PatrickThe University of AlabamaxVandana ShahCornell University

Nassib NassarIndex DataxAngela Zoss

Duke University


Veit KöppenUniversity Magdeburg
Lisa DeCarolisSmith College/Five Colleges
xLinda MillerCornell University
Elena O'Malley

Emerson


Matt HarringtonDuke University     Holly MistlebauerCornell University

Eric PenningtonTexas A&MxAndi BihlerMunich Technical University Library







Discussion Items

Item

Who

Notes

AttendanceSharon

Today's Attendance Taker: Linda Miller

Today's notetaker:  Tod Olson

Last week's notetaker: Vandana Shah

Custom FieldsAngela 

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)Joanne Leary

Updates from Various Reporting Related Groups and EffortsVarious

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
    • - missing topic
    • Naming conventions for reports and queries, how do we differentiate, name consistently.
  • LDP Report Working Group
    • Data Dictionary (Vandana)
  • LDP Data Privacy Working Group
  • LDP SysOps Working Group
  • Software development
  • Others?
Additional Topics?All 
Topics for Future MeetingsAll

Review and update Topics for Future Reporting SIG Meetings 


Action items

  • Reporting Data Privacy Group to flag reports that may have user data
  • Reporting Data Privacy to follow up with Jesse, Tod, and Cate, and Chair-Elect to determine approach to audit trails in LDP




  • No labels