/
2025-03-10 Resource Access Meeting Notes

2025-03-10 Resource Access Meeting Notes

Owned by Cornelia Awenius
Last updated: Mar 12, 2025 by Thomas Trutt


Recordings

NOTE: RESOURCE ACCESS SIG USES EITHER ZOOM’S AI NOTES FUNCTIONALITY OR MICROSOFT COPILOT TO PROCESS THE TRANSCRIPT. If you would prefer that we do not use AI any session you attend, we are happy to! Please alert the convener at the start of the meeting.

Find all recordings here: https://recordings.openlibraryfoundation.org/folio/resource-access-sig/ (pw: folio-lsp)


Zoom

https://zoom.us/j/337279319 (pw: folio-lsp)

Attendees

Jana Freytag

David Bottorff

Thomas Trutt

Kajsa Bäckius

Mark Canney

Tobi Hines

Catherine Descanzo

Erin Weller

Christine Tobias

Susan Kimball

Cornelia Awenius

Magnus Andersson

Olga Kalachinskaya

Marie Widigson

Laurence Mini

Anja Kakau

Discussion Items:

Time

Item

Who

Description

Goals/Info/notes

5Min

Administrivia

Cornelia Awenius

Susan Kimball

Upcoming meetings

Note Taker: AI (Thomas Trutt)


55MinPrintingJana Freytag

Printing use cases from Circ Apps Printing in FOLIO

Printing in FOLIO - Overview

Goals:

  • Find a person to attend SIG meetings on printing in FOLIO.
  • Explore more use cases for RA (Resource Access) and Circ (Circulation).

Current Use Cases for RA/Circ Printing (see here: Printing in FOLIO)

  1. Staff Troubleshooting:

    • Printing part of a patron’s record (e.g., loan history, fee/fine history) to assist with issue resolution.

  2. Patron Record Copies:

    • Printing specific parts of a patron’s record (e.g., loan history) so they have a paper copy of their transactions.

  3. Receipt for Returns:

    • Patrons may request a printed receipt when returning books, especially if there have been past disputes (e.g., claim returned).

  4. Complete Patron Record (GDPR):

    • Patrons may request a printout of all their data in FOLIO (excluding internal comments) due to GDPR requirements.

  5. Circ Log Printing (question):

    • Printing the circ log to track circulation activities.

Further info on Printing in FOLIO:

  • Umbrella-Ticket: For more details on printing functionality, see FOLIO-3742.

Printing Types:

  • Screen Printing: Printing specific parts of a record on-demand (e.g., loan or fee history).
  • Notices & Labels: Automated system-generated notices (e.g., overdue notices, item labels).

How Printing Screens Works Now:

Fee/Fine History:

Loans:

Circ Log:

Next Steps:

  • Discuss gaps and needs in current printing functionality in the next SIG meeting.


Meeting Notes


🗣️ Discussion Points:

  1. Upcoming Meetings and Agenda (11:02:57 - 11:06:08)

    • Thursday: Backlog review session.
    • Next Monday: Discussion on the request override feature.
    • March 24th: Presentation on lists and bulk edit apps by Kathleen and Magda.

  2. Request Override Feature (11:03:39 - 11:05:33)

    • Clarification on the functionality of the request override feature.
    • Importance of the feature for various departments.

  3. Printing Use Cases in SIRCAP (11:06:55 - 11:28:24)

    • General Printing Needs:
      • Printing parts of the patron's record (loan history, fee history).
      • GDPR-related printing requirements.
    • Specific Use Cases:
      • Current Loans and Requests:
        • Printing a list of current loans and requests for patrons.
        • Ensuring the printout includes all relevant details, even if the list is long.
      • Checkout and Return Receipts:
        • Printing receipts for items checked out or returned.
        • Importance for equipment and reserves with attached fees.
      • Courses and Open Requests:
        • Printing lists of courses and open requests.
        • Useful for course reserves and managing requests.
    • Challenges:
      • Browser Printing Limitations:
        • Current browser functionality cuts off parts of the screen.
        • Need for better integration to print complete information.
      • Integration and Functionality:
        • Ensuring the system can handle various printing needs seamlessly.
        • Potential for developing specific print features within the apps.
    • Additional Insights:
      • GDPR Compliance:
        • Need for easy printing of patron data for GDPR compliance.
      • User Preferences:
        • Some users, especially older patrons, prefer physical printouts.
        • Legal advice in some libraries to provide printed returns receipts.

  4. Anonymization and Loan History (11:32:22 - 11:39:17)

    • Discussion on the ability to anonymize loan history.
    • Importance of user privacy and the ability to manage loan history visibility.

  5. Discovery Layer Integration (11:39:17 - 11:39:28)

    • Integration of loan history visibility in discovery layers.
    • Challenges faced by different libraries in implementing this feature.

✅ Decisions Made:

  • Request Override Feature: Confirmed the need for the feature and its high priority.
  • Printing Use Cases: Identified key use cases and agreed to bring them to the App Interaction SIG meeting.
  • Anonymization: Acknowledged the need for a feature to allow users to manage their loan history visibility.

📌 Action Items:

  • Susan: Prepare for the backlog review session on Thursday.
  • Jana: Document the printing use cases and present them at the App Interaction SIG meeting.
  • Olga: Check and bring any additional printing-related use cases from the course reserves subgroup.
  • Marie: Investigate the non-sticky column choice issue and report back.

📊 Data & Insights:

  • Printing Limitations: Current browser printing functionality is inadequate for the needs of the library system.
  • User Privacy: There is a significant need for features that allow users to manage their loan history and privacy settings.

🔄 Follow-Up:

  • App Interaction SIG Meeting: Jana to attend and present the printing use cases.
  • Next Meeting: Scheduled for Thursday to review backlog requests.



Related content