Page Comparison

Announcements/Reminders

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.

• About the Reporting SIG meeting schedule
  
  • • 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)
  • Are there any new fields or features we should know about from any of the functional areas that may impact reporting?
  • Review and update the Impacts of New Fields and Features on Reporting grid 

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

• Any new members?
  • Welcome/introductions

• Representative for the Documentation Working Group 
  • urgently needed
  • work with reporting documentation team to  update Reporting section of FOLIO documentation for each FOLIO software release 
  • see https://docs.folio.org/docs/reporting/
• Query developers
  
  • ongoing need
  • work on derived tables and report queries for the FOLIO Analytics repository and to support Metadb
  • see https://github.com/folio-org/folio-analytics

Impacts of New Fields and Features

We'll review the current list of new fields and features with potential impact on reporting. 

• Review and update the Impacts of New Fields and Features on Reporting grid 

Donor field

• you can delete data in the old field, but cannot update or add new and still displays existing data; still interacting with data import mapping using the old field; Data Import will not see the new field until Ramsons
• half-implemented, which could be problematic
• new field is available to enter new donor information
• need to determine which derived tables need to be updated
• is used heavily at UChicago
• how to move old donor data to new field?
• used to be an open string on a PO line without validation of the donor information, whereas the new donor field is controlled - when you add a donor to a PO line, it will need to be validated against an organization

• 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.)

We'll review the latest status of derived table development:

• review latest FA issues at https://github.com/folio-org/folio-analytics/issues
• review latest FA pull requests at https://github.com/folio-org/folio-analytics/pulls

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. 

2024-08-08 Product Council Agenda & Meeting Notes

The FOLIO developer advocate updated the PC on progress on a new manual for developers. Then the PC discussed how to manage and track the type of progress members are interested in including climate. This is an ongoing discussion.