Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel4

...

AppKnown issueWorkaroundJIRA issueProduct Owner
UsersMail notices do not get sent to proxy, even when that value is selected, but get sent to sponsorCurrently no work around; this is new work to do the back-end of what is visible in the UI.julie.bickle 
mod-inventory-storageAuthorities update through quick-marc are applied to mod-search records with a delay of 1 updateRemove DB_HOST_READER , DB_PORT_READER environment variables from mod-inventory-storage. Next authority update will be successful.MODINVSTOR-1006Khalilah Gambrell 
Export Manager

Files generated by following jobs are available only for several hours due to AWS Identity and Access Management (IAM) instance profile settings:

  • Bursar
  • Circulation logs
  • Bulk edit
Repeat exports again

MODEXPW-326

Magda Zacharska 
Bulk editIntermittent error "Something went wrong" after rearranging columns while editing holdings record.  The error occurs on the Are you sure form before any changes are committed.Restart bulk edit.

UIBULKED-170

mod-searchboundWith flag is not updated in mod-searchFor mod-search either remove KAFKA_EVENTS_CONSUMER_PATTERN  env variable so that the default ($ENV\.)(.*\.)inventory\.(instance|holdings-record|item|bound-with) is used, or add bound-with to your custom pattern.

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMSEARCH-458

Title level requests
  1. Users are able to recall items with statuses they should not be able to (Aged to lost, Claimed returned, Declared lost)
  2. Users unable to recall items with status In process, In transit, On order when TLR is enabled
  3. Item level policies are not being upheld by title level requests (Even though an item is not requestable via item level request by the patron, it could be used to fill the title level request upon check in)
  4. 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
No known workarounds. CIRC-1683, CIRC-1684, CIRC-1693

UXPROD-4245

Stephanie Buck 
Purging a tenantAfter disabling modules with purge option for one tenant other tenants get this error:
"ERROR: function f_unaccent(text) does not exist (42883)"
This affectes only modules where environment variable DB_MAXSHAREDPOOLSIZE is set.
After disabling modules with purge option restart all modules where environment variable DB_MAXSHAREDPOOLSIZE is set.

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRMB-955

Julian Ladisch 
All

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRMB-348
was implemented to split reading and writing traffics into separate database nodes. While it's working for some workflows (check in/out, MARC BIB/Authority Data import Creates and Updates), it is buggy in other workflows. These are: Acquisition, Data Export, Data Import of MARC Holdings. 

Additionally in very rare circumstances when a failover happens between the database nodes, such as when the write node fails over to the read node (the read node now becomes the new write node and vice versa), the storage modules may still cache the old addresses so they may continue to write to what is now the new read node or that the old write node has gone out of service). 

Remove DB_HOST_READER , DB_PORT_READER environment variables from mod-inventory-storage, mod-data-export, mod-source-record-manager, mod-orders-storage.



A workaround for the failover issue is to create an AWS lambda (or some process that listens for failover events) that restarts the RMB storage modules to create new connections to the new database nodes

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMDEXP-576

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODINVSTOR-1019

Martin Tran 
NCIPWhen the acceptItem service is called, if the pickupLocation contains '/' the service will fail:
org.z3950.zing.cql.CQLParseException: expected boolean, got '/'
Use the patched version of the module:
https://github.com/folio-org/mod-ncip/releases/tag/v1.12.3

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODNCIP-54

ERMWhen you view a License in the License App that has a linked Agreement, on viewing the "Agreements linked to this license" the Agreement information does not display (only the 'License link status' displays)Currently no work around; the issue is fixed in mod-agreements 5.5.x

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyERM-2638

Owen Stephens 

...

PresentationPresentation datePresenterSIG meeting (link)Notes
AcquisitionsNovember 1, 2022Dennis BridgesAgenda and Meeting Notes#:~:text=Demo%20Nolana%20Release%20highlights
ERM: AgreementsNovember 2, 2022Owen Stephens 

ERM-SIG:

Notes

Recording

View slide 2-4, and recording from 10:14-37:10 (includes Dashboard 13:45-17:45)
DashboardNovember 2, 2022Owen Stephens 

ERM-SIG:

Notes

Recording

View slide 2, and recording from 13:45-17:45
Bulk editNovember 10, 2022Magda Zacharska 

MM SIG Meeting Recording

Bulk edit related recording starts at 26:20

...

Support Period

Assuming the FOLIO support policy remains unchanged, Nolana will be supported with critical security and bug fixes until Poppy (R2 2023) release (around April November 2023). With the Nolana release Lotus has reached end of life and is no longer supported.

...