Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added notes for Users loans and Users search changes

...

Tableenhancer
numberOfFixedRows1



Functional AreaChange or AdditionConsiderationsAction timing,
Action required
CommentsContact person,
Related JIRAs
Affected app or moduleWhat has been changed or added that should be noted for this releaseWhat 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 personUser name of person that can provide additional detail.
Include issue link for bug fix, story or feature that applies
Inventory, SRS, Data importDefault MARC-Instance mapping updated to change multiple classification fields or repeated subfields within one classification field are handled

Libraries should review and decide: 

  1. If existing Instances should be refreshed against the updated map, so that all existing instances reflect these changes

See Update of mapping to correct handling of repeated classification fields and subfields for additional details.

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


Ann-Marie Breaux 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyMODDICORE-323

Inventory, SRS, Data import

Default MARC-Instance mapping updated to adjust punctuation handling for the 1xx/7xx contributor fields and for the $e/$j relator terms

If the library wants more name relator terms to be standardized, for searching and filtering, this update will help.

Libraries should review and decide: 

  1. If existing Instances should be refreshed against the updated map, so that all existing instances reflect these changes

See Update of mapping to adjust punctuation handling for 1xx/7xx contributors and $e/$j relator terms for additional details.

Follow the 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


Ann-Marie Breaux 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyMODDICORE-347

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyMODDICORE-355

Settings. Patron Overdue Policy. Reminder fee section.

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. 



Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-2015

Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-4159

Florian Ruckelshausen 

Charlotte Whitt 













Loan records. Add patron info and add staff info

Loan-related notes/comments (action based):

Two new buttons for adding this information is now available from the detailed loan display, and the check-out screen when clicking the three dots.



The notes/comments are searchable in the Circulation log app. 


Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-3913

Axel Dörrer 

Charlotte Whitt 

Patron notices

A new token supporting sending patron notices with the new patron information has been developed: 

{{loan.additionalInfo}}




Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-3913

Axel Dörrer 

Charlotte Whitt 

Julie Bickle 

Patron notices

7 new tokens for users primary address information supporting sending printed letters with a final reminder to patrons:





Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-4267

Florian Ruckelshausen 

Charlotte Whitt 

Julie Bickle 

Patron notices

Addition:

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.

UXPROD-3573.docx

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.


Julie Bickle 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-3573

Patron notices

Addition:

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.

UXPROD-3740.docx


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


Julie Bickle 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-3740

Patron notices

Addition:

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

UXPROD-3998.docx


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. 


Julie Bickle 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-3998

Patron notices

Mandatory change:

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. 

UXPROD-3999.docx


Mandatory change:

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. 


Julie Bickle 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-3999

Title level requestsAddition:
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. 
Consortia, mod-search

New env variable (CONSORTIUM_ENABLED=true/false) with default - false, defining whether module is in consortium mode or not.

New tenant initialization parameter (centralTenantId) to define tenant for db structure and indices creation.


Add CONSORTIUM_ENABLED=true env variable for environments with consortia enabled.

Pass 'centralTenantId' parameter on tenants initialization.


ConsortiumMod-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:

Steps to setup Consortia env

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 costAdditions:
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. 



OAI-PMHConsortial permissions required for multitenant settings.

Viachaslau Khandramai and Mikita Siadykh  please provide additional details.
Users Loans

When the "Anonymize all loans" button is clicked a confirmation modal will now appear before the anonymization takes place. 




UXPROD-3906

Amelia Sutton 

Users Search

The keyword search in the Users app will now match on a user's middle name. Therefore Users keyword search now matches on:

  • username
  • personal.firstName
  • personal.preferredFirstName
  • personal.lastName
  • personal.middleName
  • personal.email
  • barcode
  • id
  • externalSystemId
  • customFields



UIU-2860

Amelia Sutton 



New Apps


Removed Apps

Permissions Updates

...