| Attendance & Notes | Angela | Attendance & Notes - Today's attendance-taker: Linda Miller
- Today's note-takers: Team Leads for project updates
|
Announcements /
Reminders | Angela | Reporting SIG Holiday Schedule - Plan to cancel December 27 and January 3
- Also no meeting on December 20
Recruiting New Query Developers - The Reporting SIG is always on the look-out for new query developers. Please let us know if you are interested in doing query development or if there are others at your institution who might be a good fit.
New Opportunity for SIG volunteer - Documentation subgroup coordinates changes to the reporting documentation posted at docs.folio.org; represents the Reporting SIG at the monthly Documentation Working Group meetings
Reminder about documenting communication patterns with developers regarding data model changes - subteams/individuals, please consider documenting examples of data model changes that went well or poorly
- tentative deadline: January 10
- Angela will check in with Khalilah in January
- note: we're not really interested in UI changes, which is what the spring review focuses on. we really want to know the changes that affect the database. Those seem to show up more in GitHub PRs, not even in release notes. For example, Data Import will say, "we have better logging capability, you can click on...". That's very high level and focused on UI, not the API or the database.
|
| Intro to SQL, LDP data model | Angela | Angela will lead some introductory SQL sessions for anyone wishing to participate - Can use DBeaver and connect to folio_snapshot LDP
- If not using DBeaver:
- Use a browser-based database tool (sqliteonline)
- Download copy ("dump") of the folio_snapshot LDP (SQL file)
- Angela will walk through how to load the data into sqliteonline
- Slides from Library Carpentry SQL lessons
Basic idea behind relational databasesSelecting and sortingFiltering and limiting- Aggregating and calculating
- Ordering and commenting
- Aliases
- Joins
See also: |
| Updates and Query Demonstrations from Various Reporting Related Groups and Efforts | Community & Coordination, Reporting Subgroup Leads | Project updates Reporting development is using small subgroups to address priorities and complete work on report queries. Each week, these groups will share reports/queries with the Reporting SIG. Reporting development team leads are encouraged to enter a summary of their work group activities below. RA/UM Working Group - Meetings have become more of a lab session, working through specific problems
- Angela has been attending RA SIG meetings to open the lines of communication, now once a month
- Contact Angela if you would like to join these meetings; first Wednesdays at 10am eastern
- Context
MM Working Group - MM SIG has a new Release Highlights that try to focus on changes for releases.
- The zoom link for the meeting is https://umass-amherst.zoom.us/j/99254861410. Usual FOLIO password. Our lab sessions are open to everyone. Please bring your questions, examples, and comments about reporting and metadata.
- Meetings are 1st Tuesday of the month 12-1pm ET
ERM Working Group - First prototype created for documentation. A wider discussion is needed as to whether this approach is sufficient or whether it needs improvement. Preferably in one of the meetings on Monday. Link to prototype
- On going work on ERM data with LDlite.
- Need discussion about the workflow from FY rollover later to better understand some attributes. https://folio-org.atlassian.net/wiki/display/DD/Fiscal+year+rollover
- New additional derived tables are planned for orders and invoices. In view of the technical background of some reporting software, we need additional tables to make some reports realizable.
- Issue: "ERM - Create report of agreements by cancellation dates" #506 was therefore paused.
- Waiting for relational data in the MetaDB in orders and invoices
- ERM Prototype and Query Development Status
- Bi-weekly schedule (next meeting 11th Jan 9:00 AM ET)
- Zoomlink (password is the common zoom password in the FOLIO community)
RM Working Group - working on LDP to Metadb table mapping spreadsheet to prepare for transition to Metadb
- subscription costs and subscription counts queries PR posted to folio-analytics
- casting numbers: need to cast numbers related to finances as decimals, not money; money rounds up, which may throw totals off
- looking at using https://mermaid-js.github.io/mermaid/#/ to document data models in finance areas of FOLIO
- exploring ways to make it easier to find options for reporting parameters in your LDP (e.g., a list of locations, item statuses, etc.)
- several queries for RM completed, but still need documentation, testing, and review
- for latest updates, see RM Prototype and Query Development Status
- weekly meetings on Thursdays at 9am ET on zoom – contact Sharon Beltaine for zoom link and invitation
Reporting SIG Documentation Subgroup - Honeysuckle documentation is live on https://docs.folio.org/docs/
- Iris documentation is in progress, due December 15
- Additional Context
- The Reporting SIG has representation on the Documentation Working Group, which is building end-user documentation for https://docs.folio.org/docs/ (mostly linking to existing documentation over on GitHub)
External Statistics Working Group - no updates currently
- new organizational/tracking scheme for JIRA, with pointers to queries in folio-analytics repository
- New organizational structure for External Statistics reports
- external statistics reports (e.g., ACRL) typically require running queries from different functional reporting areas
- these reports will be captured in JIRA under one UXPROD-XXXX report cluster issue, then the descriptions will point to each of the queries required to run them on the folio-analytics repository
- institutions will need to rank each of these 8 new UXPROD-XXXX report cluster issues
- each reporting development team will take responsibility for the queries in their area for the external statistics clusters
Product Council
For all recent work on FOLIO Reporting SQL development:
|
| Topics for Future Meetings | All | - Follow-up on MARC status, Quickmarc/Data Import conflicts
- How to strengthen connections to SIGs and their developers to be kept in the loop about changes to the data model
- Show and tell
- how are institutions using the LDP
- examples of using the local schema
- Cornell's report ticketing system
- Rollout plans from institutions
- Ask someone on the sysadmin side to talk about LDP administration (Jason Root?)
- What is done in JIRA? (JIRA clean up)
- Training topics
- adding test data in FOLIO snapshot
- How to do ad hoc querying with the derived tables
- How to use the LDP app
- using KNIME to build reports (LDP edition)
- use of local schema for custom tables
- more on MARC (ask Jennifer)
- using different applications (other than DBeaver)
- Insomnia for API queries?
- SQL
- LDP to metadb
- Metadb implications
- if schema changes, will that be relatively seamless? old fields still in history, but new fields in current?
- if fields are deprecated and removed, what happens if they come back again?
- how will deleted records show up?
- GitHub
- Panorama
- LDLite (again?)
- Discussion:
- how to rank clusters with institutional rankings going away?
- consortia SIG is talking about a central office app of some kind; that app might need to deal with consortia-wide reporting
- how to train:
- wiki pages with examples? form a small project team? (e.g., how to pull from marc, how to use local schema)
- each dev team create training about the data structures in that area?
- Query style (ask Nassib)
- Gathering institutional query repositories; someone can propose a new page or a new addition to an existing page on FOLIO Analytics?
- Follow up on how devs can work with SMEs better to decide on and advertise data model changes
- Upcoming:
- SQL advice/query optimization (Axel)
- query demo - MARC (Tod)
- Intro to SQL training (December 6 and 13 at least)
- revisit discussion on openness/transparency in communication and open source software; decide as a group what we would like to advocate for
- ERM prototype for derived table documentation (January 10)
Review and update Topics for Future Reporting SIG Meetings
|
|
|
|