Versions Compared

Old Version 4

changes.mady.by.user Nassib Nassar

Saved on

compared with

New Version 5

changes.mady.by.user Nassib Nassar

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

Review of LDP Table Reviewtable namingAngela

Angela will review the names of the Nassib has requested community feedback on the naming of tables in the LDP to see if there are any issues before continuing any further with development.(Detailed notes will be added here)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-exists 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 current table names, and it is probably a good time to consider 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 of the table mappings and naming is provided here, and I would appreciate any input from the Reporting SIG:

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

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 


...