What has been changed or added that should be noted for this release
What challenges may arise related to this change or addition
When can the action be taken (before, during or after upgrade)?
If applicable, detail what action(s) must be taken here
Is this action required for the next release?
Name of user leaving comment: comment on what you encountered or ask a question @mention Contact person
User name of person that can provide additional detail. Include issue link for bug fix, story or feature that applies
System wide
Refresh token support. Expiring token support. See the guide for more information.
Third party integrations that use non-expiring legacy tokens will need to be updated to use a new token endpoint during the deprecation period of Poppy. Within Poppy both the legacy and new login endpoints will be supported.
Integrations that use the edge API are unaffected.
System operators can configure access and refresh token TTLs through configuration documented here.
Follow instructions here for updating third party integrations and for configuration.
Follow the instructions to update the mapping rules.
Mandatory change.
Note that any revised mappings will only apply to Instances created or updated via MARC Bibs after the map is updated. To refresh existing Instances against the current SRS MARC Bibs and current map, the library may consider running Script 3 described here: Scripts for Inventory, Source Record Storage, and Data Import Cleanup
Note that any revised mappings will only apply to Instances created or updated via MARC Bibs after the map is updated. To refresh existing Instances against the current SRS MARC Bibs and current map, the library may consider running Script 3 described here: Scripts for Inventory, Source Record Storage, and Data Import Cleanup
The overdue policies has been extended with an additional section to define “Reminder fees”. The policy is defining the wanted process to bill reminder fees.
Reminder schedule. The process runs nightly and once per day. It creates the appropriate reminders for overdue items if an overdue policy with an active reminder fee section is in effect.
The process is honoring closed days, so if a service point is closed for a whole day the process does not create reminders on this day for the given service point.
Given: You have a lost item policy that charges the actual cost + a notice policy that sends notices with the existing trigger “Lost item fee(s), charged”, When: You bill the actual cost for an item that has aged to lost, Then: A notice is sent to the patron, according to the settings in the notice policy.
There are no new options or features in the notice policy or the notice templates; rather, the existing triggers have expanded their scope.
Please note: This ALSO works for items that have been declared lost.
Before upgrading to Poppy and/or switching to actual cost, please review whether your notice policies and/or templates (e.g. wording) need to or can be updated as a consequence.
Remember: Updates to a notice policy are applied when the open loan is next updated. Updates to the lost item policy are NOT applied to open loans.
Given: You have billed the actual cost for a lost item (both whether aged to lost or declared lost) + you have a notice policy that sends notices with the existing trigger “Lost item returned - fee(s) adjusted”, When: The lost item is checked in (returned), Then: A notice is sent to the patron, according to the settings in the notice policy.
There are no new options or features in the notice policy or the notice templates; rather, the existing triggers have expanded their scope.
Before upgrading to Poppy and/or switching to actual cost, please review whether your notice policies and/or templates (e.g. wording) need to or can be updated as a consequence.
Remember: Updates to a notice policy are applied when the open loan is next updated. Updates to the lost item policy are NOT applied to open loans
Lost item fees (set cost, actual cost and processing fee) can be bundled into one notice, overnight (or whenever you have agreed to with your hosting provider).
The functionality works the same as for notices trigged by the “Loan due date/time”:
There is a new “Mutliple fee/fine charges” token pair to add to the templates: #feeCharges & /feeCharges
For the triggering event “Lost item fee(s) charged”, there are two new options to select:
Send overnight with multiple lost item fee charges by patron. – This option will bundle any open lost item charges into one email (by standard, up to 100 charges). MUST contain the multiple charges tokens: #feeCharges & /feeCharges
Send throughout the day with one lost item fee charge per notice. – This represents existing functionality, and will be the default setting in your existing notice policies that use this trigger. MUST NOT contain the multiple charges tokens: #feeCharges & /feeCharges
Before upgrading to Poppy and/or selecting this option, please review whether your notice policies and/or templates (e.g. wording) need to or can be updated as a consequence.
Remember: Updates to a notice policy are applied when the open loan is next updated. Updates to the lost item policy are NOT applied to open loans.
Overdue fines can be bundled into one notice. The functionality is very similar as for check in and out notices:
There is a new “Mutliple fee/fine charges” token pair that MUST be added to the templates: #feeCharges & /feeCharges Otherwise, the notices will have an empty email body.
For the notice policy trigger “Overdue fine, returned”: The overdue fines generated in a single check in session are bundled when the check in session is closed.
For the notice policy trigger “Overdue fine, renewed”: The overdue fines are bundled when you renew multiple items at the same time.
Before upgrading to Poppy and/or selecting this option, you MUST update the relevant notice templates to include the multiple charges tokens. Otherwise, the notices will have an empty email body.
In addition, please review whether your notice policies and/or templates (e.g. wording) need to or can be updated as a consequence.
Remember: Updates to a notice policy are applied when the open loan is next updated. Updates to the lost item policy are NOT applied to open loans.
Addition: Institutions will now be able to choose to have title level request holds fail OR always succeed, following Circulation rules. (Through Orchid, holds can always be placed, regardless of Circulation rules).
When this setting is enabled, title level holds will work only when an item record is present. (A future enhancement will address title level holds when item records are not present)
Settings > Circulation > Title level requests. Select the box next to "Fail to create title level hold when request is blocked by circulation rule" to prevent holds from succeeding when Circulation rules do not allow them.
Mod-consortia can be enabled for libraries that want to share data between multiple FOLIO tenants.
Enabling this funcitonality will add additional functions and require at least one user account to have additional permissions to take advantage of these functions
Deployment instruction to setup consortia env is created:
Kitfox has already created an automation pipeline using this instruction for dev/testing needs for 4 tenants, FSE should create similar for prod usage for 61 tenants.
Serhii Nosko can you please add details here regarding actions and timing required to enable this funcitonality. thanks!
Fees/fines: Actual cost
Additions: Actual cost, fee/fine, and status details have been added to the Actual cost processing page. You can now access the processing page through the Action menu on the User details record. An "X" has been added to enable people to leave the processing page without needing to use the back button on the browser.
