Ramsons (R2 2024) Notes on functionality
- Pavlo Smahin
- Ryan Taylor
- Christine Schultz-Richert
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. | @Charlotte Whitt | |
MARC authority | New environment variable | @Justin Travis | |
Data export | Users can exclude fields from export by providing a list within data export mapping profile. | UXPROD-4146: Data export - Removing MARC fields before exportClosed | @Magda Zacharska |
Data export | Improved data entry validation on the data export mapping profiles | UIDEXP-383: Mapping profile view - empty indicators and subfields displayClosed UIDEXP-384: Mapping profile - modify validation of transformation elementsClosed UIDEXP-385: Transformation form: empty indicators and subfields displayClosed | @Magda Zacharska |
Data export |
Additional information: https://folio-org.atlassian.net/wiki/x/Z4CLD | MDEXP-683: Export deleted instances Closed MDEXP-680: Ability to export deleted MARC authority recordsClosed | @Magda Zacharska |
ECS - Data export |
| MDEXP-722: Export Instances with Custom Export Profile from Member TenantClosed MDEXP-721: Export Authority Records with Default Export Profile from Central TenantClosed MDEXP-721: Export Authority Records with Default Export Profile from Central TenantClosed | @Magda Zacharska |
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: /automated-patron-blocks/synchronization/job API omits aged to lost itemsClosed | @Stephanie Buck |
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. | @Dennis Bridges | |
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: Implement consumer for Inventory record reference changesIn Review | @Dennis Bridges |
Inventory - Instance mapping updates |
| @Ryan Taylor | |
ECS - Inventory | Users with necessary permissions can update ownership of Inventory Holdings & Items from one affiliation to another.
| @Ryan Taylor | |
Data Import | Users can Export & Import Data Import Job Profiles via API
| @Ryan Taylor | |
Inventory - Classification browse | New options for browsing by instance-level Classification numbers. There are steps to configure these browse options in a new section in Settings app for “Classification browse”. This configuration determines which Classification identifier types are browsable in which option. Users must have permission Settings (Inventory): Configure classification browse | @Christine Schultz-Richert | |
Inventory - Date filter & sort | Records can now be sorted and filtered by date, enabled by three different pieces of functionality:
| @Christine Schultz-Richert |