2019-12-09 Reporting SIG Meeting notes

Today's Attendance Taker: Linda Miller

Today's notetaker:  Vandana Shah

Last week's notetaker: Sharon Beltaine

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.