2024-08-22 Agenda and meeting notes

Attendees:

@Nina Morgenstern @Andreas Mace @Uschi Klute @Jana Freytag @Stephanie Buck @Anne Ekblad @Thomas Trutt @Kajsa Bäckius @Cornelia Awenius @lisa perchermeier @Niels Erik Nielsen @David Bottorff @Amelia Sutton @Anja Kakau @Charlotte Whitt

Discussion Items:

• Administrative topics

• Outline of next meetings

• In / Out of scope: (firm decisions)

  • Items with no records

  • Manual changing of hold shelf expiration date (ILL workflows)

  • Delivery to areas other than Service points

  • Special service point configuration; restricted check-in and check-out

• Review of common workflow

• Where should the option for this request type live?

  • Separate request type

  • Extension of current request types

  • Switch on the request policy

  • Option on the new request form

Things to consider:

• Discovery layer changes

• changes to Edge APIs

General notes:

In this meeting, I’d like to solidify a few points and discuss the first part of the workflow. In this and the next meetings, I’d like to break the workflow into sections and focus on that section, trying to capture any requirements and possible issues.

Meeting notes:

🔍 Meeting Overview and Administrative Topics (00:12 - 10:54)

• Meeting focused on extending the request app for reading room circulation

• Agenda includes administrative topics, outline of next meetings, and in/out of scope items

📊 Scope Definition and Workflow Discussion (11:00 - 21:11)

• Discussed items with no barcodes, decided to keep out of scope

• Explored changing hold shelf expiration dates, left open for further discussion

• Agreed to keep delivery to areas other than service points out of scope

• Reviewed a simplified workflow diagram for requests

🛠️ Request Policy Options (21:11 - 30:09)

• Explored options for implementing reading room/persistent requests

• Discussed potential locations for the option within the request policy settings

  • The option could be added as a completely new request type under the existing request policies.

  • Another possibility is to have a setting that applies to all request types, indicating that the request is a reading room or persistent request.

  • A more granular approach could involve adding an option for each request type, allowing for specific configurations based on circulation rules.

• Considered implications for discovery layers and APIs

📝 Circulation Rules and Request Types (30:10 - 40:52)

• Examined circulation rules and request types in the test environment

• Discussed the need for mixture of persistent and non-persistent requests

• Considered use cases for different request types (page, hold, recall)

🔄 Request Modification and API Considerations (40:54 - 50:57)

• Discussed the ability to change existing requests into persistent requests

• Considered adding a section to review the edit request form and UI

  • Considerations for reviewing the edit request form and UI may include:

  • Identifying user experience improvements to streamline the editing process for requests.

  • Ensuring that the necessary fields for modifying request details are clearly labeled and accessible.

  • Evaluating the integration of new features, such as persistent request options, within the existing UI framework.

• Agreed on need to look at APIs for integrations with other systems

• Decided on an overall setting for persistent requests in the request policy

📚 Special Cases and Next Steps (50:58 - 57:04)

• Addressed special user groups with extended borrowing privileges

  • These groups may include staff members or specific patron categories that are allowed to check out reading room loans.

  • The circulation policies can be tailored to apply different loan policies based on user groups, allowing for flexibility in borrowing rules.

  • Special configurations can be established to ensure that certain items are only available for use by designated user groups, enhancing access control.

• Discussed potential solutions using circulation policies and loan types

  • Circulation policies can be tailored to allow specific user groups access to different types of loans, enhancing flexibility in managing requests.

  • Loan types can be utilized to differentiate between reading room loans and regular loans, allowing for distinct handling procedures based on item location.

  • Combining circulation policies with loan types enables libraries to create nuanced rules that cater to various patron needs while maintaining operational clarity.

• Planned to create a subfolder for notification templates

• Set agenda for next meeting to focus on emails, page slips, and templates

Decisions:

Action Items:

Tom

• Create a subfolder for notification templates under use cases (56:04)

• Add a page for templates in the main space (56:18)

• Try to get a list of all tokens and have them listed for the next meeting (55:34)

• Add a fourth section to look at the request app UI and edit forms (45:34)

• Reach out to devs to confirm if changes will require updates to discovery layer or edge APIs (48:07)

All participants

• Think about workflows, additional tokens, and layout options needed for next meeting (55:27)

• Share any existing templates for notifications in the newly created subfolder (55:57)

Charlotte

• Reach out to the National Library of Florence to see if they could join the group (54:07)

General Workflow

Open