Ramsons (R2 2024) Notes on functionality
- Pavlo Smahin
- Thomas Trutt
- Stephanie Buck
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. | UXPROD-4969: SPIKE - Floating collection. If item is returned at non-owning library location, library can configure (at the collection or service point level) how the return is handledClosed , UXPROD-5050: Floating collection. Back end work.Closed | @Charlotte Whitt |
MARC authority | New environment variable | MODINV-1071: Extend Authority with Additional fieldsIn QA MODELINKS-248: Extend Authority with Additional fieldsClosed MODELINKS-267: Extend Authority with saft* fields having custom mappingOpen MODDICORE-426: Extend Authority with saft* fields having custom mappingAwaiting deployment | @Justin Travis |
Data export | Users can exclude fields from export by listing them in a custom 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 |
Additional information: https://folio-org.atlassian.net/wiki/x/F4D_H | MDEXP-722: Export Instances with Custom Export Profile from Member TenantClosed https://folio-org.atlassian.net/browse/MDEXP-721 https://folio-org.atlassian.net/browse/MDEXP-721 | @Magda Zacharska |
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. | @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 | |
eUsage |
| https://folio-org.atlassian.net/browse/UXPROD-4953 https://folio-org.atlassian.net/browse/UIEUS-365 https://folio-org.atlassian.net/browse/UXPROD-4971 https://folio-org.atlassian.net/browse/UXPROD-4963 | @Stefan Dombek |
Bulk edit | Bulk edit supports now editing instance notes for instances with source MARC and FOLIO. Users are now able to add a new note, update or remove existing note. Before changes are committed they can be previewed in .csv and .mrc files. Additional information: https://folio-org.atlassian.net/wiki/x/s4CvIQ | @Magda Zacharska | |
ECS - Bulk edit | User with appropriate affiliation and permissions are able to update holdings and items records from the central tenant. Additional information: https://folio-org.atlassian.net/wiki/x/AoAEFQ | @Magda Zacharska | |
Enable MARC bib and MARC authority LCCN (010 $a) duplicate record check | For the Ramsons release, a tenant can enable MARC bib and MARC authority LCCN (010 $a) duplicate record checking so that a MARC bib/MARC authority record cannot be saved with an existing 010 $a value. If enabled and a duplicate LCCN (010 $a) is found, then the user will receive a Fail error and cannot save the MARC bib/authority record. This functionality only applies to creating/editing a MARC bib/authority record via quickMARC.
Configuration details
 POST response body
| @Khalilah Gambrell | |
Enable MARC bib and MARC authority LCCN (010 $a) structure validation check | For the Ramsons release, a tenant can enable a setting to check that the MARC bib/authority LCCN (010 $a) entered complies with Library of Congress (LOC)'s rules. If the setting is enabled then the LCCN 010 $a entered on a MARC bib/MARC authority record will be checked against LOC’s rules and if the value is invalid then the user will receive a Fail error and cannot save the MARC bib/authority record. This functionality only applies to creating/editing a MARC bib/authority record via quickMARC.
Configuration details Required permissions:
Steps to enable MARC bib LCCN (010 $a) structure validation
Step to enable MARC authority LCCN (010 $a) structure validation
| @Khalilah Gambrell | |
ui-invoice | Users are now able to duplicate invoices and invoice lines. When duplicating the resulting duplicate will be created in the status “Open”. |
| @Dennis Bridges |
ui-orders ui-receiving | Add support for routing lists and alternate materials handling upon receiving. | @Joseph Reimers | |
ui-receiving | Add support for binding materials | @Joseph Reimers | |
mod-organizations | Prevent deletion of banking account types when in use |
| @Joseph Reimers |
Check Out | If Profile Pictures are enabled they will be displayed at Check out for users with the “Users: Can view profile pictures” permission | @Amelia Sutton | |
Users | An error message will now be displayed when a user tries to add a non-image or invalid URL as an externally linked profile picture | @Amelia Sutton | |
Users | New functionality to Export User Data for Library Card Printing. The user profile “Actions” now includes an option to “Print library card”. This option is only available when the user meets all of the following:
The User’s Barcode, First name (preferred name instead if present), Middle name, Last name, Patron group, Expiration date will be included in a .csv file. The user’s profile picture will download as a separate .jpg or will be included in the .csv if the profile picture is linked from an external URL | @Amelia Sutton | |
Settings > Circulation | Two new staff slip tokens were added to the staff slip template editor:
| @Amelia Sutton | |
Settings > Circulation | New Staff Slip type, “Due date receipt”, has been added. The template can be configured under Settings > Circulation > Staff slips > Due date receipt. The slip will populate the following tokens (new tokens in Bold): borrower.firstName borrower.lastName borrower.middleName borrower.preferredFirstName borrower.patronGroup loan.dueDate Item.title Item.barcode item.primaryContributor item.callNumber item.enumeration item.chronology item.copy
| @Amelia Sutton | |
Users > Open Loans | Due date receipts can be printed from the open loans screen either by selecting one or more open loans then selecting Print due date receipt, or via the actions menu for an individual invoice. Due date receipts can also be printed from the Loan details page for an individual loan by selecting Print due date receipt | @Amelia Sutton | |
Settings > Circulation | New section under the Requests header, “View print details”. This section includes a single option to enable the viewing of print details in the requests app. When enabled, the system will record when a staff slip is printed for a request, and that information will be displayed in the Requests app. When disabled, existing data will remain in the database, but future print actions will not be logged. | @Amelia Sutton | |
Requests | Functionality to deter duplicate pick slip printing can be enabled by enabling “View print details (Pick slips)” under Settings > Circulation > View print details. When enabled, users see two new columns that can be selected to display in Requests search:
The system will log the request ID, username, date, and time of printing. Logs can be accessed via the API. | @Amelia Sutton | |
Users | A new field “Email communication preferences” has been added. This field is a multiselect with three options:
| @Amelia Sutton | |
mod-users | The encryption key field in the profile picture configuration is no longer updateable. | @Amelia Sutton | |
Users | New Reading Room Access accordion on User records. Users with the appropriate permissions (See the permissions update notes for more details) can see a user’s access for each reading room. On the user edit screen staff can update the user’s access to reading rooms and add a note to each room on a user’s record. | @Amelia Sutton | |
Settings > Tenant | New section under General, “Reading room access”, where reading rooms can be configured by users with the appropriate permissions (See the permissions update notes for more details). Each reading room has 3 fields, the room name, a Boolean setting a room as private or not, and a multiselect for associated service points. Reading rooms with Public set to False will not allow access by default. Reading rooms with Public set to True will default to allowing access. Each reading room can have any number of service points assigned, but each service point can only be assigned to a single reading room. | @Amelia Sutton | |
Requests → Search slips | Note on functionality with Title level requests (TLR). The search slips report looks at the holdings record effective location for TLR’s holds. The report does not take into consideration any attached items.
The search report would print a slip at Circ 1. |
|