Topic: Name Matches - big frustration
The new recorder name matching in version 220.127.116.111 of Recorder 6 is extremly frustrating. After edits to the source data finanly managed to import some records from iRecord.
1) Recorder 6 can now say there are multiple possible entries for a name. However, there is only one extact match, and various other fuzzy matches. If there is an exact match, then Recorder 6 should use that. I am not interested that there are other vague matches. I don't know and I don't care that "J Smith" may be or maybe not "John Smith" when I already have a "John Smith" entry. Unless I know the person, and they have a rare name, I just don't whether they are the same person or two different people.
My rule, is that if there is not an exact match, create a new person. I tried in the past to clean up the database to remove duplicates, and it was too much hard work for too little reward.
2) People with double barrel surnames are a pain to enter into Recorder 6, as there seems to be no format that Recorder 6 understands. the real issue is that Recorder 6 can treat comma to mean either surname, forename or recorder 1 and record 2. The standard should be comma means "surname, forename". I usually find out there is a problem, when Recorder 6 wants to create a person with just their forename.
Surrey County Butterfly Recorder