| Child pages (Children Display) | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Important Upgrade Considerations
This section outlines all changes that require special consideration for customers in production. Configuration changes may be needed to prevent operational interruptions. See checklist for guidelines on how to fill this out.
Changes and Required Actions
...
Functional Area
...
Change or Additions
...
Considerations
...
Action timing,
Action required
...
Comments
...
Contact person,
Related JIRAs
...
Affected app or module
...
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
...
Deployment
...
AWS S3 URL endpoint validation is more picky in Poppy
...
If using Amazon S3: Only an officially supported Amazon S3 endpoint URL is allowed in the S3 URL environment variables of modules. Example:
Wrong: AWS_URL=
...
https://s3-us-west-2.amazonaws.com/
Correct: AWS_URL=https://s3.us-west-2.amazonaws.com
...
Before upgrade change environment variables and secure store variables AWS_URLand S3_URL.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Deployment
...
Set SYSTEM_USER_PASSWORD environment variable for
mod-consortia
mod-data-export-spring
mod-dcb
mod-entities-links
mod-inn-reach
mod-pubsub
mod-remote-storage
mod-search
...
Module will fail on startup or when enabling a tenant if system user password is not set.
Consider setting a different SYSTEM_USER_NAME and a different SYSTEM_USER_PASSWORD for each module.
...
Before upgrade set environment variables/secure store variables.
The new password will be applied when migrating a tenant to the Poppy version of the module.
If changing the SYSTEM_USER_NAME from the default name or from the previous name the old system user still exists and must be manually disabled or deleted.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
System wide
...
Refresh token support. Expiring token support. See the guide how to configure for more information.
...
Third party integrations that use non-expiring legacy tokens will need to be updated to use the new authn/login-with-expiry token endpoint during the deprecation period of Poppy and Quesnelia. Within Poppy and Quesnelia both the legacy authn/login and new login endpoints will be supported.
Integrations that use the edge API are unaffected.
System operators can configure access and refresh token expiration (TTLs) as documented in the mod-authtoken READMEusing the new token.expiration.secondssystem property.
It is also possible to configure the token cookie SameSite attribute using LOGIN_COOKIE_SAMESITE environment variable. as documented in the READMEs of mod-login and mod-login-saml.
When the LOGIN_COOKIE_SAMESITE attribute is not set, it defaults to the more restrictive Lax attribute.
For system operators who are not using the FOLIO front-end and wish take full advantage of the enhanced security of expiring tokens, there is a new system property legacy.token.tenants in mod-authtoken. This property affects the system state in three ways.
When not provided or provided with a wildcard
*character, all tenants are legacy token tenants.When provided, with a comma separated list of tenant ids, only those tenants will be legacy token tenants.
When provided with an empty string value, no tenants will be legacy token tenants.
A legacy token tenant is a tenant for which a request to the legacy authn/login endpoint will not return a 404. See the readme of mod-authtoken for additional details.
...
Follow instructions here for updating third party integrations and for configuration.
In Poppy, backend modules default to using the new authn/login-with-expiry endpoint which issues expiring tokens. Enabling the legacy token endpoint through configuration does not disable this new endpoint. It only has the effect of exposing the legacy endpoint to requests for a given tenant allowing for a smother transition for clients which currently depend on the legacy endpoint.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Inventory, SRS, Data import
...
Default MARC-Instance mapping updated to change multiple classification fields or repeated subfields within one classification field are handled
...
Libraries should review and decide:
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 (Deactivated)
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
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:
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 (Deactivated)
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Data Import
...
This functionality enables libraries to reliably process large MARC 21 files through data import. When enabled, the system automatically splits large files into smaller parts, which are optimal for processing.
...
Data splitting functionality is currently an opt-in feature that is disabled by default and requires S3-compatible storage to use. Environment variables to control enablement/disablement are set at the cluster level for mod-data-import.
See detailed release documentation here: Detailed Release Notes for Data Import Splitting Feature#Suggestedvalues and user-level documentation here: DRAFT Overview: reliably process large MARC files
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
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 first reminder is scheduled at check-out based on the due date and the reminder fee configuration defined in this section. As the first reminder is sent the next reminder is scheduled according to this configuration, and so forth. A timed process is then defined in mod-circulation, to pick up due reminders, charge fees and send notices.
If the library does not use reminder fees then leave this section unfilled.
...
A new timed process is defined in mod-circulation to process reminders that have become due according to the configured reminder fees policy.
By default the process is scheduled to run once a day, at one minute past midnight in Central European timezone (00:01 CET) where it will pick up reminders that have become due since the most recent run.
The default timing of the process can be changed using Okapi's timer interface. Use Okapi's timer API to find the timed process at path "/circulation/scheduled-digital-reminders-processing" and follow the Okapi guide to set the desired timing of the process.
The process can be disabled entirely, if desired by tenants not using reminder fees. The Okapi guide describes how to disable a timed process as well. This is not required though, since simply letting the process run will have negligible impact on installations that do not use reminder fees.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Inn Reach listening to Kafka topics.
...
A new environmental variable INNREACH_TENANTS introduced which is mandatory and should contain the list of tenants for which mod-inn-reach module will be enabled.
...
The INNREACH_TENANTS variable is not set then the module will not start.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Requests, Request policies, Service points
...
For each type of request allowed in a Request policy, libraries will be able to specify which Service points are allowed for pickup (from among the Service points that are flagged as pickup SPs in Settings > Tenant > Service points).
The New Request form will be dynamic, enabling Title / Item information AND Requester information to determine available Request types and Pickup locations
Libraries will see a confirmation popup when changing a Pickup location from “Yes” to “No” as a reminder that this action will remove it from existing Request policies and affect all Circulation rules using the policies.
...
...
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 Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Patron notices
...
A new token supporting sending patron notices with the new patron information has been developed:
{{loan.additionalInfo}}
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Patron notices
7 new tokens for users primary address information supporting sending printed letters with a final reminder to patrons:
{{user.primarydeliveryAddressType}}
{{user.primaryAddressLine1}}
{{user.primaryAddressLine2}}
{{user.primaryCity}}
{{user.primaryStateProvRegion}}
{{user.primaryZipPostalCode}}
{{user.primaryCountry}}
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
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.
...
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.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
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.
...
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
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
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
...
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.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
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.
...
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.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Title level requests
...
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).
...
Via discovery: The TLR endpoint used by edge-patron tries Page, Recall, then hold when TLR is enabled. If you allow recalls, by policy, it will never fall back to TLR hold (if holds are also allowed by policy).
...
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.
...
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.
...
...
OAI-PMH - AWS S3/ MinIO Server
...
OAI-PMH uses AWS S3 or Minio Server for storing error logs generated by harvests
...
The environment will need to be configured as described in https://github.com/folio-org/mod-oai-pmh#environment-variables
...
Viachaslau Khandramai (Unlicensed)
...
OAI-PMH/Inventory storage
...
New field completeUpdatedDate has been added to the instance schema to improve OAI-PMH performance for incremental harvests (with from/until parameters)
...
Execute scripts as documented in Migration scripts for OAI-PMH
...
Execution of the script takes approximately 5 hours for 8 millions instance records.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Viachaslau Khandramai (Unlicensed)
...
OAI-PMH
...
A new property cleanErrorsInterval has been added to OAI-PMH technical configuration. The property defines for how many days the error logs are stored.
Retrieve OAI-PMH technical config via request: GET /configurations/entries?query=module="OAIPMH" and configName="technical".
Update config: PUT /configurations/entries/{id} with body included parameter
cleanErrorsInterval:
{
"id": "{id}",
"module": "OAIPMH",
"configName": "technical",
"enabled": true,
"value": "{\"enableValidation\":\"false\",\"formattedOutput\":\"false\",\"srsClientIdleTimeoutSec\":\"20\",
\"maxRecordsPerResponse\":\"50\",\"srsHttpRequestRetryAttempts\":\"50\",\"fetchingChunkSize\":\"5000\",
\"cleanErrorsInterval\":\"30\"}"
}
...
Additional information can be found in: https://github.com/folio-org/mod-oai-pmh#configuration
...
Viachaslau Khandramai (Unlicensed)
...
OAI-PMH
...
Columns path_to_error_file_in_s3 and started_date has been added to the request_metadata_lb table
...
Requests metadata table should be empty or clean up in case there are records before upgrading.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Data export
...
New field userId has been added to jobExecution schema for completed jobs filtering purposes
...
No action is needed. The migration script is executed automatically during the module upgrade.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Viachaslau Khandramai (Unlicensed)
...
Users Loans
...
When the "Anonymize all loans" button is clicked a confirmation modal will now appear before the anonymization takes place.
...
...
Settings > Users > Permissions
...
Added new accordion "Assigned users" when viewing a permission set in settings. If the logged in user has the "Users: Can view permissions assigned to users" permission, this accordion contains a table listing the name (Last name, First name) and patron group of each user who has the permission assigned.
If the logged in user has the "Users: Can assign and unassign permissions to users" permission assigned, a button will appear at the top of the accordion labeled "Assign/unassign" which will bring up a modal to search for users and assign or unassign them the selected permission set.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
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 with the "Text Field" or "Text Area" custom field types
...
Inventory, Call-numbers
...
Migration needed to correct call-number shelving order that is used for call-number browse:
recalculate based on call-number type specified in a record
recalculate for NLM and SuDoc call-numbers
...
2-action script: before and after upgrade
Instructions provided on the page: Call-numbers migration
...
...
Agreements
...
Increased memory requirements. Module descriptors updated to reflect these
...
In testing the latest release of mod-agreements is using slightly more memory. While it cannot be predicted how this will affect any particular environment it is recommended to review the updated module descriptors as per https://github.com/folio-org/mod-agreements/pull/684/files
...
Review available memory and MaxRAMPercentage used by mod-agreements
...
...
Agreements Local KB
...
New configuration KBIngressType controls whether external knowledge base data is obtained through a harvesting/pull model (where mod-agreements fetches data from external systems) or through a push model (where an external system pushes data into mod-agreements via an API endpoint)
The application determines which KBIngressType is to be used through an environment variable: INGRESS_TYPE
This can have the values:
Harvest (Default and used is no
INGRESS_TYPEenvironment variable is set)PushKB
...
Although the KBIngressType can be set via the environment variable, it is not recommended that a running system is switched between services.
While the PushKB ingress type has been tested in the hosted-reference environments (snapshot and snapshot-2) it has not yet been tested in a more production like environment where larger data sets can be loaded and where the use of this process over a period of time can be monitored for any issues
This being the case it is not recommended that mod-agreements v6.x.x is used with
ingressType = KBIngressType.PushKB
in a production environment without first running extensive testing
...
No action is needed to keep the population of the Agreements Local KB from an external knowledge base operating as previously as the default services used in mod-agreements v6.x.x is Harvest which is the same method as previous versions of mod-agreements.
...
In either configuration file upload (JSON or KBART) in the Local KB Admin module can still be used in addition to integration with an external knowledge base
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Agreements Local KB
...
The titleInstanceResolverService controls how resource data from external sources (added through external knowledge base integration, other system integrations or file upload). In mod-agreements v6.x.x a new service WorkSourceIdentifierTIRSImpl is added
The application determines which titleInstanceResolverService is to be used through an environment variable: TIRS
This can have the values:
IdFirst(Default and used is noTIRSenvironment variable is set)WorkSourceIdentifierTitleFirst
Although the titleInstanceResolverService can be set via the environment variable, it is not recommended that a running system is switched between services.
While the new WorkSourceIdentifier method has been tested in the hosted-reference environments (snapshot and snapshot-2) it has not yet been tested in a more production like environment where larger data sets can be loaded and especially in situations where the incoming data from external data sources interacts with existing data in the Agreements Local KB which may have been loaded from various sources
This being the case it is not recommended that mod-agreements v6.x.x is used with
TIRS = WorkSourceIdentifier
|
...
No action is needed to keep the population of the Agreements Local KB from an external knowledge base operating as previously as the default service used in mod-agreements v6.x.x is IdFirst which is the same method as previous versions of mod-agreements.
...
Whether it is being used or not introduction of the new WorkSourceIdentifierTIRSImpl method has resulted in a change to the processing of data added through file upload (JSON or KBART) in the Local KB Admin module.
The import documentation has been updated to reflect these changes and is available at https://drive.google.com/drive/folders/1YFZyKKm8NsqGJKC3EhMJPFBi57GBiyk7?usp=drive_link
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Requests, Discovery
...
New endpoints at edge-patron and mod-patron added that return available Pickup service points - This is a Discovery UX related enhancement (e.g., Locate and EDS).
Oleksandr Kurash
...
Export manager
...
migrated mod-data-export-spring to quartz implementation
...
No longer need to re-enable modules. Just install and enable once
...
This would be a consideration for after the upgrade
...
More than one mod-data-export-spring can now be run in parallel.
...
...
Invoices
...
Invoices can now be assigned to previous fiscal years. When processed all transactions will be made against the corresponding fiscal year.
...
Users will need specific permissions to perform this action (see below).
...
No action required
...
If ignored invoices will continue to apply to the current fiscal year.
...
...
Users
...
Integration with Kafka was added to mod-users.
...
Make sure that environment variables KAFKA_HOST and KAFKA_PORT are set before upgrading the module, otherwise mod-users startup fails with "Failed to construct kafka consumer".
Kafka events are sent only for ECS based envs by design, though.
...
...
Users
...
User type is a required field. For non-consortia environments, it is optional but can be used if desired through the UI.
...
In a consortia environment, users must be given a type of "patron" OR "staff". There is also a type of "system" and "shadow", "dcb" that is used by FOLIO to manage user accounts and access across members.
...
Can not be ignored when creating users as it will be required in ECS environments. In non-ECS environments selecting a value or leaving this field blank will have no consequence. If a value is set it will be possible to filter accounts based on this data.
...
...
Reporting (formerly known as LDP)
...
With the addition of two major new features (support for Metadb and pre-authored reports), the LDP app is now renamed Reporting. This reflects its ability to provide near-real-time information based on complex pre-authored reports.
The Reporting App is now compatible with Metadb.
...
To point to a Metadb instance, the configuration will need to be updated in the Settings → Reporting → Database Configuration.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Reporting (formerly known as LDP)
...
Using the 'Run Report' tab in the Reporting App, a user can run a report and specify input parameters against a query stored in a GitHub repository.
...
Documentation on how to write, store, connect, and publish reports used by this feature.
...
To use, a GitHub repository must be added in Settings → Reporting → Report repositories.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Authorities, mod-entities-links
...
mod-entities-links is required to deploy with tenant parameter: loadReference=true
...
...
Authorities
...
Authorities, authority note types, authority source files, and the authority reindex API have been relocated from mod-inventory-storage to mod-entities-links. The implementation remains consistent with the previous version, including APIs and permissions. The database schema was changed.
...
Migration script for existed authorities could be found on the page: Authorities migration
Upgrading mod-entities-links and mod-inventory-storage have to be done in one Okapi install request.
...
...
Search
Reindex for instance records are required.
mod-search reindex endpoint was updated (now it is possible to change index settings. Check MSEARCH-436 and MSEARCH-437for details.
...
...
quickMarc
...
mod-quick-marc does not support high availability (HA). Only one instance of the module should be running at a time.
...
...
Lists
...
New app
...
mod-lists needs an S3 bucket (or an S3-compatible bucket using something like MinIO or Ceph) in order to support exporting list contents
ui-lists depends on the Query Builder plugin (v1.0.2) being present in the Stripes bundle, so this will need to be manually included when building the bundle.
...
This should be set up prior to module installation, as the bucket name is a required system property. Without this, this function will not work
...
The module does work without an S3 bucket, however the list export functionality will not work.
...
...
FQM
...
New module
...
We highly recommend running mod-fqm-manager with read/write split, using the standard read/write split configuration, in order to prevent the module from impacting the performance of other FOLIO modules
...
This is not required, but is HIGHLY recommended
...
...
SRS, Data import (marc record matching)
...
MODSOURCE-601 requires the execution of scripts to populate marc_indexers version data for existing records so that existing marc records can be matched/found using marc fields other than 001, 999f$s, and 999f$i.
...
The scripts to populate marc_indexers version should be run after upgrading mod-source-record-storage from v5.6.7 (or lower) to v5.7.0.
During the module upgrade from v5.6.7 (or lower) to v5.7.0 it is recommended to set property srs.record.matching.fallback-query.enable = true to enable the fallback query, ensuring the lookup of records imported prior to v5.6.8 until these scripts have been completed.
After the scripts are completed, this property can be set to false (which is the default value) in order to avoid fallback query execution, as it will be redundant once the scripts are finished.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Requests
...
Request field fulfilmentPreference has been renamed to fulfillmentPreference
...
This is a breaking change. All third party integrations that use request related APIs (like /circulation/requests... or /request-storage/requests...) need to change the spelling of this field name accordingly.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Domain events (mod-pubsub)
...
Fallback credentials for mod-pubsub's system user have been removed from the code.
...
Before Poppy, libraries could use optional environment variables SYSTEM_USER_NAME and SYSTEM_USER_PASSWORD to override default user credentials. Now these variables become mandatory. If they are not present in the system, mod-pubsub will crash immediately after start.
...
Set environment variables SYSTEM_USER_NAME and SYSTEM_USER_PASSWORD (if they are not present) before upgrade.
...
Alexander Kurash
Oleksandr Vidinieiev
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Dashboard
...
A new mechanism for storing dashboard layouts has been implemented. To ensure existing dashboards (i.e. migrated from previous versions) are setup to use this new mechanism a special admin job is required
Only relevant for those upgrading from previous versions of Dashboard where dashboards have already been created. New dashboards created after the upgrade are not affected.
...
...
To make mod-search consume all types of changes for instances, holdings, items, and changes related to bound-with functionality it has a consumer with a default Kafka topic pattern:
| Code Block |
|---|
(${ENV}\.)(.*\.)inventory\.(instance|holdings-record|item|bound-with) |
This pattern could be changed by setting KAFKA_EVENTS_CONSUMER_PATTERN environment variable.
...
If the library requires the default behavior of mod-search, please ensure that the KAFKA_EVENTS_CONSUMER_PATTERN is either omitted from the environment variables or is set to the same value as the default pattern.
...
...
mod-circulation
...
Integration with Kafka was added to mod-circulation.
...
Without valid Kafka configuration the module will crash at startup.
...
Make sure that environment variables KAFKA_HOST and KAFKA_PORT are set before upgrading the module.
...
More information on supported environment variables and their default values can be found in mod-circulations README.
...
Oleksandr VidinieievAlexander Kurash
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
mod-entities-links
...
Needs authority data copied from consortium central tenant to consortium member tenant when enabled for new consortium member tenant
...
Without authority data in member tenant instance-authority link propagation will be broken and reports exported from member tenant may miss data.
...
Execute 2 scripts to copy data from a central tenant to a new member tenant
Adding a new member tenant to consortium. mod-entities-links scope
...
Only in consortium environment for a member tenant
...
...
Data Import Job Profiles (mod-di-converter-storage)
...
Changed structure of storing links between profiles.
...
Some links to reusable Action Profiles might be missing after the migration.
...
After migration review existing Job Profiles to verify they migrated correctly. Pay attention to reusable Action Profiles. In case issues are found Job Profile can be updated manually. For additional information on links created for that Job Profile - execute script #15 (or follow the link), notify support.
|
...
After updating to mod-service-interaction 3.0.3 (included in Poppy CSP #1):
With a user with the “Dashboard: Dashboard administrator” permission allocated
GET <okapi base URL>/servint/admin/ensureDisplayData
Expected response:
200 OK
| Code Block |
|---|
{
"status": "OK"
} |
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Changes and Required Actions Only Concerning Systems With Enhanced Consortia Support Enabled.
Poppy includes a set of functionality that can be enabled to allow multiple FOLIO tenants to collaborate on supported workflows. This functionality is NOT enabled by default and should not impact features and configurations required for implementations that have not enabled this feature set.
...
Functional Area
...
Change or Addition
...
Considerations
...
Action timing,
Action required
...
Comments
...
Contact person,
Related JIRAs
...
Affected app or module
...
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
...
Enhanced Consortia Support
...
Added mod-consortia and ui-consortia-settings
...
Added for libraries that would like to run a multi-tenant FOLIO system. Please review the following documentation Steps to setup Consortia env. This will instruct you as to how and why you would enable this functionality.
...
Configuration takes place after the upgrade
...
Applicable only for multi-tenant FOLIO customers. If site is not multi-tenant the are no actions required to disable these functions.
...
...
Consortia, mod-search
...
A new tenant initialization parameter, "centralTenantId," is introduced to specify the tenant for database structure and index creation. This parameter is necessary because Elasticsearch indices and the database schema should only be generated for the central tenant. If the parameter is omitted, the tenant is assumed to be "not in consortia," and the indices and database schema are created. If the parameter is provided and it differs from the tenant for which the module is enabled, the tenant is considered a "member," and the indices and database structure are not generated.
This parameter is exclusively required for consortium-like environments and should be provided to all tenants within the consortium, both central and member tenants.
To pass the 'centralTenantId' parameter during the initialization of all consortium tenants (with the value of the central tenant ID), it should be included in the 'tenantParameters' parameter in the same way as we handle 'loadReference' and 'loadSample'. The format would be:
| Code Block |
|---|
/install?tenantParameters=centralTenantId=<central_tenant_id> |
...
...
OAI-PMH
...
Consortial permissions required for institutional user when harvesting in consortial multitenant settings.
...
user-tenants.collection.get permission needs to be assigned to institutional user
...
Additional information: https://github.com/folio-org/edge-oai-pmh#multi-tenant-consortia-harvesting-setup
...
Viachaslau Khandramai (Unlicensed)
...
Login
...
Changes made to mod-consortia, mod-login, mod-users, mod-authtoken. Username is unique across member tenants
If the cluster has existing users - all they should be processed by the consortium pipeline: Steps to setup Consortia env. The process of adding tenants to the consortium will take care about migration of existing users that have a type that does not equal to 'patron' or 'dcb'.
...
For Forgot email/Forgot password functionality make sure that config entries for module 'USERSBL' like: 'FOLIO_HOST', 'RESET_PASSWORD_UI_PATH' populated for each tenant in the consortium. So no new params added, just make sure that all existing ones are populated for each tenant.
For mod-authtoken to be able to do cross tenant requests for ECS based envs need to populate system property: 'allow.cross.tenant.requests=true'
...
Make sure that the DB schema for the central tenant is located in the DB cluster as schemas for all other tenants in the consortium.
...
...
Consortia manager
...
In an environment that has consortia functionality enabled (see above) There is now an area in settings where consortia membership can be edited.
...
Membership can only be edited in the UI. To add or remove members you must use APIs (see above for more info)
...
After migration
...
...
Consortia manager
...
Settings areas that can be manipulated via the consortia manager now have a "source" field with a possible value of "consortium" OR "local"
...
No action is required but users should be aware they can only edit settings with source "local" unless they're in Consortium Manager.
...
N/A
...
...
Users
...
User type is a required field. For non-consortia environments, it is optional but can be used if desired through the UI.
...
In a consortia environment, users must be given a type of "patron" OR "staff". There is also a type of "system" and "shadow", "dcb" that is used by FOLIO to manage user accounts and access across members.
...
Can not be ignored when creating users as it will be required in ECS environments. In non-ECS environments selecting a value or leaving this field blank will have no consequence. If a value is set it will be possible to filter accounts based on this data.
...
New Apps
...
App
...
Description
...
Comments/notes
...
Product Owner
...
mod-consortia
...
Backend module that enables workflow collaboration between FOLIO tenants
...
Not included in FOLIO platform complete
...
...
ui-consortia-settings
...
UI module that surfaces workflow collaboration functionality in FOLIO systems with mod-consortia enabled
...
Not included in FOLIO platform complete
...
...
mod-lists
...
Backend module responsible for persisting the metadata and the contents (IDs) of lists.
...
...
ui-lists
...
UI module that is used to create and manage Lists which are queries across multiple modules (for example: find all items marked as missing or declared lost, or find all open loans assigned to inactive users.
...
...
mod-fqm-manager
...
FQM (FOLIO query machine) is the engine that takes in queries, processes queries, and provides answers. FQM consolidates data from different modules within FOLIO in real time, allowing users to conduct cross-application searches efficiently.
...
...
edge-fqm
...
Provides an ability to retrieve query and entity type information from FOLIO.
...
The purpose of this edge API is to bridge the gap between 3rd party discovery services and FOLIO mod-fqm-manager module.
...
Removed Apps
Permissions Updates
...
App
...
New Permissions
...
Deprecated Permissions
...
Product Owner
...
Users
...
Following permissions are necessary for users who will be assigning patron and staff info to the loan record:
Users: User loans: add patron information
Users: User loans: add staff information
...
...
Settings > Tenant
...
ui-tenant-settings.settings.location.view- "Settings (Tenant): View locations" - this will allow users to view the tenant location tree but be unable to create, update or delete institutions, campuses, libraries or locations
...
...
Invoices
...
Invoice: Pay invoices in a different fiscal year - This will allow users to specify the fiscal year of an invoice for processing in that year. Even without this permission users will now be able to see the assigned fiscal year of an invoice record.
...
N/A
...
...
Consortia manager
...
Consortia: Assign and unassign affiliations - Allows a user to add or remove affiliations of other users
...
Consortia: View affiliations - Allows a user to view the affiliations of other users
...
Consortium manager: Can create, edit and remove settings - Allows a user to perform build create, edit and delete actions via the consortia manager BUT user must also have correct permissions in individual tenants to carry out these actions
...
Consortium manager: Can share settings to all members - Allows a user to create settings that will be shared by all members and only editable in the central tenant.
...
Consortium manager: Can view existing settings - Allows a user to view all the settings of members they are affiliated with via the consortia manager
...
Settings (Consortia): Can view and edit consortia membership - Allows a user to view and edit the details of the list of members in the settings app of the central tenant.
...
Settings (Consortia): Can view consortia membership - Allows a user to view the details of the list of members in the settings app of the central tenant.
...
N/A
...
...
Settings > Users
...
New Invisible Permissions:
Settings (Users): Can view manual charges - Allows a user to view the Manual Charges section of Users Settings
Settings (Users): Can view if comment required - Allows a user to view the Comment Required section of Users Settings
Settings (Users): Can view waive reasons - Allows a user to view the Waive Reasons section of Users Settings
Settings (Users): Can view payment methods - Allows a user to view the Payment Methods section of Users Settings
Settings (Users): Can view refund reasons - Allows a user to view the Refund reasons section of Users Settings
Settings (Users): Can view owners - Allows a user to view the Owners section of Users Settings
Settings (Users): Can view transfer accounts - Allows a user to view the Transfer Accounts section of Users Settings
Settings (Users): Can view patron blocks conditions - Allows a user to view the Conditions section of Users Settings
Settings (Users): Can view patron blocks limits - Allows a user to view the Limits section of Users Settings
Settings (Users): Can view patron blocks templates - Allows a user to view the Templates section of Users Settings
Permissions Renamed (new names in bold):
Settings (Users): Can create, edit and remove feefines renamed to Settings (Users): Can create, edit and remove manual charges
Settings (Users): Can create, edit and remove comments renamed to Settings (Users): Can edit if comment required
Settings (Users): Can create, edit and remove waives renamed to Settings (Users): Can create, edit and remove waive reasons
Settings (Users) Can create, edit and remove payments renamed to Settings (Users): Can create, edit and remove payment methods
Settings (Users): Can create, edit and remove feefines renamed to Settings (Users): Can create, edit and remove manual charges
Settings (Users): Can create, edit and remove refunds renamed to Settings (Users): Can create, edit and remove refund reasons
Settings (Users): Create, edit, and view departments renamed to Settings (Users): Can create, edit, and view departments
Settings (Users): Create, edit, view, and delete departments renamed to Settings (Users): Can create, edit, view, and delete departments'
Permission Renamed and made Invisible (new name in bold):
Settings (Users): View departments renamed to Settings (Users): Can view departments and made invisible
New Visible Permissions:
Settings (Users): Can view general entries - Allows a user to view all sections under the General header in Users Settings (Permission sets, Patron groups, Address Types, Departments, and Custom Fields)
Settings (Users): Can view feefines-related entries - Allows a user to view all sections under the Fee/fine header in Users Settings EXCEPT Transfer criteria (Owners, Manual charges, Waive reasons, Payment methods, Refund reasons, Comment required, and Transfer Accounts)
Settings (Users): Can view all patron blocks entries - Allows a user to view all sections under the Patron blocks header in Users Settings (Conditions, Limits, and Templates)
Settings (Users) View all settings - Allows a user to view all sections in Users Settings (EXCEPT Transfer criteria).
...
...
Users
...
Renamed (new name in bold):
Users: Can create new user to Users: Can create and edit users
...
...
Inventory/quickMARC
...
quickMARC: Create new MARC bibliographic record: Required for users to be able to create a new MARC bib record via a new option in the Inventory actions menu
...
N/A
...
...
Bulk edit
...
Permissions Renamed (new names in bold):
Bulk Edit: In app - View renamed to Bulk Edit: In app - View inventory records
Bulk Edit: In app - Edit renamed to Bulk Edit: In app - Edit inventory records
Bulk Edit: (CSV) View renamed to Bulk Edit: Local - View user records
Bulk Edit: (CSV) Edit renamed to Bulk Edit: Local - Edit user records
Bulk edit: In app - Update user records renamed to Bulk Edit: In app - Edit user records
Bulk edit - Can view logs renamed to Bulk edit: Can view logs
Bulk edit: Query renamed to Bulk edit: Can view logs
Additional information about Bulk edit permissions can be found here.
...
N/A
...
...
Sip2 new commands implemented
...
As part of poppy new commands have been implemented -
Patron Status Request, Fee Paid, Item Information, Renew All, Renew
...
...
Organization Settings
...
Settings (Organizations): View settings
...
...
Acquisition units Settings
...
Settings (acquisition units): View acquisition units
...
...
Finance Settings
...
Settings (Finance): View settings
Settings (Finance): Export fund and expense class codes
...
...
Lists
...
New Visible Permissions:
Lists (Enable): Can view Lists - Allows a user to view Lists and List details
Lists (Edit): Can edit Lists- Allows a user to view, edit, and refresh Lists
Lists (Export): Can export Lists- Allows a user to view, edit, refresh, and export Lists
Lists (Delete): Can delete Lists- Allows a user to view, edit, refresh, and delete Lists
Lists (Delete): Can delete Lists- Allows a user to view, edit, refresh, and delete Lists
Lists (Admin): Can perform all operations on Lists- Allows a user to view, edit, refresh, export, and delete Lists
...
Known Issues
General
...
App
...
Known issue
...
Workaround
...
JIRA issue
...
Product Owner
...
Title level requests
...
Recalls are unevenly distributed when there is no item to page and there is at least one item that is not checked out but is "available" for a recall to be placed upon
...
...
...
Inventory (mod-search)
...
Call number browse using call number prefix/suffix in search string doesn't show an exact match
...
Do not use prefix/suffix as a part of search string for call number browsing
...
...
...
Inventory
...
Effective location (item) facet: In this release, if items on a single Instance have call numbers of different call number types, when browsing by a specific type, the locations of all items on that Instance will appear in this facet.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Inventory
...
Effective location (item) facet: In this release, when call numbers have a type and a custom location, they will not show in call numbers (all) option. Will be addressed in future refactor.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Bulk edit
...
Query tab has been hidden until the backend work is completed.
...
...
...
FQM/Lists
...
FQM queries can be very slow, depending on many factors. This is most visible in the new Lists app.
...
Avoid using the "contains" operator for string fields. Instead, prefer the "=" and "starts with" operators when possible. Also, provide as many filtering criteria as possible when creating queries.
...
...
Inventory
...
Call number browse: If the call numbers on holdings on different instances contain the same first 10 characters of the shelving order, the preceding records will not be returned
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Settings > Circulation > Fee/fine > Overdue fine policies. Accordion: Reminder Fee
...
When viewing the new accordion Reminder fee, the first five selection options are frozen:
Count closed days/hours/minutes
Ignore grace periods for recalls
Ignore grace periods for holds
Allow renewal of items with reminder fee(s)
Clear patron block when paid
This is new work being worked on for Quesnelia (R1 2024)
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Florian Ruckelshausen Charlotte Whitt
...
Settings > eholdings > Create a new Knowledge base configuration
...
Customer ID and password fields are auto-populated with FOLIO login details due to Chrome browser not autocomplete = off. See https://bugs.chromium.org/p/chromium/issues/detail?id=914451
...
...
ECS: Inventory > Call number browse
...
In member tenants, when users select a tenant in the Held by facet for a tenant other than the one that created created the call number will result in the placeholder being placed at the top of the results list regardless of alphabetical order.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
ECS> Loading authority records and adding a tenant
...
If shared authority records are already loaded into the central tenant and a new member tenant is added, shadow copies are not created in the new member tenant so users cannot link shared MARC bibs to shared MARC authorities.
...
Ensure all member tenants are created before loading shared MARC authorities.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Circulation/inventory
...
We have observed performance issues in operations which involve publishing Kafka-events on Orchid and Poppy Bugfest environments. Processes such as check-ins, check-outs, requests, loan updates and others would occasionally freeze for 10-20 seconds.
...
The issue was fixed by pointing Bugfest environment to a dedicated Kafka cluster instead of the one shared by 40+ environments. If you observe similar issues on your environment, and you are using a shared Kafka installation which is under high load, please consider using a dedicated Kafka.
...
Alexander Kurash
Eldiiar Duishenaliev
...
ECS: Inventory > Search
...
Effective location (item) & Held by facets
Effective locations can be search in the Effective location (item) facet. However, the incorrect number of entries is showing in the facet.
...
Users may have to click the "+More" button more than once to see the remainder of entries.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
Additional known issues (Reminder change filter to Release = Poppy)
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Notes on functionality
...
App
...
Notes
...
Jira
...
Product Owner
...
Requests
...
Optional columns now available: Effective call number string and Pickup service point. They can be added in the Actions dropdown. Both columns are sortable. When sorting the effective call number string column, the sort is based on a normalized effective call number string (effective shelving order) which excludes prefixes from the sort. A user can do a basic "starts with" search for a call number, with or without a prefix. If the search within Requests begins with the call number (no prefix), it will only search the call number. It will not yield results for any searches that include information beyond the call number (e.g., suffix, copy number +).
...
...
...
Settings > Tenant > Locations
...
Improvement in UI for navigating through the location tree in Settings. The number on "institution" now links to the number of campuses; The number on "campus" now links to the number of libraries; the number on "libraries" now links to the number of locations.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
(OLD ACCOUNT) Erin Nettifee until mid-August
...
Settings > Tenant > Locations
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
(OLD ACCOUNT) Erin Nettifee until mid-August
...
Circulation rules
...
The circulation rules now have the metadata object, allowing libraries to see who last updated the rules and when.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
(OLD ACCOUNT) Erin Nettifee until mid-August; after, ask in #resource-access
...
Bulk edit
...
The Bulk edit app allows suppressing from discovery item and holdings records.
The app also supports bulk editing item notes. The functionality covers adding a new note, changing the note types, duplicating circulation notes, updating part of the note and removing notes.
...
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
...
OAI-PMH
...
New option has been added to allow libraries to harvest from inventory only. This id the extension of the previously supported harvests from SRS or SRS and Inventory.
OAI-PMH will provide information about bad data encountered during the harvest so that the data can be corrected by libraries without the need to reaching out to hosting providers. The logs of bad data are available in the OAI-PMH settings page and are available for up to 30 days after the harvest completed.
OAI-PMH performance has been further improved and supports up to three concurrent harvests (two full and one incremental).
For the consorcial implementations, in addition to the tenant level harvests, OAI-PMH supports also cross-tenant harvests allowing one harvest started in the central tenant to harvest data from all tenants continuously.
...
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
...
Data export
For consortial implementations, data export supports exporting shared instance records from member tenants.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
...
Inventory > Advanced search modal
New modal in Inventory to perform advanced searches
...
Search options:
Contains all
Exact phrase
Starts with
...
Boolean operators
AND
OR
NOT
...
Out of scope for current iteration
Contains any search option
Reconsideration of word-stemming for Instances coded as English
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
...
Inventory > Create original MARC bib
...
Added functionality to create original MARC bibliographic records from the quickMARC UI, accessed via a new Action in Inventory. Requires new permission: quickMARC: Create new MARC bibliographic record
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
...
quickMarc
...
Bibliographic records: proper order added for field 008
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
quickMarc
...
Added display of the link button in the reference view, when adding a term to a bibliographic records from the authority.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Inventory > Create bound with relations
...
Added functionality to add bound with relations as one item linking to multiple holdings using the edit function in Inventory
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
...
Inventory > Call number browse by type
...
Added the ability to browse by specific call number types: Dewey, LC, Local, Other scheme, SuDoc, and NLM. Added normalized sorting for both SuDoc and NLM. Note that in order to support this implementation, the mentioned types are now uneditable in the Inventory settings.
All call numbers can still be browse interfiled in the Call numbers (all) option.
Effective location (item) facet: In this release, if items on a single Instance have call numbers of different call number types, when browsing by a specific type, the locations of all items on that Instance will appear in this facet.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Automated authority linking > Changing which linkable MARC fields can be enabled for automatic linking permission.
...
The permission which allows a user to update automated linking rules (enable or disable field for automated linking) is not assigned for admin user by default.
There is only one way to add this permission to the user - sending request via Postman to include this back-end permission "instance-authority.linking-rules.item.patch" in the list of user's permissions.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
...
Settings > Circulation > Fee/fine > Overdue fine policies. Accordion: Reminder Fee
Business logic for scheduling Reminder fees is implemented, and it's possible to set up and send reminders to patrons via email.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Florian Ruckelshausen Charlotte Whitt
...
eholdings aop > Packages facet
...
Feature: eholdings app Packages facet
What: Ability to filter title results by Packages facet
Note:
The facet is only available on the eholdings app's Titles search tab
Single select only
Returns packages that contain search query
Title detail record will filter to selected package facet value
Screencast: https://issues.folio.org/secure/attachment/61199/61199_UIEH-1351-verified.webm (login into JIRA to see it)
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
...
Title level request holds
...
Libraries can now choose whether title level holds should fail or succeed, based on circulation rules. (Through Orchid, holds always succeeded, regardless of circulation rules)
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
PO Release Presentations
Please include links to any slide decks and recordings
...
Topic
...
Presentation Date
...
Presenter
...
SIG Meeting (date)
...
Notes
...
...
4/20/23
...
...
...
(starting at 5:35 in the meeting recording)
Loan. New staff and New patron info, incl. new token for patron notices
...
10/16/23
...
...
...
Starting at 7:30 in the recording
...
...
11/13/2023
...
...
...
Starting at 10:17 in the recording
...
Inventory advanced search modal
...
9/6/23
...
...
...
Starting at 44:50 in the recording
...
Inventory - create bound with relations (one item linked to multiple holdings)
...
11/2/2023
...
...
...
Starting at 12:10 in the recording
...
Authority Control: Automated support/Heading validation
...
9/6/23
...
...
...
Starting at 50:25 in the recording
...
...
9/20/23
...
...
...
Starting at 14:58 in the recording
...
Reporting (formerly known as LDP)
...
10/23/2023
...
...
...
Starting at 14:05 in the recording
...
...
7/25/23
...
...
...
Lists App - a forthcoming FOLIO app
...
8/24/23
...
...
WOLFcon presentation
...
...
10/18/23
...
...
These are the slides and screencasts for the release digest
...
FOLIO Acquisitions - Poppy Highlights.pdf
...
10/24/23
...
...
Acquisitions SIG
...
FOLIO ECS - Poppy Highlights.pdf
...
...
Consortia SIG
...
...
7/25/23
...
...
Internal demo
...
Please note the new request form has changed since this demo
...
UXPROD-2689 (Enable Request Policy to Determine Allowed Pickup Service Points)
...
9/19/23
...
Oleksandr Kurash (PO:Anne Ekblad)
...
Internal demo
...
Bulk edit, OAI-PMH and Data export
...
11/16/2023
...
...
...
Starting at 7:00 in the recording.
Post-Release Hotfixes
Critical Service Patch #1-
| Status | ||||
|---|---|---|---|---|
|
Approval Log
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Tickets list
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Modules list
...
Release tag
New Features by Epic (Sub-Project)
Closed Bugs
All Closed Bugs and Stories
...