Page tree
Skip to end of metadata
Go to start of metadata

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

Jean PajerekCornell UniversityxTod OlsonUniversity of Chicago

Claudius Herkt-JanuschekSUB Hamburg
Scott PerryUniversity of Chicago


Doreen HeroldLehigh University
Stefan StadtherrMPIL Heidelberg

Anne L. HighsmithTexas A&MxSimona TabacaruTexas A&M

Harry KaplanianEBSCOxKevin WalkerThe University of Alabama
xIngolf Kusshbz
Charlotte WhittIndex Data

Lina LakhiaSOAS

Andi Bihler

Munich Technical University Library

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

Nassib NassarIndex DataxAngela Zoss

Duke University

xVeit KöppenUniversity Magdeburg
Lisa DeCarolisSmith College/Five Colleges
xLinda MillerCornell UniversityxElena O'Malley

Emerson

xMatt HarringtonDuke University     Holly MistlebauerCornell University
xJean PajerekCornell UniversityxNancy BolducCornell University
xMargaret Briand WolfeBoston CollegexEric PenningtonTexas A&M
xSarah ParkDuke UniversityxChristie ThomasUniversity of Chicago


Discussion Items

Item

Who

Notes

AttendanceSharon

Today's Attendance Taker: Linda Miller

Today's notetaker:  Vandana Shah

Last week's notetaker: Sharon Beltaine

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: opening up a public instance of the LDP, and queries can be tested on it. There are still a few issues under discussion. Angela hopes to have an update soon.
  • LDP Data Privacy Working Group: Ingolf flagged personal data from mod-organization-storage, so that Nassib can anonymize those fields. Also, personal data fields in ERM reports were identified. Only one report (REP-158) may contain personal data, but this is currently needed only by Cornell in 2021, so it is not an immediate concern.
  • LDP SysOps Working Group
  • Software development
    • Here is a summary of changes in the past week:

      * Support for historical data has been added.  (It was previously
      disabled in the 0.3 release.)  See Section 6 of the LDP User Guide for
      details.

      * A bug has been fixed that caused tables not to be updated when an
      extraction succeeded with zero records.

      * Improved handling of cases where data record sizes exceed Redshift
      data type limits.

      * The date and approximate time when each table was last updated can now
      be viewed with:

           SELECT * FROM sys.loading;

      * The databaseUser configuration parameter has been renamed to ldpAdmin,
      and databasePassword has been renamed to ldpAdminPassword.

      * The LDP database user can now be specified via a configuration
      parameter, ldpUser.  The default value is ldp.

      * A few preliminary notes on Redshift database configuration have been
      added to the LDP Admin Guide.

      * A few notes have been added to the LDP Admin Guide on running the data
      loader in production.


New Reporting Slack ChannelsNassib

New Reporting Slack Channels:

#ldp-announce - Announcements of the Library Data Platform project

#ldp-users - Querying and general usage of the Library Data Platform

#ldp-sysadmin - System administration of the Library Data Platform

Connecting to and Testing Queries with the New Public LDPAngela

Angela will walk us through connecting to and testing our queries with the new Public LDP environment. See the LDP Reference Environment page for more information.

Instructions on connecting are here: LDP Reference Environment


Who is going to WolfCon in January 2020?All

We'd like to get a sense of how many Reporting SIG members plan to attend our upcoming conference. Please add your name to the second worksheet labeled "Attendees" if you plan to attend the WolfCon January 2020 conference.

So far, 4 members plan to attend. Chicago (and others) are still in the process of deciding who will go. It will depend on the draft agenda.


Reporting Prototypes and QueriesAll

Let's review our Report Prototype and Query Development Project List

Meeting Notes: See notes in the list (column "status").


Additional Topics?All 
Topics for Future MeetingsAll

Review and update Topics for Future Reporting SIG Meetings 


Action items

  •  Community and Coordination group to discuss how to maintain GDPR compliance for REP 147 and REP 148
  •  Vandana Shahto follow up on notes for changes to JIRA tickets for MM Reports and Report Clusters