Not allowed to merge?
The new merging experience tells me that two profiles "have a high degree of inconsistency. Merging is not recommended." Yet, the new profile has no sources and has the same wife and child. The new profile shows the man born in Virginia in 1600 when no European were in Virginia, while the existing, older profile shows him born in England in 1599 and has 24 good sources attached. The new profile is obviously a weak profile of the same man. However, the new system does not appear to allow the merge to continue, even after I make these observations and reasons for merging. I have clicked on "merge" and "submit" several times. Does this new system really not allow merges that REALLY should be done?
¡Te damos la bienvenida!
Comentarios
-
Did you enter a reason statement? If not, is that what is blocking it? Posting the two IDs would let the developers evaluate the problem, if it is one.
If the issue is that the two men's profile show them born on two different continents, I would view that as a good block. If that is what is going on, all that it should take to be able to merge is to fix the birth place where it is obviously wrong.
0 -
@vNatale thank you for your feedback, and your patience as we work on this beta project. Could you post the PID's for the individuals in this merge. It would be helpful to see exactly what you are looking at.
0 -
Hello Rhonda,
I got frustrated with the Beta test site, so I exited and merged the two already under the current system. However, here is the information: The original profile was for William Carter 99XC-R27, who has 24 sources and shown born about 1599 in England, died in Virginia about 1655. The new profile was William Carter P9WY-JP7, with no sources, shown as born 1600 in Virginia (impossible), died about 1654 in Virginia. Both profiles had the same name and were attached to wife Alice Croxon LBLQ-SZ8. The beta site appeared to not allow me to merge the two men (even though I entered a reason) because their birth locations were so far apart, yet it is readily apparent that the new profile was meant to be the same man as the existing one. As a previous commenter has stated, I could have changed the information on the new profile first, then merged, but that puts a heavier burden on those who are simply trying to assist with keeping the profiles fairly clean and manageable, without multiple spouses of the same name that causes confusion which leads to more errors. I would humbly suggest that the block on merging not be so stringent on the values. I seem to remember when trying to merge under the beta site that the message included that the births of these men were more than ONE DAY different. Surely there's a broader window that that for merging.
Thank you for listening.
1 -
@vNatale thank you for your response. We have created a ticket to look further into these issues.
0 -
Not allowed to merge even with reasons stated. Goes back and forth between Submit and Merge.
0 -
I've had the same difficulty. I realize that there must be a balance between merges that are clearly wrong and merges with inconsistencies that a reasonable person can see are probably just mistakes made by poor research or incomplete entries, etc. Informative warnings should be sufficient and then allow the merger to make the choice ("I teach the people correct principles and let them govern themselves"). 🙂
0 -
@jerroleensorensen1 Do you have an example of a merge that is being totally blocked? I haven't found one yet and in the presentation at RootsTech it was stated that at this point a merge would never be totally prevented.
@HendersonBrentTeamon Can you post the IDs you were trying to merge? What you describe sounds like a programming bug. The engineers are going to need to see specific examples if this is a bug to track down what is going on.
0 -
Gordon — the original two profiles that I mentioned is an example of a merge that was totally blocked. William Carter 99XC-R27 and William Carter P9WY-JP7. (These have been merged under the current system, but the engineers can examine it). As Brent Henderson mentioned, it went back and forth between Submit and Merge with nothing happening.
0 -
I'd like to take a look at an example of this where the people have not been merged yet and test it out to see if there are any clues as to what is really going on. Also, it could be device or browser dependent which is something the engineers would be helped by knowing.
0 -
I'd also love to see one that hasn't been merged yet. Right now, the system should not be disallowing any merges. If you aren't able to merge one, that would be a bug or a usability problem on our side
We'll look into the merged one, but it's a little hard to debug everything after the fact.
Did you add a reason statement?0 -
Hello Mary Anna. Yes, I had written a detailed reason statement, but it would not allow me to merge the two profiles. I even tried a second time. I believe I am not the only one who has seen this happen. HendersonBrentTeamon mentioned that he had the same problem. After entering the reason, the screen seemed to toggle back and forth between Submit and Merge, with nothing happening. jerroleensorensen1 also mentioned having the same problem. I have not experienced that issue again, so I am unable to give another example.
0
