I thought I'd explain in more detail how I as a curator can help with a family line in a Project; answer your questions about how come you have some access but not all; why there are triblets and clones and clowns oh my!; help with Master Profiles; and get naming conventions and source data on the page.
1. I wasn't sure when the name change was from Coffyn to Coffin and how you all wanted to do that (as you say, different sources can say different things). It sounds like you want to stick with Coffyn for England and the first immigrant to the US, Tristam Coffyn senior, and then do the switch over to Coffin?
2. As I understand it, the database does most accurate "searches" and matches on:
First name, last name, then maiden names, then dates, then suffix, then display names. Middle name doesn't always show in the "conflict resolution tool" I don't think.
Therefore (and for consistency) I use these kinds of naming conventions:
- Names, never titles, never nicknames, in the name fields. That means "Sir" is never a first name. (Can you imagine what kind of result you'll get with a search on first name "Sir"?)
- Nicknames in "quotes" in the Middle Name field.
- To distinguish between generations of David (for example), use Roman Numerals in the Suffix Field.
- To distinguish between David in the same in the same generation from different branches of the family, use a location in the Suffix field. In general I've started doing that for large and confusing families -- real historians do it apparently and it works great.
So, for example: David Coffin, lll, of Devon
This is also good for titles: instead of putting them in the name field, use the suffix field. For example, Margaret Cornfield, Countess of Westwood (making it up).
Display names are wonderful but get lost in merges.
Next messages to explain about why so many merges. :)