2020-05-04 Reporting SIG Meeting notes

Date

Attendees

Present?

Name

Organization

Present?

Name

Organization

xSharon BeltaineCornell University
Sara ColglazierMount Holyoke College/Five Colleges

Elizabeth BerneyDuke University
Erin NettifeeDuke University

Joyce ChapmanDuke University
Karen NewberyDuke University
xJean PajerekCornell UniversityxTod OlsonUniversity of Chicago

Claudius Herkt-JanuschekSUB HamburgxScott PerryUniversity of Chicago


Doreen HeroldLehigh University
Stefan StadtherrMPIL Heidelberg

Sarah ParkDuke UniversityXSimona TabacaruTexas A&M
xClint BellangerAuburn UniversityxKevin WalkerThe University of Alabama
xIngolf Kusshbz
Christie ThomasUniversity of Chicago
xJoshua LambertMissouri State

Andi Bihler

Munich Technical University Library

Joanne LearyCornell University
Cheryl MalmborgUniversity of Chicago
xMichael PatrickThe University of AlabamaxVandana ShahCornell University
xNassib NassarIndex DataxAngela Zoss

Duke University


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

Emerson

xMatt HarringtonDuke University     Holly MistlebauerCornell University

Cathy TuohyEmmanuel College (FLO)xNancy BolducCornell University

Shirley MoentnishMissouri StatexEric PenningtonTexas A&M

Stefan DombekLeipzig UniversityxAxel DoerrerUniversity Mainz
xNatalya PikulikCornell University
Owen StephensK-Int
xEliana LimaFenway Library Organization



Discussion Items

Item

Who

Notes

Attendance & NotesSharon

Attendance & Notes

  • Today's attendance-taker: Sharon Beltaine
  • Today's note-takers:  Team Leads for project updates
Updates from Various Reporting Related Groups and EffortsCommunity & Coordination, Reporting Subgroup Leads

Project updates

The Reporting SIG is using small working 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. Please include updates on specific JIRA issues for prototype or query development workflow. Do we need to create any additional JIRA tickets?

  • Community & Coordination: 
    • planning for June FOLIO forum
    • circling back to REP issues that have not yet been clustered - will be reviewing those in Reporting SIG as time allows
    • need to revisit fix versions for clusters - current clusters assigned to Q2 2020 are not realistic, so we'll be re-evaluating those
    • C&C team will be meeting with functional area team leads to check on status and move development along
  • Development:
    • data documentation for ERM now included in FOLIO Schema Parser (thanks, Owen!) 
    • tables added for Fees and Fines
    • Microsoft Access working with Postgres LDP instances; Microsoft Access is version-specific (i.e., 2016 may be different from 2019)

RA/UM Working Group: 

  • No update for this week.


MM Working Group:

  • working on External Holdings reports cluster


RM Working Group: 

ERM Working Group:



Quick Review of RM Title, Item, and Subscription Count Cluster PrototypesNancy, Axel, Linda

The RM reports team would like feedback from members of the Reporting SIG on the following RM cluster prototypes:

Notes

  • should permanent location for holdings; do we also need temporary location, other locations, etc. (ask RM SIG) 
  • what is the best way to get subscription counts?
  • would it help to agree on a model library when writing the query?
  • when creating the best model for a cluster, think about the state of the data in the records in that area
  • there is a value in keeping a query simple enough that a person can modify it easily


Identifying LDP Tables for GDPR Compliance Nassib, Ingolf, Vandana, Joyce

Toward GDPR compliance in the LDP...

  • the LDP Data Privacy group will be identifying and documenting which tables have foreign keys that reference tables containing personal data 
  • personal data located in just a few tables in the LDP
  • does the group need assistance from other Reporting SIG members?
  • this process will help with the process of making the LDP GDPR-compliant by not storing any personal data
  • FOLIO Schema Parser can help, go into Data Element and Filter to ID to get the primary key of every table


Additional Topics?All 
Topics for Future MeetingsAll

Review and update Topics for Future Reporting SIG Meetings 


Action items