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: UXPROD-4081: Refine and standardize handling of 035 OCLC numbers in MARC records (including potential duplicates)Closed

  • OCLC 035 normalization explanation

• Normalize OCLC 035 values. https://folio-org.atlassian.net/browse/MODINV-949

• Subject Heading Granularity updates: https://folio-org.atlassian.net/browse/UXPROD-4445

• Export & Import Data Import Job Profiles: Phase I Via the API: UXPROD-4348: Data Import: Ability to export Data import profile details via APIClosed , UXPROD-3556: Data Import: Ability to import Data Import profile details via APIClosed

  • 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. UIDATIMP-1657: The marked checkboxes are reset after the user is returned to the Data Import Landing page from the LogClosed

• Modify action before match when there is no match doesn’t display as “No Action” in logs. MODSOURMAN-1145: Modify action before match breaks non match logsClosed

• EDIFACT invoice lines load out of order. MODINVOICE-543: EDIFACT invoice lines load out of orderClosed

• Electronic Access relationship ID incorrect mapping. MODDICORE-406: Relationship ID incorrect mappingClosed

• Data Import sorts protected fields out of order after update. MODDICORE-358: Data import sorts protected fields out of order after updateClosed

• Disallow create/update of a job profile without actions. MODDICONV-373: Disallow create/update of a job profile without actionsClosed

• 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 → https://folio-org.atlassian.net/browse/MODDATAIMP-1058

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. https://folio-org.atlassian.net/browse/UIDEXP-383 https://folio-org.atlassian.net/browse/UIDEXP-384 https://folio-org.atlassian.net/browse/UIDEXP-385

• Export instances set for deletion. https://folio-org.atlassian.net/browse/MDEXP-683

  • Documentation: Export Deleted records via API. https://folio-org.atlassian.net/wiki/x/Z4CLD

• Export deleted authority records. https://folio-org.atlassian.net/browse/MDEXP-680

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. https://folio-org.atlassian.net/browse/MDEXP-721

• Export authority records with default from central tenant. https://folio-org.atlassian.net/browse/MDEXP-721

• Documentation: https://folio-org.atlassian.net/wiki/x/F4D_H