2024-08-05 Reporting SIG Meeting notes

Date

Attendees

Present?

Name

Organization


Arthur AguileraUniversity of Colorado, Boulder
xSharon BeltaineCornell University

Erin BlockUniversity of Colorado, Boulder

Shannon BurkeTexas A&M

Suzette CanedaStanford University

Dung-Lan ChenSkidmore College

Lloyd ChittendenMarmot
xAnn CrowleyCornell University

Tim DannayMount Holyoke College

Axel DoerrerUniversity Mainz


Shelley DoljackStanford University
xStefan DombekLeipzig University
xJennifer EustisU. Massachusetts Amherst / Five College

Lynne ForsWellesley College

Lisa FurubottenTexas A&M
xMike GorrellIndex Data

Alissa HafeleStanford University
xKara HartWellesley College

Corrie HutchinsonIndex Data

Jamie JesanisMCPHS

Jeanette KalchikStanford University

Harry KaplanianEBSCO
xSarah KastenUniversity of Chicago

Tim KiserMichigan State University
xKevin KishimotoStanford University

Ingolf KussHBZ

Alexander LaoStanford University
xJoanne LearyCornell University

Eliana LimaFenway Library Organizationder

Eric LuhrsLehigh University

Kathy McCarthyEBSCO

Lisa McColl

Lehigh University

xLinda Miller

Cornell University


Joseph MolloySpokane Public Library

Kathleen Moore

Nassib NassarIndex Data

Elena O'MalleyEmerson

Tod OlsonUniversity of Chicago
xJean PajerekCornell University

Kimberly PamplinTexas A&M University 
xScott PerryUniversity of Chicago

x

Natalya PikulikCornell University

Emily SanfordMichigan State University
xBob ScheierHoly Cross

Vandana Shah

Cornell University


Linnea ShiehStanford University

Susie SkowronekOakland University

Ken SmithValdosta State University

Kimberly SmithMiddle Tennessee State University

Clare SpitzerStanford University

Amelia SuttonU. Massachusetts

Simona TabacaruTexas A&M

Huey-Ning TanStanford University

Vitus TangStanford University

Christie ThomasUniversity of Chicago
xIrina TrapidoStanford University

Catherine TuohyEmmanuel College

Patrick WaiteU. Mass Amherst
Visitors:




Discussion Items

Item

Who

Notes

Attendance & NotesScott

Attendance & Notes

  • Today's attendance-taker: Linda (or substitute)
  • Today's note-takers:  Team Leads for project updates


Announcements/Reminders

Scott

Announcements:


  • Wolfcon 2024 coming up in September
    • Here is a summary of information about WOLFCon 2024 from Jesse Koennecke:
      • Location and Dates: Senate House, University of London, September 24-26, 2024
      • Registration Open: Join us at Senate House, University of London. September 24-26, 2024. Register now through July 31, 2024 for an early bird discounted rate.
      • Learn more about WOLFcon 2024: Want to learn more about the Open Library Foundation and WOLFcon? Be sure to visit our website where you can learn more about the foundation, members projects, communities, and the annual conference.


  • Changes to the Reporting SIG meeting schedule
      • Reporting SIG meetings return a weekly schedule, still held at 11am ET on Mondays
      • Meetings are held on the first 4 Mondays of each month at 11:00 am Eastern U.S. time (see this time in your time zone). The first and third Mondays focus on Reporting Development topics, and the second and fourth Mondays focus on Reporting Business topics. 
      • "business" means topics like presentations on reporting functionality and new features, new reporting applications, surveys and studies on reporting, etc.
      • "development" means working on derived tables and report queries for the folio-analytics GitHub repository
      • "workshopping" queries could be scheduled during any of these meetings, and it would be great to have topics and/or questions in advance so we can prepare to walk through the answers/approaches, such as "how to I fix this inventory query to get rid of the duplicates?" or "what is the best way to calculate totals in this finance query?" 


Ongoing Topics:

  • Workshopping your queries
    • part of each Reporting SIG meeting will be devoted to time to work through any query questions you may have
    • please reach out to Christie Thomas if you have a question you would like to "workshop" during an upcoming Reporting SIG meeting


  • Impacts of New Fields and Features (Sharon)


  • Upcoming Reporting SIG meeting topics (tentative)
    • Reporting App use at various institutions


  • Any new members?
    • Welcome/introductions



SIG Recruitment:

We will need to be recruiting for a variety of roles in the coming months. Please consider whether you would be interested. Please reach out to Scott Perry or Sharon Beltaine with any questions.

  • Representative for the Documentation Working Group 
  • Query developers


Metadb Software Questions

Joanne Leary

Joanne will demonstrate 2 queries running in LDP and Metadb so we can discuss the comparison. The Metadb versions appear to be running more slowly. We'd like to determine why and next steps.

  • short samples
  • expense transfer query
  • split funds query

Notes:

-(Joanne)aggregating always makes the query run more slowly

-(Jenn) There is a different kind of indexing going on for Metadb; it may be reaching its maximum

-(Stefan)[for MARC 300 query]Is a LEFT JOIN required? Otherwise you could start from marc__t and then do an INNER JOIN to inventory_instances. Starting with the MARC table may help with speed

-(Mike) servers may not have the same throughput

-Next Step: Joanne and Sharon to send queries via email to Mike Gorrell for testing at Index Data


Review Outstanding Jira issuesStefan Dombek, Sharon, Scott

We will review the outstanding Jira Issues related to the EPIC UXPROD-1319 - Getting issue details... STATUS

  • (Stefan) Sometimes the issues are linked to other issues in Jira. When we close issues, others in the community can better see the status of dependencies.
  • (Stefan) All Jira issues for DBS have been decoupled. These issues have been given their own EPIC REP-293 - Getting issue details... STATUS .  The working group D-Reporting is working on these issues.

Next Step: Sharon and Scott will close the older open LDP Reporting Issues in the EPIC UXPROD-1319 - Getting issue details... STATUS


Reporting AppSharon

Are there any institutions running the Reporting App? If so, we'd like to collaborate with you on a plan for a demo of how different institutions are using the Reporting App. 


PC UpdateJennifer EustisNo Meeting this week
Lists App UpdateJennifer EustisThere is now the Lists App Resource Management Implementation Topic Tracker. Here you can see what issues are open. In the table below you can follow what is being discussed and propose new functionality for this app.
New Fields and AppsJennifer Eustis
  • new Serials app with Quesnelia
  • field for predictive patterns of Serials in Receiving 
  • Enumeration accordion changes come with a new field in the FOLIO item record called Display Summary

From Owen (PO of Serials App):

This field (Display Summary in the item record) originates in the Receiving app. It can be populated by using the Serials app for predictive patterns or can be populated manually in Receiving. The reason (or at least part of the reason) it was introduced was because of the existing enumeration & chronology properties were ambiguous and not used consistently across libraries. The Display Summary allows for a single string representation of the issue details e..g "Vol 1, Issue 6, Jun 2024" . Aleph breaks down the enumeration into levels and allows for multiple chronologies and I think there's still an argument we should do the same, but as an immediate solution using display summary at least gives a way of having a single field that brings together all the relevant information in a human readable way. From the Serials (predictive piece generation) side we had the same challenge - where does all the information go in the receiving piece (and so Inventory item) if there are several levels of enumeration, some alternative enumeration, multiple chronologies etc. So having a single text field (display summary) allows for us to at least generate something that is going to work for everyone, even if some would like to see a more granular breakdown of the information ultimatelyAnd means we can handle language differences OK as well (Vol. vs Bd. etc.)


From Khalilah:
I have a draft document about fields that are returning in the edge-rtac response with Q release. https://folio-org.atlassian.net/wiki/spaces/FOLIJET/pages/1395735/What+gets+returned+in+edge-rtac+response. This jira issue contains details as to when the Display summary field would be returned in the edge-rtac response https://folio-org.atlassian.net/browse/MODRTAC-107. You may want to discuss with EDS support where that information displays.



Recurring Items (Updated weekly, but not always discussed in meeting)

ItemWhoNotes
Review of In-Progress Projects (Recurring)


Review the release notes for FOLIO Analytics, LDP, LDLite, LDP Reporting App, ldpmarc, Metadb Projects (Recurring)


Updates and Query Demonstrations from Various Reporting Related Groups and Efforts Projects (Recurring)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.

D-A-CH Working Group (D-Reporting)

  • Ongoing topics: Workshopping, DBS statistics
  • Meetings: Contact Stefan Dombek if you would like to get a calendar invitation


Product Council


Reporting SIG Documentation Subgroup

  • Orchid documentation is live on https://docs.folio.org/docs/
  • Poppy documentation is in development
  • 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)


For all recent work on FOLIO Reporting SQL development: