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 | Khalilah Gambrell |
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. See more here. | UXPROD-4969, UXPROD-5050 | Charlotte Whitt |
MARC authority | New environment variable AUTHORITY_EXTENDED has been introduced in mod-inventory module. If the environment running the module has environment variable AUTHORITY_EXTENDED=true then data import process and quickmarc edit start to use extended version of authority record mapping which can produce additional elements saftBroaderTerm ,saftNarrowerTerm ,saftEarlierHeading ,saftLaterHeading, saftPersonalNameTrunc, saftPersonalNameTitleTrunc, saftGenreTermTrunc, saftGeographicNameTrunc, saftCorporateNameTrunc, saftCorporateNameTitleTrunc, saftMeetingNameTrunc, saftMeetingNameTitleTrunc, saftUniformTitleTrunc, saftTopicalTermTrunc in json for mapped records and kafka messages, module mod-entitied-links starts to convert extended AuthorityDto to db entity and adds "relationshipType" and truncated versions of saft headings to the entry in "authority" and "authority_archive" tables in "saft_headings" column | MODINV-1071 MODELINKS-248 MODELINKS-267 MODDICORE-426 | Justin Travis |
Data export | Users can exclude fields from export by providing a list within data export mapping profile. | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-4146 |
---|
|
| Magda Zacharska |
Data export | Improved data entry validation on the data export mapping profiles | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UIDEXP-383 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UIDEXP-384 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UIDEXP-385 |
---|
|
| Magda Zacharska |
Data export | Additional information: https://folio-org.atlassian.net/wiki/x/Z4CLD | Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MDEXP-683 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MDEXP-680 |
---|
|
| Magda Zacharska |
ECS - Data export | Data export supports now exports of instances and associated holdings/items records with a custom mapping profile from the central tenant. Export of instance records with the default profile from the central tenant. Export of authority records with the default profile from the central tenant.
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MDEXP-722 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MDEXP-721 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MDEXP-721 |
---|
|
| Magda Zacharska |
Automated patron blocks | Before Ramsons, running automated patron block synchronization of any scope (“user” or “full”) would result in losing accumulated patron block data related to lost items. 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: Code Block |
---|
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: Code Block |
---|
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: Code Block |
---|
GET /automated-patron-blocks/synchronization/job/JOB_ID_HERE |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MODPATBLK-179 |
---|
|
| Stephanie Buck |