|
Private User
5/29/2010 at 2:34 AM
|
|
|
5/29/2010 at 3:35 AM
|
||
|
Private User
5/29/2010 at 4:10 AM
|
|
|
Private User
5/29/2010 at 6:01 AM
|
|
|
Private User
5/29/2010 at 6:17 AM
|
|
|
|
Private User
5/29/2010 at 9:57 AM
|
|
|
Private User
5/30/2010 at 2:51 AM
|
|
|
Private User
5/30/2010 at 3:30 PM
|
|
|
|
Private User
5/30/2010 at 3:33 PM
|
|
|
Private User
5/30/2010 at 3:55 PM
|
|
|
Private User
5/31/2010 at 3:31 PM
|
|
|
Private User
5/31/2010 at 3:58 PM
|
|
|
6/1/2010 at 12:11 PM
|
||
|
Private User
6/1/2010 at 2:51 PM
|
|
|
|
Private User
6/1/2010 at 2:58 PM
|
maybe the "last manager" is not the one that has the best info
oherwise leave it to the main manager, who will get the conflict in his/hers merge issues list OR send back to requester |
|
|
Private User
6/1/2010 at 3:01 PM
|
|
|
Private User
6/1/2010 at 3:04 PM
|
|
|
6/1/2010 at 3:13 PM
|
||
|
|
Private User
6/1/2010 at 3:21 PM
|
Harald - what I am trying to say is that perhaps the manager should do the "resolving data conflicts". Or the one with the best knowledge. I leave rather than guess. If I am the manager -- I check. Günther - Yes I have.
|
|
6/1/2010 at 11:57 PM
|
I think that one should be extremely careful using automerge. I just had a request to merge a profile, where the dates of birth and death show an age of only two years, and she was married and had children, another request the same day the age was 4 years and she was also married. Even though the profile is your own you have to check it before you request merges, someone can have edited it in between. Especially when siblings baptized the same names, and deceased early (within a few years) have elder namesakes that survive, you have to be careful. another problem is the tradition of naming children after grandparents for several generations. I came across one yesterday with 6 times Elisabeth and 6 times Edward, the merges were a horrible mix of all six of each. We really MUST be careful when we merge. With automerge the extra check of the merger disappears and mistakes go undetected. |
|
|
Private User
6/2/2010 at 1:32 AM
|
Michael Lancaster
@Susanna ths
|
|
6/2/2010 at 2:06 AM
|
@Michael, perhaps an "about" or "circa" date for some of the same name issues would work? I've seen some profiles with the dates included. In my own family, that would be a big help, since fathers, grandfathers, sons etc. all in a row have the same names - sometimes even the same middle names. And also the multiple names within one generation where a child dies and a later child is given the same name. On another note - I know it doesn't belong here, but I can't find any reference to it - what do the stars/asterisks before (or sometimes after) a name mean? Also I've seen a cross before at least one of the big tree names. Can anyone tell me what they're for? Thank you! |
|
|
|
Private User
6/2/2010 at 3:32 AM
|
|
|
Private User
6/2/2010 at 4:44 AM
|
|
|
6/2/2010 at 4:55 AM
|
||
|
6/2/2010 at 5:00 AM
|
Erik, "auto-accept" is a feature on your collaborators page. When set, collaborators that send you merge requests are automatically accepted. It speeds up the merge process, but care should be exercised when using it. I do trust most of my collaborators to do the right thing, however, I have come across examples where I have had to undo merges, so use at your discretion... |
|
|
Private User
6/2/2010 at 5:29 AM
|
|
|
6/2/2010 at 5:53 AM
|
||
|
6/2/2010 at 6:23 AM
|
Showing middle names would go a long way toward avoiding bad stacking, even if just the first 3 or 4 characters. In my tree, half the females are named "Marie" followed by a given name. In the resolve duplicates window, they all look the same! When no birth date is given, one has to take the time to check individually. |
|
|
6/2/2010 at 11:22 AM
|