Rabbi Eliezer Lipman (Heilprin) Ashkenazi-Halperin [ABD Tiktin], A.B.D. Tiktin - Another Eliezer Lipman Halperin Merger Problem

Started by Private User on Sunday, April 11, 2021
Problem with this page?


Showing all 14 posts
Private User
4/11/2021 at 10:14 AM

Kevin Lawrence Hanit Hello, You may already be aware of this new merger which creates a problem. The merger attempts to conflate two Yitzach Halperins as being the same person when in fact they are different. The merger needs to be reversed,

Private User
4/11/2021 at 10:16 AM

This is the Yitzach who now has two sets of parents: R' Isaac Halpern, A.B.D. Tykocin

4/11/2021 at 11:08 AM

Private User

The same person who made the wrong merger today made more wrong mergers.
I opened a discussion about one of them today.
I do not understand how people who merge, do not see that they cause two different pairs of parents to be, which is completely impossible.
The same people are causing damage to the general tree, and spoiling the hard work that good people do on the site.
I suggest that the CEO of geni determine that only curators can make a merger. This will dramatically reduce the wrong mergers.

4/11/2021 at 11:11 AM

Mike Stangel
I would love your response.
If you establish a policy that only curators can merge, it will also dramatically reduce the wrong mergers and the many forgeries that people make. In addition, in the long run, in my opinion, it will reduce the hard work that curators do.

Private User
4/12/2021 at 1:53 AM

I agree that it would improve the credibility of the tree.
However on the other hand people would be much less likely to participate without the joy of making merger discoveries as positive reinforcement.
How about having to tracks on official and one free - style.
Or how about having an option of a certified merge / tree.
Sounds like work for somebody though. Curators presently do just a percentage of the mergers.

Private User
4/12/2021 at 1:55 AM

Is there a simple way to go back in time and reverse one own mistaken merge?

4/12/2021 at 2:05 AM

Private User
When it comes to rabbinical families, every mistake (even of course in innocence) that someone has made, and of course every forgery (and unfortunately, there are many who forge a connection to rabbinical families) changes the whole big family tree.
I deal with the family tree very much, and so far I have invested in it for 3 years and over 2500 hours, it is very annoying when someone makes a wrong change, and spoils you a lot of hard work you have done.
I can not constantly check every branch and branch.
When only curator will deal with it, I know two things:
1: He is proficient in this work
2: Even if he makes a mistake, it is in innocence, and when you turn to him he corrects.

Private User
4/12/2021 at 9:54 AM

I believe a way to resolve this dilemma is via a technical enhancement of the system: Any merger that either triggers additional mergers (upstream or downstream) or that creates more than one father and/or mother fpr any merger-connected profile would be placed on pending status for 15 days. During that time the person who did the merger and the affected managers must address all the merger flags. If they are not addressed then the merger is automatically reversed. Meanwhile, no new mergers are permitted on any of the flagged profiles during the 15 day period. Each affected profile is tagged with a logo indicating 'Pending Status' and the number of days remaining. Note that I am not including data conflicts in this process which would not be required to be addressed prior to the merger becoming official.

The other upgrade suggestion which I have previously made is to show any available ydna and mtdna haplogroup information next to profile names on ancestor and descendant reports. for example you would have: "John Q. Public (y: J-240, m: HV40b) b1945 Toledo".This simple adjustment would address the problematic issue of identifying the haplogroups of distant relatives of more than 10 steps away who have been tested, without having to visit countless individual profiles one by one. Related to this is the issue of testing upgrades at FTDNA not being automatically integrated into GENI. As it is now, the user must manually disconnect the FTDNA account from GENI and then reconnect so that GENI picks up the new information from FTDNA. This is impractical for most people who have enough else to worry about..

As a mere user I have no idea of the feasibility of making computational changes to the GENI system so I can only hope that perhaps one day when there is an upgrade something like this this could be part of the new GENI.

4/12/2021 at 11:16 AM

Haim Wartski(Hachoen) disallowing anyone but curators from merging is antithetical to the crowd-sourced approach that we embrace.

4/12/2021 at 11:52 AM

Mike Stangel

I understand the approach that geni adopts, but need to see and consider the gaze of the user who deals a lot with the big tree and any change (even if done by mistake and even if done maliciously) changes the whole big general tree, ruining him the hard work he put in
Therefore (in my opinion) need to find a way to balance and combine the desire of the people to engage in merging, and the need to preserve the truth and authenticity of the great general tree.

By the way, the big mistakes that the same person made yesterday (which I am convinced were not made on purpose, but the same person is not versed in the subject), were not corrected, and caused me big changes in my family tree.

Private User
4/15/2021 at 12:40 PM

Did you ask a Curator to undo the merge?

Is it a situation where you should also ask for a Profile to be MPd and relationship locked or??

4/15/2021 at 11:23 PM

There is a person in geni who recently opened hundreds of incorrect profiles parallel to the general tree, and then merged with the general tree and caused very great damage to the tree and very many mistakes.
Makes me wonder why I'm so busy with my family tree, when people come and intentionally fake it and nothing is done.
So I decided to leave geni and set up a family tree on another site

4/17/2021 at 9:09 AM

Private User,

Merge has been reversed.


Private User
4/17/2021 at 10:51 AM

A more simple approach is for everyone that builds a evidence based tree to MP the whole tree straight away, and then merging can be locked pending the manager or curators approval.

Showing all 14 posts

Create a free account or login to participate in this discussion