Versions Compared

Old Version 2

changes.mady.by.user Sharon Markus

Saved on

compared with

New Version 3

changes.mady.by.user Sharon Markus

Saved on

Key

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

Date

...

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.

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

LDP Table ReviewAngela

Angela will 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").


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 


...