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. | ||
Data export | Improved data entry validation on the data export mapping profiles | - UIDEXP-383Getting issue details... STATUS - UIDEXP-384Getting issue details... STATUS - UIDEXP-385Getting issue details... STATUS | |
Data export |
Additional information: https://folio-org.atlassian.net/wiki/x/Z4CLD | - MDEXP-683Getting issue details... STATUS - MDEXP-680Getting issue details... STATUS | |
ECS - Data export |
| - MDEXP-722Getting issue details... STATUS - MDEXP-721Getting issue details... STATUS - MDEXP-721Getting 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 |
Manage space
Manage content
Integrations