App | Notes | Jira | Product Owner |
|---|---|---|---|
Notes | Possible to failure while creating multiple notes via API when creating multiple note_link objects for the same target object (was not able to reproduce it via manual testing or using Jmeter highload perfomance tests) | N/A | |
Floating collections | Floating collection is defined as a group of items that are not housed permanently at a specific library, but are shelved at the library where they were most recently checked in. Floating collections are used to decrease transportation of items between libraries and to reduce manual handling, transit time, shipping expenses and/or traffic emissions. The Back End work supporting floating collection is implemented. | ||
MARC authority | New environment variable | ||
Data export | Users can exclude fields from export by providing a list within data export mapping profile. | UXPROD-4146 - Getting issue details... STATUS | |
Data export | Improved data entry validation on the data export mapping profiles | UIDEXP-383 - Getting issue details... STATUS UIDEXP-384 - Getting issue details... STATUS UIDEXP-385 - Getting issue details... STATUS | |
Data export |
Additional information: https://folio-org.atlassian.net/wiki/x/Z4CLD | MDEXP-683 - Getting issue details... STATUS MDEXP-680 - Getting issue details... STATUS | |
ECS - Data export |
| MDEXP-722 - Getting issue details... STATUS MDEXP-721 - Getting issue details... STATUS MDEXP-721 - Getting issue details... STATUS | |
Automated patron blocks | Before Ramsons release, running automated patron block synchronization of any scope (“user” or “full”) would result in losing accumulated patron block data related to lost items for affected patrons. This may have affected libraries that use automated patron blocks with condition “Maximum number of lost items”. In order to rebuild lost data and recalculate patron blocks in these libraries it is recommended to run full patron block synchronization: POST /automated-patron-blocks/synchronization/job
{
"scope": "full"
}
In case if potential data loss is limited to specific patron(s), a user-level sync can be executed instead: POST /automated-patron-blocks/synchronization/job
{
"scope": "user",
"userId": "USER_ID_HERE"
}
Both calls will return an ID of the sync-job which can then be used to monitor job’s progress: GET /automated-patron-blocks/synchronization/job/JOB_ID_HERE | MODPATBLK-179 - Getting issue details... STATUS | |
ECS - Central ordering | This functionality must be enabled and it is only available in the central tenant of a FOLIO system with ECS enabled. As noted in the UI once this feature is enabled it can NOT be disabled in the Ramsons release version. System that do not plan to create orders centrally that they want to generate records inventory for use in related data tenants. Should not activate this funcitonality. | UXPROD-4553 - Getting issue details... STATUS | |
Order<>inventory link management ECS and non-ECS | When the relationships between inventory records are changed any linked orders will be updated to reference the new Instance holdings and item(s). Moving an item in inventory will now produce a warning modal if the movement will impact related order records. In some cases this will limit a users ability to change the relationship of item records directly from inventory. This will prevent the corruption of order and receiving data resulting from the change of relationship between items, holdings and instances. In the ECS context it will allow items associated with central orders to be moved from a location in one tenant to a location in another tenant as long as the item and holdings are related to a “Shared instance”. In this version it will not be possible to “change ownership” of items (move the item from one tenant to another) that are linked to a local order in a member tenant. However, these items could still be move between holdings and items within the local tenant. | UXPROD-4976 - Getting issue details... STATUS |
Manage space
Manage content
Integrations