Versions Compared

Version Old Version 1 New Version Current
Changes made by

Sharon Markus

Herkt-Januschek, Claudius

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added link

Date

Attendees

...

Present?

Name

Organization

Present?

Name

Organization

xSharon BeltaineCornell UniversityxSara ColglazierMount Holyoke College/Five Colleges

Elizabeth BerneyDuke University
Erin NettifeeDuke University

Joyce ChapmanDuke University
Karen NewberyDuke University

Elizabeth EdwardsUniversity of Chicago
Tod OlsonUniversity of Chicago

Claudius Herkt-JanuschekSUB HamburgxScott 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

Andi Bihler

Munich Technical University Library

Joanne LearyCornell University
Uschi KluteGBV
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







Discussion Items


Item

Who

Notes

AttendanceSharon

Today's Attendance Taker:

 

Elena O'Malley

Today's notetaker:

 

Vandana Shah

Last week's notetaker: Kevin Walker

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: The group is reviewing how to respond to all the blockers impeding the LDP, and exploring backup plans.
  • LDP Report Working Group
Received feedback from SIG members. Will continue to work on finalizing definitions for elements currently in the LDPTake a look at reports next week that will be affected by GDPR compliance.
  • : Will meet later today, and will also look at blockers impeding the LDP,  and backup plans.
  • LDP Data Privacy Working Group
  • Plans: All data that enters the LDP should be anonymized. Personal data that is stored in-app could be used for audit functionality. Personal data that is stored in-app must allow for deleting upon request (right to delete exists only for GDPR compliant institutions).
      • See next agenda topic "Reports with Personal Data"
    • LDP SysOps Working Group
    Anne
    • :
    Speaking to Jason Root at TAMU regarding the injection of test data into LDP
    • TAMU has joined.
    • Software development
      • Another new reporting developer! From UChicago, who will most likely be half-time.
    ...

    (2) Reporting Blockers - labels complete, all issues are mandatory so no ranking required

    • UXPROD-1414 - Complete the documentation of data attributes in module APIs
    • FOLIO-1839 (will become a UXPROD issue) - Enable incremental requests for all records since last request
    • UXPROD-1438 - Implement a process for tracking data-related API schema changes
    • UXPROD-1432 - Add new effective location attribute calculated at the time of check-out

    (3) UXPROD Reporting Clusters (umbrella issues for Reports) - IN PROGRESS, institutions will need to rank clusters

    Notes:

    MM not planning to develop any in-app reports - will leave metadata reporting to the LDP (this issue is still developing)
      • Also, we will be losing a full-time developer in a month or two, so it's a good thing that Chicago, Duke, and Cornell have contributed developers.
      • Call for additional developers
    • Others?


    Reports with Personal DataReporting Data Privacy Workgroup

    On Monday, we plan to review all reports containing personal data. It would be great if you could look through the list created by Joyce (link below) before the meeting, so that we can zip through them. The ones highlighted in RED contain personal data.

     

    https://docs.google.com/spreadsheets/d/1nR9frGMUgWq6TNKJFhY84FJx2Cwnlndnd2iq6p0wDx4/edit#gid=0

     

    Capacity Planning Update for Reporting

    Nassib, Holly, Angela, and Sharon have been preparing reporting JIRA issues for FOLIO Capacity Planning. Here is where we stand today.

    (1) Reporting Functionality Features ("ldp-platform" label) - labels complete, some ranking left for institutions, no need to rank issues with "mandatory" or "NFR" label

    The Reporting Data Privacy Group has identified reports that contain personal data.  These are highlighted in RED in the spreadsheet linked below.  

    Flagged FOLIO Reports - Personal Info

     - See Jira notes for each report; most of the reports we looked at today may be suitable for in-app reporting. We will need to continue next week to get through the rest of the reports.

    RE: Ad-hoc reports: we should keep in mind that for US universities, anonymizing personal data in the LDP will be an option (a switch that can be turned on or off), but the European universities will not have this option. So we shouldn't be developing reports that the European universities can't use, but instead these can be run as ad-hoc reports for US universities. See UXPROD-1873 for more details/constraints on ad-hoc reporting.

    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
    •  Reporting Data Privacy to email the Reporting SIG to ask for feedback on which reports contain personal info Joyce Chapman

    ...