Regarding (1) the "doubling" of the headings, you merged 602196 into 603799, as far as I can tell. Headings stand entirely on their own, so the resulting record is expected. The fact that you see the same heading used twice is a side-effect of how the test was set up.
Regarding (2), because import of duplicate authority records from other systems, say, during migration, is so common we were forced to relax that no-duplicates restriction. This may very will be the case in your installation. Once duplicates have been purged from your system a UNIQUE index can be created to make sure that doesn't happen in the future. However, even the 040 difference may be at fault if the record uses a locally defined thesaurus.
Regarding (b), as far as MARC is concerned $0 can live anywhere in the field. I would suggest creating a separate wishlist bug for this.
George,
Regarding (1) the "doubling" of the headings, you merged 602196 into 603799, as far as I can tell. Headings stand entirely on their own, so the resulting record is expected. The fact that you see the same heading used twice is a side-effect of how the test was set up.
Regarding (2), because import of duplicate authority records from other systems, say, during migration, is so common we were forced to relax that no-duplicates restriction. This may very will be the case in your installation. Once duplicates have been purged from your system a UNIQUE index can be created to make sure that doesn't happen in the future. However, even the 040 difference may be at fault if the record uses a locally defined thesaurus.
Regarding (b), as far as MARC is concerned $0 can live anywhere in the field. I would suggest creating a separate wishlist bug for this.