2025-04-28 Resource Access Meeting Notes

📄 Meeting Minutes

📋 Attendees:

• Cornelia – UB Mainz
• Susan – Role/Department not specified
• Thomas – Role/Department not specified
• Mark – Lehigh University
• Anja – Role/Department not specified
• Shelley – Role/Department not specified
• Tobi – Role/Department not specified
• Lisa – Leipzig University Library, Service Department
• Franziska – Product Owner, Project with Leipzig University Library
• Shirley – Role/Department not specified

🗣️ Discussion Points:

1. Introduction and Announcements (11:01 - 11:05)

   • Overview:
     • Susan welcomed attendees and shared personal updates about recent vacations.
     • Mentioned the upcoming EBSCO user group meeting in Providence, Rhode Island.
     • Noted that there would be no reserve meeting due to Olga's absence.
   • Decisions Made:
     • Cornelia to remove the regular meeting from the calendar.

2. Loan Anonymization as a User Preference (11:06 - 11:57)

   • Presentation by Lisa:
     • Institutional Background:
     • Leipzig University Library's cooperation project funded by the European Regional Development Fund.
     • Full migration to FOLIO as a new library system.
     • Current Practices:
     • Leipzig anonymizes loan data immediately after loans close due to GDPR regulations.
     • Dresden does not anonymize by default but does so upon patron request.
     • Proposal:
     • Implement user-specific loan anonymization settings in FOLIO.
     • Allow patrons to opt-in or opt-out of anonymization.
     • Discussion:
     • Thomas suggested using a dropdown for anonymization settings.
     • Anja proposed using the discovery layer for storing loan history.
     • Shelley raised concerns about GDPR compliance and data anonymization in circulation logs.
     • Susan emphasized the importance of developing loan and request anonymization functionalities in tandem.
     • Complications:
     • Synchronizing data between FOLIO and the discovery layer.
     • Ensuring user data is anonymized correctly without giving a false sense of security.
     • Decisions Made:
     • Lisa and Franziska to draft UXPROD tickets for loan and request anonymization.
     • Thomas to assist with mock-ups and provide feedback.

3. Technical Considerations and Next Steps (11:57 - 12:01)

   • Discussion:
     • Anja highlighted the need for performant data retrieval for patrons.
     • Thomas discussed the importance of clear anonymization policies and user settings.
   • Action Items:
     • Lisa to contact Dresden colleagues for feedback on current system performance.
     • Franziska to create draft UXPROD tickets and share with Thomas and Anne for review.

✅ Decisions Made:

• Remove regular meeting from the calendar due to Olga's absence.
• Draft UXPROD tickets for loan and request anonymization.
• Collaborate with Thomas on mock-ups and feedback.

📌 Action Items:

• Cornelia: Remove regular meeting from the calendar.
• Lisa: Contact Dresden colleagues for feedback on current system performance.
• Franziska: Create draft UXPROD tickets and share with Thomas and Anne for review.
• Thomas: Assist with mock-ups and provide feedback.

📊 Data & Insights:

• Leipzig University Library anonymizes loan data immediately after loans close due to GDPR regulations.
• Dresden Library does not anonymize by default but does so upon patron request.
• Synchronizing data between FOLIO and the discovery layer is crucial for accurate anonymization.

🔄 Follow-Up:

• Next meeting to discuss request anonymization with Amelia from user management.

🐝 JIRAs:

• JIRA:UXPROD-LoanAnonymization (Feature)
• JIRA:UXPROD-RequestAnonymization (Feature)

💻 Related Projects:

• Migration to FOLIO as a new library system.
• European Regional Development Fund project.