| 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
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
|
| Gathering examples of communication breakdowns | All | Follow up on 11/29 discussion about lack of communication between developers and SMEs, lack of transparency in other areas of FOLIO - Had a good discussion in MM about documentation, change control; the most outspoken group is Data Export(?) group. It's complex; the changes show up in code commits. Recent change to SRS comes because SRS can have bib, holding, or item, so can't just label it all instance. Might have some implications, though, so have some questions that are going back to developers. Have a plan to bring this up with technical council. Maybe this should be a TC discussion at WOLFcon - how to track changes, how to write release notes. Ann Marie made a high level view of Data Import, but maybe not specific enough. Don't want to just know about changes, but how changes affect what we're doing. Need to advocate, keep bringing it up
- Had a quick conversation about it on TC channel on Slack, too
- TC could try to establish some norms, but to make any real change, Khalilah will probably be the point person
- MM, there will be more changes; starting to work on authority, and there is also bound-with part 2; not sure about 880 - now getting mapped to alternate titles or something; 245 can't be repeated, but in graphic representations they might be repeated; might need to be changes based on how discovery systems interact
- project management methodology has a solution for this called change control, has been around for decades; parties are identified and they give feedback
- App Interactions is also dependent on knowing about changes to data model
- would be good to have people in governance really thinking about this
- another example of an issue - in inventory a field is an integer, but in SRS it's not, and that can throw people for a loop; looking at it more closely could put a spotlight on these inconsistencies
- what about Support SIG? would they also be impacted? if new functionality is popping up, that would impact them as well
- subteams/individuals, please consider documenting examples of data model changes that went well or poorly
|
| Intro to SQL | 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 databases
- Selecting and sorting
- Filtering and limiting
- Aggregating and calculating
- Ordering and commenting
- Aliases
- Joins
|
| 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 - 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 - On going work on ERM data with LDlite
- Group started on first derived table as prototype to document this areas documentation on mermaid.
- ERM Prototype and Query Development Status
- Bi-weekly schedule (next meeting 7th, Decmber 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
Review and update Topics for Future Reporting SIG Meetings
|
|
|
|