How to handle incorrect merges

Started by Private User on Tuesday, April 20, 2010
Problem with this page?

Participants:

Showing all 20 posts
Private User
4/20/2010 at 6:55 PM

Hi All,

I am soliciting advice. I have recently been plagued by incorrect merge proposals from one Pro account who is a collaborator. The proposed merges are clearly incorrect, often having completely different names, parentage, etc. Has anyone had any experience handling this sort of thing? I looked into blocking the user, but that doesn't appear to be a very good solution, and I would very much rather help to correct the behavior rather than leave it to someone else to deal with. Any thoughts?

4/20/2010 at 7:37 PM

Sammy,

I have seen some of the same problems. I just undo the incorrect merge requests.

Kevin

Private User
4/20/2010 at 7:55 PM

Normally, I do as well. This is a bit different. I have cleaned up three stacks tonight that each had 70+ proposed merges. In one of them, there were 3 correct merges. In the other two there were less.

4/21/2010 at 12:17 AM

@ Sammy, unfortunately at this moment; there is no good way to prevent others from merging your profiles, regardless to your connections with them.
I am also experiencing some difficulties with that issue and also have written to someone about it and we agreed to try blocking him; but that didn't helped at all.
I've also noticed that some people don't seem to want to listen to explanations and are just interesting in cleaning up everything and anything without paying attention to the small details that involved in merging.

Private User
7/23/2010 at 7:20 PM

I haven't been on Geni for a few months, came in tonite and found my family has grown by leaps and bounds, but the info is all WRONG! HELP! How do I take them out and block them when I didn't allow it to change in the first place??? I have countless hours invested in my research and it's a mess now.

7/24/2010 at 1:12 AM

One NOTICE!

When You open similar profiles where is more than 2.
And when You use batch merging (checboxes and blue button below)

then result is HUGE AMOUNT of wrong stacked profiles. So PLEASE DON'T USE this feature.

Henn

7/24/2010 at 2:48 AM

When you say you didn't allow it in the first place I suspect you have but unknowingly. If you have shared your tree with anyone, even a close family member, then they can invite someone and then they can invite someone and so on so by inviting just one person you are unwittingly inviting hundreds to join your tree. Don't panic though because mistakes can be rectified much easier now than in the past. Let people know who have made errors and try to get them on board for correcting the mistakes. If you are PRO it will probably be easier than if you are not but if you are not just try to collaborate with someone who is. (this depends on how bad the errors are~ if generations have erroneously been intermarried for instance)
You can always ask for help using the discussion threads as well.

Good luck
Terry

7/24/2010 at 2:50 AM

I forgot to point out that blocking people usually only causes more difficulties because it just means a line of communication is lost it doesn't mean they can't do anything.

Private User
7/24/2010 at 10:39 AM

Thank you Terry, hopefully I can get a handle on it before our tree has tooooo many duplicated limbs.

7/24/2010 at 9:55 PM

Private User You can write to a PRO collaborator and ask them to help you clean up the tree. Please give them the correct information so that they can merge the information correctly. I know that I have fixed some tree branches that have had incorrect information on them. Fixed the parents and the family members, when people have written to me. Of course you need to make sure that the PRO collaborator can merge in the area of the tree that you are working on. Then post a note about the correct information in the profile of that person.

Private User
9/11/2010 at 1:24 AM

As a pro user I am refusing requests to merge were there has been former merges with mthe named person having more than the two normal parents.
If the requestor ant not see that there is something wrong why should I have to sort out the problem created?
Further to that if I do argee to a merge and then look a the tree I find that the merg name a multiple parents and for some resson Geni will not let me sort things out.
So it is no goog you passing all your problems to a PRO to sort out Geni has created its own problems in alloeing you to merge parents with chi,dren and even have parents of the same sex.
I suggest that ALL of you send your views to Geni to get this sorted out

Private User
9/11/2010 at 2:18 AM

Isn't that a deadlock?

How can you expect to merge two profiles with parents without getting four parents? Two plus two is four, you know.

The merge does not stop there, you have to continue connecting the parents, their parents, siblings and so on. Since this is a time-consuming job a lot o people want to get most duplicate branches connected first and then move on connecting the rest instead of have to do the job over and over again when new duplicates hits that area.

If the double set of parents already are wrong is however more serious, but if you get a merge request into such an area is just a good sign showing that someone are focused on cleaning up duplicates and fixing errors in that area. Please don't block them for doing that.

Private User
9/11/2010 at 11:01 AM

Sometime one has to merge profiles that have different parent so that the wrong ones can be disconnected. Before the changes, I would always explain to the person I was sending the merge request to what my reason was for wanting the merge completed. Now we can't do that which leave it up to the person getting the request to try and figure out what the sender was trying to do. No way of knowing if it is a mistake or intentional, now. Much more time consuming for the receiver. My take...

Private User
9/14/2010 at 4:06 AM

This is the reason why i am refusing most on the merge or collaboration requests I receive.
Then when I do look at the tree there are lots of un-merged or partly merged profiles and quite a number of them are wrong.
When I try to correct a mistake Geni informs me that the correction will split the tree and refuses the request.
Another problem is sorting out parents married to their children.
Why can’t members check their data for matching dates before adding or merging?
I do not like the American dating system – why should we be forced to use it?

Private User
9/14/2010 at 7:21 AM

"I do not like the American dating system – why should we be forced to use it?"

Because Geni is an American company.

They may eventually make all fields "international" (the first step was/is translation), but for now you just have to deal with the American system.

I could be mistaken... but I suspect that geni wasn't expecting such a large international userbase as quickly as what geni got.

They started under the assumption that most would be Americans... hence the American style of the site.

Of course, I like much of this style (I'm an American) so it does not bother me.

Reg, while some of your frustration is quite reasonable... the date system is not one of them.

You should have known from the minute you signed up that geni was based in America... and hence would use American styles (and currency, btw), yet you signed up anyway.

Que sera, sera.

Jason P Herbert

Private User
10/5/2010 at 11:40 AM

Jason

There is more to it then that.
Geni does not permit double year entries.
Britain and the British Empire (including the eastern part of what is now the United States) adopted the Gregorian calendar in 1752 by which time it was necessary to correct by 11 days. Wednesday, 2 September 1752 was followed by Thursday, 14 September 1752. Claims that rioters demanded "Give us our eleven days" grew out of a misinterpretation of a painting by William Hogarth. After 1753, the British tax year in Britain continued to operate on the Julian calendar and began on 5 April, which was the "Old Style" new tax year of 25 March. A 12th skipped Julian leap day in 1800 changed its start to 6 April. It was not changed when a 13th Julian leap day was skipped in 1900, so the tax year in the United Kingdom still begins on 6 April.
It is possible and also correct to have a baby born on say 1st April 1750 and die 11 months later on 1st March 1750.
Some people try and convert the dates for January to March into the new Gregorian calendar, but there is no way of tell if this has already been done. The only way to check is be looking at the original documents.
We need Geni to adopt a more flexible approach to things.

10/5/2010 at 8:30 PM

Reg,

I'm sure geni would welcome an angel investor in their software platform. :) :)

10/5/2010 at 9:22 PM

Sammy,

I was seeing the same thing, and it took me quite awhile to figure out what was going on. I started by being charitable and thinking there must be a good reason, and I think I found it -- for example, all the Gerberges, wife of a certain Robert had been stacked irrespective of parents, children, other marriages, etc. The person was right at that moment working through the stack, merging the correct ones and unstacking the incorrect ones. I've been able to verify every time that this is what I'm seeing by checking the Revisions tab. If someone else is working there right at that moment, I go work somewhere else. As a general rule, I try to give my collaborators the benefit of the doubt, and not think they're nuts until they've left a stack like that for 24 hours ;)

10/5/2010 at 9:28 PM

Thank you for raising that point, Justin.

When there's a tangle sometimes I have found it easier to merge in the incorrect information and then "break the connection" after to sort them back out to their right places in their families.

10/6/2010 at 10:12 AM

Wow, Reg. What a dating nightmare! I had no idea it was so complex. Thanks for explaining.

Showing all 20 posts

Create a free account or login to participate in this discussion