/
2025-10-01 Cross App SIG Meeting notes

2025-10-01 Cross App SIG Meeting notes

 Date

Oct 1, 2025

Housekeeping

Convener and notes: Tara

For zoom link, see: AI Meeting notes

Recording: https://recordings.openlibraryfoundation.org/folio/app-interaction-group-wednesdays/2025-10-01T12:00/

Topics: 2025 Meeting and Topic Calendar

  • @Tara Barnett @Laura E Daniels @Martin Scholz @Kristin Martin @Jennifer Eustis @Kimberly Pamplin @Kimberly Smith @Kevin Kishimoto @Owen Stephens @Martina Schildt @Maura Byrne

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

5 min

Announcements

 

 

WOLFcon Actions

 

  • We had two pretty fun sessions. Unfortunately, the recording for the working session is lost in the electronic ether. Anyone take notes?

  • Any particular action items from WOLFcon?

    • The Search Standards documentation--need to take a step back and re-assess the tool, based on our meeting.

    • Decision and attendance tracking

      • What vectors do we need to consider for consensus? How wide do we need to reach in order to consider it a “community” decision?

    • From Owen: “I've just caught up with the WolfCon presentation by @j.coburn on user preferences (it clashed with one of our sessions so I missed it on the day). The Cross App Sig was mentioned. Do you think we could invite John / Kimie to a future meeting to look at this concept and whether there is any role for the cross app sig in moving it forward? (recording of session available at https://prod-zoom-recordings-openlibraryfoundation-org.s3.amazonaws.com/0e61535c-dd74-41d2-bcef-1ce3e66f69db[…]ared_screen_with_speaker_view(CC).mp4)”

 

In-App Reports

Jennifer Eustis

  • Reporting SIG: Inconsistent in app reports

    • Slides:

Notes

  • Announcements

    • In order to ensure we've got consensus and we understand where decisions are coming from, we're going to start taking attendance.

    • Upcoming Meetings: following up from WOLFcon, we plan to meet about the User Preferences work, the LOC presentation, and follow through on the Search and Standards documentation.

    • The SIG is requested to present their priorities to the PC sometime in the coming year.

    • Users SIG is restarting Eureka lab

  • Cross App Consistency for In-App Reporting

    • Jennifer Eustis from the Reporting SIG presented concerns about inconsistent in-app reporting functionality across FOLIO apps. She demonstrated how different apps handle CSV exports differently. Layout and options vary significantly, terminology differs, and functionality differs significantly. This means that users need to know what is available in each app.

    • Jennifer suggested a phased approach to bring the apps into alignment.

      • Phase 1: Export search results as CSV (minimum baseline)

      • Phase 2: Export all or selected items

      • Phase 3: Pick and choose fields

      • Phase 4: Additional functionality designated by SMEs

    • Discussion

      • We ask: what qualifies something as a report vs other data exports?

        • This recalls the printing conversation we had earlier in the year.

      • We note the challenge of mapping hierarchical FOLIO records to flat CSV format

      • We ask: should the Lists app handle this instead of individual app exports?

      • We note that the question of moving lists of identifiers seamlessly between apps (Inventory to Bulk Edit, for example) is outside the scope of what is being asked for here.

      • We ask: is the work to display only what is on the screen, or something closer to a true report?

        • Kimberly notes that Orders and Invoices exports are valuable because they provide more data than what displays on screen. Apps without any export capability (like Courses) are significant gaps.

        • Laura notes: Exporting what appears in Multi-Column Lists (MCLs) would be useful but might trigger many requests to modify MCLs

        • Is this the right way to solve this issue? The lack of universal FOLIO reporting options is forcing this as a workaround.

        • Owen suggested asking if Stripes could provide standard MCL-to-CSV export functionality

      • We note: there's a question of development time vs. whether basic exports would actually meet user needs. In many cases, exporting just what's on the screen wouldn't be that useful, even if it would make FOLIO more uniform.

      • What are people doing currently for workarounds?

        • Using Bulk Edit as a reporting tool, taking screenshots, using post-its, or even manual data manipulation across apps. Plus those who have Metadb use that, Lists sometimes works, and sometimes going straight to the APIs works as well.

    • Jennifer will be taking this back to the Reporting SIG and will let us know if there’s more we can help with.

 Action items