Versions Compared

Old Version 1

changes.mady.by.user Sharon Markus

Saved on

compared with

New Version Current

changes.mady.by.user Angela Zoss (Old)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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
xClaudius Herkt-JanuschekSUB HamburgxScott PerryUniversity of Chicago

x

Doreen HeroldLehigh University
Stefan StadtherrMPIL Heidelberg

Anne L. HighsmithTexas A&MxSimona TabacaruTexas A&M

Harry KaplanianEBSCO
Kevin 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 Alabama
Vandana 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

Jean PajerekCornell UniversityxNancy BolducCornell University
xMargaret Briand WolfeBoston College
Eric PenningtonTexas A&M
xSarah ParkDuke UniversityxChristie ThomasUniversity of Chicago
xClint Bellanger




Discussion Items


Item

Who

Notes

AttendanceSharon

Today's Attendance Taker:  Linda Miller

Today's notetaker:  

Last week's notetaker: Vandana Shah

Reporting SIG Meetings around Winter BreakSharon

Our meeting today, Monday, December 16, will be Reporting SIG's last meeting of 2019.

The Reporting SIG meetings for 2020 will start back up again on Monday, January 6, still at 9am ET.

Have a nice Enjoy your winter break! 

Updates from Various Reporting Related Groups and EffortsVarious

New Reporting Slack Channels:

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

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
    • we are preparing a presentation 
  • LDP Data Privacy Working Group
  • LDP SysOps Working Group
  • Software developmentHere 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
    • issue with DBeaver and timezones; we'll send updates soon
  • Report Prototypes
    • a small group will discuss ERM reports during the Report Prototype "Open" time at 10am ET today
Review of LDP Table NamesAngela

Nassib has requested community feedback on the naming of tables in the LDP database:

At present, some table names use prefixes to remove ambiguity, e.g. /finance-storage/groups is mapped to finance_groups, while others do not use a prefix, e.g. loans, users, and groups, as they are considered to have a more general application.  In other cases, it may not be obvious whether a prefix should be used, e.g. requests.

The advantages of using a prefix are clarity and leaving "room" in the namespace for more similarly named concepts in the future to co-exist with the current tables.  The disadvantage is longer and more complex table names.

Now that queries are being developed, there will be an increasing number of dependencies on table names, and it is a good time to pause and give some thought to whether some of them should be changed, because it will be increasingly difficult to change them later without having to modify existing queries.

A spreadsheet with the table mappings and naming is linked here, and I would appreciate input from the Reporting SIG:

https://docs.google.com/spreadsheets/d/19iP5hnUHqCuGMM5OQKdUWMNCT75ZK3EDa0Vx8LgUZ24/edit?usp=sharing

Notes:

  • questions about plurals in table names, which are not used consistently
  • why are some finance table names preceded by finance, and others not?
  • repeatable fields will be served to the LDP as arrays in the data column that preserves the original Javascript object in FOLIO; a JSON extract path is used to extract this data; we will review this to discuss possible alternate ways to show this information in the LDP in a future Reporting SIG meeting
  • rename instance type tables to UI resource types
New LDP Channels on SlackSharon

Three new Slack channels are now available on the Library Data Platform:

#ldp-announce - Announcements for the LDP software (low volume of posts)
#ldp-users - Querying and general usage of the Library Data PlatformLDP
#ldp-sysadmin - System administration of the Library Data Platform

Connecting to and Testing Queries with the New Public

LDP

Angela

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?AllWe'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 Queries		All

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

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


Thanks and Kudos for 2019All

It is our tradition to end the year with a round of thanks and kudos for everyone's participation in reporting efforts this past year.

Good job, everyone!

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
  •  Angela Zoss (Old) work with Nassib Nassar to go over names list, create final proposal
  •  Angela Zoss (Old)  (?) to share proposed list with POs of SIGs to make sure changed names still make sense
  •  Angela Zoss (Old) to follow up on concerns from Christie Thomas about developing queries using json_extract_path_text; does allow for joins on individual elements in an array, doesn't work on all reporting systems