Content Comparison

...

Meeting Notes

...

🗣️ Discussion Points:

1. Open Tickets Review (00:07:36 - 00:10:02)

   • Plan to review four-year-old tickets during every other Thursday, opposite the Reserves subgroup meetings.
   • We will review tickets by topic (indicated by labels in JIRA)
   • Next meeting scheduled for the 2/13/25 at 11AM US EST.
   • Spreadsheet created to track reviewed tickets.
   • Plan to send out topic in advance on Slack for discussion.
   • Historical knowledge of the project is valuable for ticket review.

2. SIP2 Module Presentation by Axel (00:12:07 - 00:49:06)

   • Overview of Work Done:
     • Axel Dörrer from UB Mainz presented on the SIP2 enhancement implemented by Index Data funded by UB Mainz for habis network. 
     • The module connects self-check machines to the library system.
     • Development phase: April 2023 to summer 2024
     • Maintenance phase: Fall 2024 to Fall 2025
   • Goals:
     • Implement work done by

...

1. • • Spokane Public Library into main development branch
     • Enable most common features on sorting and payment
     • Don't break existing behaviors
     • Keep functionality within FOLIO not within SIP2 module
     • Test new funcationaities on several vendor machines to ensure interoperability
     • Create convenient documentation for implementing institutions/vendors (still working on)

Overview of implementations by release

• Development phaise: April 2023 to summer 2024
• Maintenance phase: Fall 2024 to Fall 2025

Sorting extensions: Slides include development work and links to Jira tickets.

Payment extensions: GOSSIP provides the option to pay specific fee items on an account. Enhancements to Patron Information Summary and fee paid messages

Minor extensions: Patron information message, reject checkins on dedicated item statuses and adding PIN support.

Still to do: bug fixing, wrap up and extend documentation

...

1. • Sorting Extensions:
     • Added fields for department, location, call number, and destination location to empower sorting machines.
     • Sorting machines can implement their own logic based on the provided information.
     • Enhanced check-in messages to include sorting information.
   • Payment Extensions:
     • Enhanced fee payment functionalities to allow partial and distributed payments.
     • Added detailed fee item information in the patron information summary.
     • Enhanced fee paid messages to include detailed fee item information.
   • Minor Extensions:
     • Added patron summary information to the patron information messages.
     • Implemented rejection of check-ins for specific item statuses.
     • Added PIN support for authentication on self-check machines.
   • Questions?

     • Can you get title information and due date for paid fee message? Need to combine information using the barcode to pull item details. 

     • Is there the ability to use different characters as white space? Yes, you can use the fieldDelimiter in the config file.

     • Client wanted to allow multiple identifiers to authenticate in SIP2? Currently only allows one option. Is that a limitation of the standard or could it be implemented. UUID and userID is already implemented. Perhaps the client wants to include custom fields. It was pointed out the meeScan allows both SSO sign on and barcode.

     • What further improvements would you be looking for? Features are meeting needs at UB Mainz. Logging might need some improvement to track down issues more easily. Perhaps too much information logged making it harder to troubleshoot. Developing proxy support is a request.

...

1. • • Future requests should be written up as jiras

...

How are proxy borrowers working for folks?

🗣️ Discussion Points:

1. Open Tickets Review (00:07:36 - 00:10:02)
   • Plan to review four-year-old tickets during off weeks.
   • Meetings scheduled for the 13th at 11 AM.
   • Spreadsheet created to track reviewed tickets.
   • Plan to send out labels in advance on Slack for discussion.
   • Historical knowledge of the project is valuable for ticket review.

2. Administrative Issues (00:10:02 - 00:12:07)

   • Missing Thursday meeting from Susan's calendar.
   • Discussion on note-taking and transcription.

3. SIP2 Module Presentation by Axel (00:12:07 - 00:49:06)

   • Overview of Work Done:
     • Axel provided a comprehensive overview of the enhancements made to the SIP2 module.
     • The module connects self-check machines and sorting machines to the library system.
   • Goals:
     • Implement Spokane Public Library's fork to make it available for the entire community.
     • Enhance sorting and payment features to improve functionality.
     • Maintain existing behaviors to ensure no disruptions.
     • Test functionalities on various machines to ensure compatibility.
   • Sorting Extensions:
     • Added fields for department, location, call number, and destination location to empower sorting machines.
     • Sorting machines can implement their own logic based on the provided information.
     • Enhanced check-in messages to include sorting information.
   • Payment Extensions:
     • Enhanced fee payment functionalities to allow partial and distributed payments.
     • Added detailed fee item information in the patron information summary.
     • Enhanced fee paid messages to include detailed fee item information.
   • Minor Extensions:
     • Added patron summary information to the patron information messages.
     • Implemented rejection of check-ins for specific item statuses.
     • Added PIN support for authentication on self-check machines.
   • Maintenance and Documentation:
     • Ongoing maintenance to address any bugs and collect feedback.
     • Documentation work is still in progress to provide clear guidance for implementers.

4. Proxy Checkouts and Requests (00:49:06 - 00:59:08)

   • Challenges:
     • Proxy checkouts are supported, but proxy requests face challenges due to limitations in discovery layers.
     • Privacy concerns arise when proxies have access to sponsors' loan information.
   • Solutions and Workarounds:
     • Some institutions use workarounds, such as issuing PINs to sponsors for sharing with proxies.
     • Proxies can make requests on behalf of sponsors, but this often requires manual intervention at the circulation desk.
   • Potential Enhancements:
     • Enhancing discovery layers to support proxy requests seamlessly.
     • Allowing proxies to request renewals for all items on sponsors' accounts without seeing the details.
     • Implementing configurable options to manage proxy relationships and their permissions more effectively.
   • Discussion Points:
     • The need for better logging and tracking of proxy activities.
     • The importance of maintaining privacy while enabling proxy functionalities.
     • The potential for future development to address these challenges and improve the user experience.

✅ Decisions Made:

• Continue reviewing open tickets during off weeks.
• Use Slack to communicate labels for ticket review.
• Ensure transcription is done for meetings.

📌 Action Items:

...

1. • • .

📊 Data & Insights:

• The SIP2 module enhancements include sorting and payment functionalities, which are crucial for the project's success.
• Testing on various machines ensures real-world applicability.
• Proxy functionality needs careful consideration due to privacy concerns.

🔄 Follow-Up:

• Next meeting scheduled for the 13th at 11 AM.
• Regular reviews of open tickets every other Thursday.
• Continued maintenance and documentation work for the SIP2 module.

...