Versions Compared

Old Version 1

changes.mady.by.user Sharon Markus

Saved on

compared with

New Version 2

changes.mady.by.user Sharon Markus

Saved on

Key

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

Date

Attendees


Present?

Name

Organization

Present?

Name

Organization


Sharon BeltaineCornell University
Sara ColglazierMount Holyoke College/Five Colleges

Elizabeth BerneyDuke University
Erin NettifeeDuke University

Joyce ChapmanDuke University
Karen NewberyDuke University

Jean PajerekCornell University
Tod OlsonUniversity of Chicago

Claudius Herkt-JanuschekSUB Hamburg
Scott PerryUniversity of Chicago


Doreen HeroldLehigh University
Stefan StadtherrMPIL Heidelberg

Anne L. HighsmithTexas A&M
Simona TabacaruTexas A&M

Harry KaplanianEBSCO
Kevin WalkerThe University of Alabama

Ingolf Kusshbz
Charlotte WhittIndex Data

Lina LakhiaSOAS

Andi Bihler

Munich Technical University Library

Joanne LearyCornell University
Uschi KluteGBV

Michael PatrickThe University of Alabama
Vandana ShahCornell University

Nassib NassarIndex Data
Angela Zoss

Duke University


Veit KöppenUniversity Magdeburg
Lisa DeCarolisSmith College/Five Colleges

Linda MillerCornell University
Elena O'Malley

Emerson


Matt HarringtonDuke University     Holly MistlebauerCornell University

Jean PajerekCornell University
Nancy BolducCornell University

Margaret Briand WolfeBoston College
Eric PenningtonTexas A&M

Sarah ParkDuke University
Christie ThomasUniversity of Chicago

...

Item

Who

Notes

AttendanceSharon

Today's Attendance Taker: 

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

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
  • 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

If you haven't yet, please join the 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 LDPLDP Table ReviewAngela

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.review the names of the tables in the LDP to see if there are any issues before continuing any further with development.

Related notes from Nassib:

See the source code file at:
https://github.com/folio-org/ldp/blob/master/src/schema.cpp

The schema mappings are currently defined by the function, Schema::MakeDefaultSchema(Schema*).

When you see this:

    table.sourcePath = "/cancellation-reason-storage/cancellation-reasons";
--> deriveTableName(table.sourcePath, &(table.tableName));
    schema->tables.push_back(table);

That deriveTableName() function is deriving the table name from the last element of the source path; in this case, it becomes cancellation_reasons.

If you see this:

    table.sourcePath = "/finance-storage/group-budgets";
--> table.tableName = "finance_group_budgets";
    schema->tables.push_back(table);

The table name is being set explicitly. I think we need to do more of that to plan for future growth in the namespace.If you see this:

    table.sourcePath = "/invoice-storage/invoice-line-number";
    deriveTableName(table.sourcePath, &(table.tableName));
--> //schema->tables.push_back(table);

The schema->tables.push_back() call is commented out, which means the table is currently being skipped (i.e. not being added). 


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 


...