Page Comparison

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

• Settings (eUsage): Can view and edit all settings
• eUsage: All permissions
• eUsage: Can view usage data providers and view/download usage reports

• eUsage: Can create and edit usage data providers
• eUsage: Can delete usage data providers

• eUsage: Can upload usage reports
• eUsage: Can delete usage reports
• eUsage: Can start harvesting for a single provider

Invoice: Export search results

Invoice: Voucher export

Finance: Export finance records

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.

quickMARC: View MARC bibliographic record

quickMARC: View MARC holdings record

UIREQ-801

CIRC-1589

CIRC-1552

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)

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

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

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."

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://folio-org.atlassian.net/wiki/x/1k0V. This was discovered while preparing a script to fix issued cause by past rollovers.