...
Administrative topics
Re-branding
PC has asked that the name be changed as they found Reading room circulation requests confusing
Options:
In-house circulation*
close to in-house use-- could cause more confusion
In-house use only
In-library circulation
Building use only
Static request
Internal use
In-building use
New Figma site
Tokens
UI changes
Token insert
Date format
What date formats are needed
Staff notes - Delimantor between notes
Reauesttoken
today date:
Can they be controlled by the tenant local format - question ? requirement
Look at the loan due date see if that is using the tenant settings.
Format for the slips?
yyyy-mm-dd / mm-dd-yyyy
Reporting needs
Workflow details
If an item is checked in on the day the hold shelf expires should the hold be closed?
No - let it close at night
Non-usage clearance report? If a request is not used in X number of days it should be listed.
30-day guarantee time with a minimum use of 7 days between loans.
Meeting notes:
Overview
Participants engaged in a discussion regarding the potential rebranding of 'reading room circulation requests' to more generic terms, such as 'in-house circulation', to reduce confusion. Additionally, advancements in token implementation were covered, focusing on updates for date formats and the proposal to switch from the Mustache to the Handlebars templating engine. The meeting further explored regional date formatting needs, workflow specifics related to hold expiration, and distinctions between hold shelf and request expirations. Finally, a phased approach for implementing complex logic was proposed, alongside considerations for the impact on consortia support environments, leading to action items for follow-up, including UI refinements and assessments of implementation feasibility.
Notes
🏷️ Rebranding and Naming Concerns (06:38 - 16:16)
PC expressed confusion over 'reading room circulation requests' name
Suggestion to rename functionality to something more generic
Discussed alternative names:
In-house circulation*
close to in-house use-- could cause more confusion
In-house use only
In-library circulation
Building use only
Static request
Internal use
In-building use
📊 Token Implementation and UI Changes (16:
...
16 - 27:09)
New tokens added for staff slips and emails
Discussion about date formats for tokens
Discussion focused on the need for date formats in tokens to accommodate different regional standards.
Consideration was given to using locale settings to format dates appropriately for different libraries, such as US and European formats.
The group agreed on the necessity of a numerical representation based on tenant settings, while also discussing the potential for extended formats if required.
Proposal to replace Mustache templating engine with Handlebars for more flexibility
The Handlebars templating engine offers enhanced features such as flow control and variable checking, allowing for more complex logic in templates.
Switching to Handlebars would be a backward-compatible transition, minimizing disruption for libraries already using Mustache.
Implementing Handlebars could provide greater flexibility for custom templates, enabling libraries to tailor notices and slips to their specific needs.
Added new sections for date and request type tokens in the UI
📅 Date Formatting and Reporting Needs (27:09 - 38:54)
Discussed date format requirements for different regions
Suggestion to use locale settings for date formatting
Explored reporting needs for the new functionality
Discussed linking loan records to original requests for statistical purposes
🔄 Workflow Details and Hold Expiration (38:54 - 48:26)
Discussed behavior when an item is checked out on hold shelf expiration day
Considered whether to close hold or let it expire at midnight
Examined edit request screens for different request statuses
⏰ Hold Shelf and Request Expiration (48:26 - 57:03)
Clarified difference between hold shelf expiration and request expiration
Discussed need for guaranteed request checkout time and maximum request time
The Handlebars templating engine offers enhanced features such as flow control and variable checking, allowing for more complex logic in templates.
Switching to Handlebars would be a backward-compatible transition, minimizing disruption for libraries already using Mustache.
Implementing Handlebars could provide greater flexibility for custom templates, enabling libraries to tailor notices and slips to their specific needs.
Considered recalculating hold shelf expiration date after first checkout
Recalculating the hold shelf expiration date after the first checkout can provide flexibility in managing item availability.
This approach allows for a guaranteed usage window for patrons, ensuring they have sufficient time to utilize the item.
It can help streamline the process of clearing holds, reducing confusion for both patrons and staff regarding item availability.
🛠️ Implementation Phases and Future Considerations (57:03 - 01:05:48)
Discussed potential phased approach for implementing complex logic
Considered moving hold shelf expiration settings from service point to request policy
Raised concerns about impact on enhanced consortia support environments
Planned to consult developers about implementation feasibility and impact
Purposed layouts
Live mockups can be found on Figma:
...