fix doc aut duplicate depends on field order

Description

fix_doc_aut_duplicate creates an empty subfield $7 instead of subfield $7 including the record's 1XX contents, if the record's 1XX field is located after the 4XX-field being handled - e.g. when the record which should be fixed is result of a merge, where 1XX field is copied from incoming record.

For example: Running fix_doc_aut_duplicate for the following "record":

000000046 4102 L $$aAhto
000000046 1102 L $$aAhtausteknillinen opisto

results in empty subfield $7:

000000046 4102 L $$aAhto$$7
000000046 1102 L $$aAhtausteknillinen opisto

instead of correct version:

000000046 4102 L $$aAhto$$7Ahtausteknillinen opisto
000000046 1102 L $$aAhtausteknillinen opisto

Resolution

This empty subfield $7s were fortunately easily avoided by preceding fix_doc_aut_duplicate with fix_doc_sort in tab_fix
Product: Aleph
Product Version: Version 22, 23
Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

Insert parts here, from the Template list.