For linked fields (e.g publisher, programmer, cracker etc.) when merging, 
the following rules can be specified by the user: -


Same ID, Different Name [ e.g. Master: <34> Thalion  Import: <34> Thalion Software ]
------------------------------------------------------------------------------------
- add to master as new record
- update existing master record
- let me pick a master record manually
- ask me what to do


Different ID, Same Name  [ e.g. Master: <34> Thalion  Import: <176> Thalion ]
-----------------------------------------------------------------------------
- keep ID of master record (do nothing)
- add to master as new record
- ask me what to do


Different ID, Different Name [ e.g. Master: <34> Thalion  Import: <176> Thalion Software ]
                             [ or   Master: <21> Ocean    Import: <224> System 3         ]
------------------------------------------------------------------------------------------
- use first found record in master with matching name, if not found ask me what to do (add-as-new/pick-manually)
- use first found record in master with matching name, add as new record if not found
- use record in master with matching name, ask me if more than 1 match found, add as new record if not found
- use record in master with matching name, ask me if more than 1 match found, if not found ask me what to do (add-as-new/pick-manually)



These rules come into effect when the merge button is clicked. 

Batch merges are only possible if both Active and Passive fields are pre-resolved to either master or import (i.e. that field defaults to not having a conflict)

Using the above rules, it should be possible to run a batch merge without user intervention if the user chose the appropriate rules.