2019-12-16 Reporting SIG Meeting notes

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! 

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

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). 

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

• Report Prototype and Query Development Project List

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

Review and update Topics for Future Reporting SIG Meetings