Customisation of merge process
Posted: 03 Dec 2008 09:41
It would be nice if there could be some more user control over the merging process.
I'm thinking along the lines of being able to change the weights that FH assigns to it's matches, or changing the criteria (e.g. date range for an event to match). Also some changes to to the existing matches such as more emphasis on including middle names/initials (currently a John E Smith will match a John Brown Smith) or excluding all records with no surname to make a better match and also taking into account the presence of a parental families (currently if the parental families don't match the records are still made a suggestion for a match - I would argue that this is a very unlikely case and can be handled seperately).
Also some enhacements to the merge dialog to make it more user friendly such as allowing the selection of more than one record to unmatch, unmatching all below a set score, single key modifiers for actions* (e.g. just + or - rather than Alt-D/Alt-U which require awkward finger positions from one hand when the other is using the mouse), ability to add columns to the lists so that, for instance, B&D dates can be seen at a glance rather than having to open up each record.
A nice extra touch to the merging process would be that of assiging a key person to start the merge from. Sometimes you might get a gedcom with only one or a few people who match, such as an IGI extract or a new branch from an existing record. In these case rather than FH blindly going through all records to find matches, giving FH a hint should make the matching more efficent as it can check just that branch in question. A similar existing wish list item exists for this but it's described differently.
* This is already a wish list item.
http://www.fhug.org.uk/wishlist/wldispl ... lwlref=393
ID:3143
I'm thinking along the lines of being able to change the weights that FH assigns to it's matches, or changing the criteria (e.g. date range for an event to match). Also some changes to to the existing matches such as more emphasis on including middle names/initials (currently a John E Smith will match a John Brown Smith) or excluding all records with no surname to make a better match and also taking into account the presence of a parental families (currently if the parental families don't match the records are still made a suggestion for a match - I would argue that this is a very unlikely case and can be handled seperately).
Also some enhacements to the merge dialog to make it more user friendly such as allowing the selection of more than one record to unmatch, unmatching all below a set score, single key modifiers for actions* (e.g. just + or - rather than Alt-D/Alt-U which require awkward finger positions from one hand when the other is using the mouse), ability to add columns to the lists so that, for instance, B&D dates can be seen at a glance rather than having to open up each record.
A nice extra touch to the merging process would be that of assiging a key person to start the merge from. Sometimes you might get a gedcom with only one or a few people who match, such as an IGI extract or a new branch from an existing record. In these case rather than FH blindly going through all records to find matches, giving FH a hint should make the matching more efficent as it can check just that branch in question. A similar existing wish list item exists for this but it's described differently.
* This is already a wish list item.
http://www.fhug.org.uk/wishlist/wldispl ... lwlref=393
ID:3143