/
2025-04-02 Cross App SIG Meeting notes

2025-04-02 Cross App SIG Meeting notes

Owned by Tara Barnett
Last updated: May 28, 2025

 Date

Apr 2, 2025

Homework

Housekeeping

Convener and notes: Tara

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

Topics: https://folio-org.atlassian.net/wiki/spaces/AppInt/pages/665452545

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

5 min

Announcements

Tara

  • Next Session Ideas

  • WOLFcon Progress:

  • Wiki edit-a-thon in May?

 

Printing in FOLIO

 

  • We discussed printing in FOLIO previously on 2025-03-05. We looked at https://folio-org.atlassian.net/browse/FOLIO-3742 Folks took the ticket back to their SIGs. Informed by that discussion, we will try to refine this ticket. Our goal is to look for places where we want to make sure we have cross-app consistency. We envisioned individual apps defining their own use cases and creating tickets.

    • Notes from other SIGs?

    • Considerations

      • Is the use case printing, exporting, or reporting?

      • What common elements call for consistency?

        Should print buttons be standardized across apps?

      • Questions Brainstorming

        • Is it “print what you see” or “print what’s on the page no matter what’s open/closed”.

        • Should users be able to select specific accordions to print? Does that require a separate button?

        • Should there be consistency in what prints (open accordions vs. all data) when printing from the top of a page?

        • When printing from a search results list, should it print only visible results or all results (including pagination)? Selected results?

        • How should printing handle data that spans multiple related records (e.g., PO and PO line)?

        • Are we printing just data elements, or are action elements printed too? (Accordions, buttons, etc)

        • Is there any styling applied at all?

        • How should long tables and lists be formatted when printed?

        • How should the system handle hidden columns? Hidden fields if we ever get there?

        • Other questions?

Notes

During our discussion of printing functionality in Folio, we made significant progress in identifying what actually needs cross-app consistency versus what can be handled at the individual app level. We discovered that modal printing has serious issues - when users try to print modal windows, they often get inconsistent results with background content also appearing in the print output, and scrolling within modals can cause completely blank print results. We agreed this appears to be a bug that should be reported to John Coburn or Zach for investigation.

Regarding the placement of print functionality in the interface, we reached consensus that special print functions like "print order" should be placed in Actions menus rather than as standalone top-level icons. For general printing needs, the standard browser print function (Ctrl+P) is sufficient for "print what's on screen" functionality. This led us to also agree that all apps with keyboard shortcut lists should include Ctrl+P for printing the rightmost pane, ensuring consistency across Folio.

We made substantial progress in validating the original use cases by consulting with various SIGs. The ERM and Acquisitions SIGs reported they have no real printing needs, with existing browser printing and PDF export functionality being sufficient. Most metadata management printing requests turned out to be display issues rather than actual printing problems. We also determined that spine label printing is out of scope for this cross-app discussion since it's a specialized function rather than general screen printing.

The use cases that remain valid are limited. From Inventory, there's still the issue of printing selected records from the modal view, though this is affected by the modal printing bugs we identified. The Users SIG has a high-priority need for GDPR-required patron data printing, but this still needs proper specification. Resource Access use cases still need to be evaluated, though we expect these might be more substantial.

 Action items

@Tara Barnett will write up consensus points and post to cross-app SIG for feedback
@Tara Barnett will clean up the printing ticket https://folio-org.atlassian.net/browse/FOLIO-3742
@Maura Byrne will follow up with Users SIG to specify GDPR printing requirements with Ushi
SOMEONE will contact John Coburn/Zach about modal printing behavior issues
@Tara Barnett will plan a future discussion on which apps need to implement keyboard shortcuts to ensure consistency