Ancestry SideView Technology to be Extended

[Gow67]

Thanks a lot.

I see it on the website but not on my app.

Website saying: "Something went wrong. Please try again later."

Now I know where it is though will keep an eye on it.

Thanks again!

G67

[LizzieL]

Thanks a lot.

I see it on the website but not on my app.

Website saying: "Something went wrong. Please try again later."

I keep getting the same thing

[Pheno]

I am reliably told that Ancestry started rolling this out yesterday but have said it will take until midnight tonight (Thursday) before everyone has the feature so a wait and see game.

Pheno

[LizzieL]

Just looked again, I now have labels saying parent 1's side, parent 2's side and unassigned. Where I had already put in maternal or paternal side, no new label has been added, so I don't have confirmation. One at least of my matches where Ancestry has identified a common ancestor which I have verified, has been labelled unassigned, even though I have four shared matches with that person , three of which are now labelled Parent 1's side (my father) and the other I had already labelled paternal side. This one now has a little note "This match is on your Parent 1's side. Do you want to change Parent 1 to Paternal side? This will label all Parent 1 matches Paternal side and Parent 2 matches Maternal side".

[LizzieL]

I have one match who is related on both sides. (Was very surprised when I found it because father from Berks / Oxon and mother from Dorset / Hants coast, but my match's ancestors met up about half way between!). ancestry has labelled this a paternal as we are 3rd cousins through my paternal ancestor and 5th cousins once removed through my maternal ancestor.

[Pheno]

How would you know if you had previously got the assignment between maternal and paternal wrong?

I had previously assigned to either maternal or paternal side and now those same groups of people are saying the same thing and appearing correctly under either maternal or paternal matches.  Would there be some indication that I had said maternal for instance and that the match was appearing in the paternal listing?  Or did I simply get it right every time?

Pheno

[ikas]

Thanks a lot.

Iebsite saying: "Something went wrong. Please try again later."

Now I know where it is though will keep an eye on it.

Thanks again!

G67

I was getting that error message as well. I have just realised it was because I was hitting the new parent button. If you just look at the list of matches you will see they have been allocated to parent 1, parent 2, or unassigned.

I assume pressing the parent button will at some point allow you to select all parent1 matches or parent 2 matches or even unassigned matches. Is this feature already working for anyone?

At first pass it seems accurate but some surprising unassigned.

[Pheno]

I was getting that error message as well. I have just realised it was because I was hitting the new parent button. If you just look at the list of matches you will see they have been allocated to parent 1, parent 2, or unassigned.

I assume pressing the parent button will at some point allow you to select all parent1 matches or parent 2 matches or even unassigned matches. Is this feature already working for anyone?

At first pass it seems accurate but some surprising unassigned.
[/quote]

Yes thats exactly what it is like.  The matches, having used the 'By Parent' heading are then in 3 groups Maternal Matches, Paternal Matches & Unassigned matches.  You then proceed by choosing one of these options.

I have allocated maternal & paternal to Parent 1 & Parent 2.  If you haven't it might be that the headings are Parent 1 matches & Parent 2 matches.

Pheno

[ikas]

Good to hear that parent button is working for you, Pheno. Guess I will just have to be patient. So far I have not found any incorrect allocations but the unassigned is occasionally bizarre. One of my matches is unassigned but her daughter is correctly assigned. Even more inexplicable is another match where ancestry has correctly identified the common ancestor but still labels the match unassigned.