Skip to end of banner
Go to start of banner

Morning Glory (R2 2022) Release Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 110 Next »

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

New Apps

Bulk edit.  Morning Glory functionality covers:

  • Bulk edit  - in app approach:
    • Inventory items locations (temporary and permanent)
    • Inventory item statuses
  • Bulk edit - csv approach:
    • Users records

The Bulk edit app requires following permissions to edit inventory items:

  • Bulk Edit: In app - Edit
  • Bulk Edit: In app - View

The Bulk edit app requires following permissions to edit user records:

  • Bulk Edit: (CSV) Edit
  • Bulk Edit: (CSV) View

Known limitations:   

  • Bulk edit of user records - up to 2500 records at one time.   
  • Bulk edit of item records - up to 10 000 records at one time

Module configuration:

For stable module operations the following mod-data-export-worker configuration is required: Java args -XX:MetaspaceSize=384m -XX:MaxMetaspaceSize=512m -Xmx2048m, AWS container: memory - 3072, memory (soft limit) - 2600, cpu - 1024.

Removed Apps

Permissions Updates

AppNew PermissionsDeprecated PermissionsProduct Owner
Data Import

Data import: Can upload files, import, and view logs (renamed from Data import: All permissions)

Data import: Can delete import logs

Data import: Can view only

Settings (Data import): Can view only


Ann-Marie Breaux (Deactivated) 
eUsageGeneral: Settings, All, Read-only:
  • Settings (eUsage): Can view and edit all settings
  • eUsage: All permissions
  • eUsage: Can view usage data providers and view/download usage reports
Usage data providers actions:
  • eUsage: Can create and edit usage data providers
  • eUsage: Can delete usage data providers
Reports actions: 
  • eUsage: Can upload usage reports
  • eUsage: Can delete usage reports
  • eUsage: Can start harvesting for a single provider

There has been a major refactoring of all eUsage permissions ( UXPROD-3734 - Getting issue details... STATUS ). Please check existing permission sets and re-assign. 

Annika Schröer 
Invoices

Invoice: Export search results

Invoice: Voucher export

None
Finance

Finance: Export finance records

None
ReceivingReceiving: Export search resultsNone

Orders

Orders: Can create new Orders and Order lines

Orders: Can delete Orders and Order lines

Orders: Can edit Orders and Order lines

Orders: Can view Orders and Order lines

Orders: Cancel order lines

Orders: Cancel purchase orders

Orders: Can create new Order lines

Orders: Can delete Order lines

Orders: Can edit Order lines

Orders: Can view Order lines

Orders: Can create new Orders

Orders: Can delete Orders

Orders: Can edit Orders

Orders: Can view Orders 


Orders: Edit orders should be marked as deprecated but this label will not appear in the UI until Nolana.

Requests, title level requestsSettings (Circulation): Title request level edit
Inventory / quickMARC 

quickMARC: View MARC bibliographic record

quickMARC: View MARC holdings record


Khalilah Gambrell 
InventoryInventory: Create order from instanceNone
MARC authorityMARC Authority: Delete MARC authority record
Khalilah Gambrell 




Known Issues

General

AppKnown issueWorkaroundJIRA issueProduct Owner
Settings > Inventory > Statistical codesHandle delete of statistical code associated with instance, holdings, or item in a properly manner. The approach we took for this issue MODINVSTOR-829 should be similar to what needs to be done for the other related issues, addressed in UXPROD-1889

UXPROD-1889 - Getting issue details... STATUS

RequestsWhen duplicating a request, the original pickup location selection is not preserved.Re-select the pickup location. 

UIREQ-751 - Getting issue details... STATUS


RequestsIn the Request details pane, the publication date may sometimes appear as "-", even though a publication date is listed in it's Inventory record. This happens when there is a character preceding the date, for example, c1905 or [1960]. Check the item or inventory record for the publication date. Correcting this has been added to a feature for future enhancements. 

UIREQ-801

Stephanie Buck 
Data import 

MODDATAIMP-705 - Getting issue details... STATUS


MODDATAIMP-705 - Getting issue details... STATUS

Ann-Marie Breaux (Deactivated) 
MARC authorityFirst deletion of a MARC authority record may be delayed but the record is deleted. No workaround

UIMARCAUTH-159 - Getting issue details... STATUS

Bulk editWhen triggering the bulk edit of item records by submitting a list of holdings HRIDs, the reported number of the updated records might be incorrect.No workaround

UIBULKED-122 - Getting issue details... STATUS

Bulk editOn larger data sets (~ 10 000 records) there is a significant delay on the screen showing the preview of proposed changes (Are you sure? form) Wait until the form is populated and the Download preview button works

MODBULKED-36 - Getting issue details... STATUS

Title Level RequestsRequests with the status Closed - pickup expired are causing queue positions to be absent from the queue. For example, if Request A was position 1, and it's status changes to Closed pickup expired, then Position 1 will be absent from the queue. This does not affect the functionality of the queue.No workaround

CIRC-1589

Title Level RequestsWhen placing a title level request and the Title look-up is used in the request form, the title information isn't loading consistently. Use the Instance ID, or search for the title again. It usually loads properly the second time. 

CIRC-1552

Stephanie Buck 
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)
No known workaroundsCIRC-1683, CIRC-1684, CIRC-1693Stephanie Buck 
Item LimitsWhen a patron reaches the Loan Policy Item Limit at checkout, the error message that appears in the "Item not checked out" pop-up always indicates that the limit is "1", when it could be another number.  Item limits work, but the message is incorrect.Check the Loan Policy to see what the Item Limit is.

UIU-2652 - Getting issue details... STATUS

Holly Mistlebauer 
RequestsMorning Glory includes the implementation of shortcut keys for the request policy, but inadvertently left out adding the UI caret and shortcut key menu to the app. This will be fixed in a future release.Reference docs.folio.org documentation for the shortcut key list as needed - https://docs.folio.org/docs/platform-essentials/keyboard-shortcuts/keyboardshortcuts/

UIREQ-817 - Getting issue details... STATUS


Inventory/Single Record Import

When importing a Single record using the Import button in Inventory's action menu, then an instance is created. But if the user then use the 'back' button in the browser, a duplicate import of the same record is created

Do not use the 'back' button.

UIIN-2197 - Getting issue details... STATUS

Charlotte Whitt 
Circulation log

An item referred in the Circulation log is allowed to be deleted without any warning. But in the Circulation log, when clicking on the referred item (which is a link) then it throws an ugly error. 

New work has been identified: UXPROD-3738, and the architect has written up a technical spec document: UXPROD-3738 Circulation log update: deleted item records

For now accept the ugly error. This will be fixed when the work on UXPROD-3738 can be prioritized by the development team Vega. 

UXPROD-3738 - Getting issue details... STATUS

UsersInvalid date values can cause the user expiration timer to break and freeze the FOLIO tenant.

The Users app can allow saving of records with invalid dates, like a birthdate of 0000-00-01. The User UI context is fixed in the Nolana release; there are larger platform issues that also need to be resolved, being tracked in RMB-943.

If these dates are present, the user expiration timer will not be able to process that user record. The timer will continue to attempt to process the record and eventually the entire FOLIO tenant will freeze.

If you are upgrading an existing FOLIO tenant to Morning Glory, the recommendation is prior to migration to check for these existing date values and resolve them if they are present.

Suggestion from Index Data:

"You can find the user records in the database with a query something like this:

SELECT jsonb FROM diku_mod_users.users
WHERE jsonb->'personal'->>'dateOfBirth' !~ '^[0-9]{4}';

....You can also control the timer that was hanging up the system using the timer management API: https://github.com/folio-org/okapi/blob/master/doc/guide.md#timer-management.

You could reset the interval to be very long and restart your mod-users instances (which releases all the hanging connections and allows Okapi to come back to life), then fix the records and set the timer back to its usual interval."

MODUSERS-320 - Getting issue details... STATUS

UIU-2651 - Getting issue details... STATUS

RMB-943 - Getting issue details... STATUS


AgreementsThe "Is perpetual" property for an agreement cannot be set or editedIf the "Is perpetual" is already set for an agreement, this will remain set, but the value will not be displayed in the Edit form (it will display in the View correctly), and in the Edit (or Create) form for an agreement there are no options in the dropdown for the "Is perpetual" property

ERM-2464 - Getting issue details... STATUS

Owen Stephens 
AgreementsSome of the non-english translations for labels in the UI related to "Supplementary properties" are incorrectThere is no work around for this issue at this time

ERM-2472 - Getting issue details... STATUS

ERM-2478 - Getting issue details... STATUS

ERM-2479 - Getting issue details... STATUS

LicensesSome of the non-english translations for labels in the UI related to "Terms" are incorrectThere is no work around for this issue at this time

ERM-2472 - Getting issue details... STATUS

ERM-2478 - Getting issue details... STATUS

ERM-2479 - Getting issue details... STATUS

Finance, orders, invoices

When modules attempt to update transactions in finance app they may receive an error regarding a null version. Eg. 

{

    "errors": [

        {

            "message": "{\n  \"errors\" : [ {\n    \"message\" : \"Conflict when updating a record in table transaction: Cannot update record e52816e8-c4c9-4648-b65d-XXXXXXXXX because it has been changed (optimistic locking): Stored _version is <NULL>, _version of request is 1\",\n    \"code\" : \"conflict\",\n    \"parameters\" : [ ]\n  } ],\n  \"total_records\" : 1\n}",

            "code": "genericError",

            "parameters": []

        }

    ],

    "total_records": 1

}

Optimistic locking should remain disabled for the Morning Glory release.

Instructions regarding exactly what to disable can be found here under "Before Running" https://wiki.folio.org/x/tRm-BQ. This was discovered while preparing a script to fix issued cause by past rollovers.

MODFISTO-340 - Getting issue details... STATUS

Dennis Bridges 
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.

MSEARCH-458 - Getting issue details... STATUS

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.

RMB-955 - Getting issue details... STATUS

Julian Ladisch 

Additional known issues

key summary type updated Potential Workaround Development Team status resolution Release
Loading...
Refresh

Notes on functionality

PO Release Presentations

PresentationPresentation datePresenterSIG Meeting (link)Notes
Inventory2022.07.28Charlotte WhittMM-SIGView demo and slide deck
Cataloging2022.08.11Khalilah Gambrell
View slide 8
Acquisitions2022.08.19

Dennis Bridges


Includes gifs.
Data Import2022.08.04Ann-Marie BreauxMM-SIGDemo at SIG meeting, plus slide deck
ERM: Agreements and Licenses2022.08.10

ERM-SIG:

Notes

Recording

View slide 2, and recording from 08:50-24:50
Bulk edit2022.08.31Magda Zacharska WOLFcon presentation

Post-Release Hotfixes

Hot fix release #1 - RELEASED AT DECEMBER 20

Tickets list

key summary type assignee priority resolution reporter
Loading...
Refresh

Modules list


The Jira server didn't understand your search query. If you entered JQL, please ensure that it's correctly formed. If you entered an issue key, ensure that it exists and you have permission to view it.


New Features

key summary Development Team
Loading...
Refresh


Nonfunctional Requirements (NFR) Features

key summary Development Team
Loading...
Refresh

Closed Bugs


All Closed Bugs and Stories


Remaining Open Bugs at Time of Release

Support Period

Morning Glory will be supported with critical security and bug fixes until Orchid (R1 2023) is released (around April 2023). At the Morning Glory release day the Kiwi release has reached end of life and is no longer supported. See FOLIO support policy.

  • No labels