Ramsons Flower Release
Full Details
Deduplication of the MARC field 856:
MODDICORE-408: Data Import removes duplicate 856s in SRSClosed
Solution:
If EXISTING record and INCOMING record have exact field values, it should dedupe.
If INCOMING record has multiple exact field value matches, the fields from the INCOMING record should NOT dedupe.
For example, if the Incoming record contains duplicate 856 field values, then these fields should not be deduplicated
Protected fields are not in order after update.
MODDICORE-358: Data import sorts protected fields out of order after updateClosed
Protected field of EXISTING record should be placed either ahead or behind the same field number from the new INCOMING record.
Mapping Rules/Run Script to Update Rules: Default MARC-Instance mapping rules were updated to add:
010$z Canceled LCCN
008 Date type
6xx for Subject source and Subject type fields
After upgrade follow the instructions to update the mapping rules.
UXPROD-4444: MARC-Instance default mapping changes: Canceled LCCN -- 010 $z (Ramsons)Closed
Refine and standardize handling of MARC field 035:
Normalize OCLC 035 values. https://folio-org.atlassian.net/browse/MODINV-949
Subject Heading Granularity updates:
Export & Import Data Import Job Profiles: Phase I Via the API:
Documentation: https://folio-org.atlassian.net/wiki/x/NYCnIQ
Marked checkboxes are reset after the user is returned to DI landing page from the log.
Modify action before match when there is no match doesn’t display as “No Action” in logs.
EDIFACT invoice lines load out of order.
Electronic Access relationship ID incorrect mapping. https://folio-org.atlassian.net/browse/MODDICORE-406
Data Import sorts protected fields out of order after update.
Disallow create/update of a job profile without actions.
Marc records updated with single record overlay thereafter uneditable → same issue as ticket SRS marc updates results in 2 srs records with state = ACTUAL. https://folio-org.atlassian.net/browse/MODCPCT-85 →
MARC Validation: Improvements with Record specifications were implemented to be used for MARC validation. MARC Validation Rules: With Sunflower, the field 035 9\ or 035 \9 will be considered invalid because of the 9 in either the first or second indicator. For those that rely on this MARC field and indicator of 9, it is recommended to configure the MARC validation rules to avoid seeing an error when editing records with that MARC field in quickMARC.
Cleanup of legacy field Donor Information: Updated migration script to remove redundant entry for the "donor information" field that may have been added due to repeated migration script execution during the upgrade from Quesnelia (Quesnelia CSP#4 or higher) to Ramson, which causes profile to be corrupted during editing.
Resolve instances not connected to a marc srs record: https://folio-org.atlassian.net/browse/MODINV-1178
Data Export (Related)
Users can exclude fields from export by listing them in a custom data export mapping profile. https://folio-org.atlassian.net/browse/UXPROD-4146
Improved data entry validation.
UIDEXP-383: Mapping profile view - empty indicators and subfields displayClosed https://folio-org.atlassian.net/browse/UIDEXP-384 https://folio-org.atlassian.net/browse/UIDEXP-385
Export instances set for deletion.
Documentation: Export Deleted records via API. https://folio-org.atlassian.net/wiki/x/Z4CLD
Export deleted authority records.
ECS - Data Export
Supports new exports of instances and associated holdings/items. https://folio-org.atlassian.net/browse/MDEXP-722
Export instances with default from central tenant.
Export authority records with default from central tenant.
Documentation: https://folio-org.atlassian.net/wiki/x/F4D_H