Page Comparison

...

• First iteration created in MODDICONV-137
• Bugfixes required and will be delivered in Morning Glory, so this page has been created to document expected behavior for 1) Protecting MARC field and then 2) Overriding MARC field protections
• Related bugs
  • https://issuesfolio-org.folioatlassian.orgnet/browse/MODDATAIMP-643
  • https://issuesfolio-org.folioatlassian.orgnet/browse/MODDICORE-248
  • https://issuesfolio-org.folioatlassian.orgnet/browse/MODDICORE-146

See MODDICORE-146 SPIKE: Instance & SRS record updates need to honor MARC field protections for additional technical information

...

• As with applying MARC field protections, overriding those protections are somewhat limited in releases prior to Morning Glory, in that they cannot be used without an Update MARC action in the job profile, and do not distinguish the handling for repeatable and non-repeatable fields properly.
• As of the Morning Glory release, all of the details in the above MARC field protections scope section also apply to overriding MARC field protections.
• Field protection override behavior:
  • Field is non-repeatable, and the field protection for the existing field is overridden in the job profile
    • Existing field's will be replaced by the incoming field's data in the updated record, regardless of whether that data is the same or different from the existing data
  • Field is repeatable, and the field protection for the existing field is overridden in the job profile
    • Existing field also is in the incoming record:
      • The field will be retained in the updated record (actually replaced by the incoming version of the field, which is an exact duplicate to the existing field)
    • Existing field is not in the incoming record:
      • The field will not be retained in the updated record (since its protection was overridden)