...
Deduplication of the MARC field 856:
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDICORE-408 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.
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODDICORE-358 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.
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4444
Refine and standardize handling of MARC field 035:
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4081 Subject Heading Granularity updates:
Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4445 Export & Import Data Import Job Profiles: Phase I Via the API:
,Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4348 Jira Legacy server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-3556