| Attendance | Sharon | Today's Attendance Taker: Linda Miller Today's notetaker: Last week's notetaker: Vandana ShahSharon Beltaine |
| Reporting SIG Meetings around Winter Break | Sharon | 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 Efforts | Various | 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 coordinationwe are preparing a presentation
- LDP Data Privacy Working Group
- LDP SysOps Working Group
- Software developmentissue 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 Names | Angela | 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 consistentlywhy 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 meetingrename instance type tables to UI resource typesPrioritizing Reporting Clusters for the MVP | Angela | Several new reporting clusters have been created recently in JIRA as UXPROD issues. Each reporting cluster captures one or more reports with related data elements. We will review and prioritize these new issues for the MVP.
|
| New LDP Channels on Slack | Sharon | 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 LDP
#ldp-sysadmin - System administration of the LDP |
2019 Goal Review and 2020 Goal Planning
|
| We will review the Reporting SIG's list of Goals for 2019 and start working on our Goals for 2020. See Goals for 2019 |
| 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 2019 | All | 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 Meetings | All | Review and update Topics for Future Reporting SIG Meetings
|