Inventions in Search results impacting the PQS
Earlier today, I posted about an issue I saw in Search results for Ireland Civil Registrations. Just now, I saw that those invented dates are impacting the PQS.
My 2nd GGM, Sarah Hughes McGarrity, was born in September 1836 and died on 10 May 1891 in County Tyrone, Ireland.
Ireland began birth registration in 1864; we only have Sarah's baptism from 1836. Her 1891 death record (#217) does not contain a date of birth, just her age last birthday, 56.
An apparent recent change to the index algorithm now shows her birth as June 1835, and an error is called out when there is no error in the record or the index - just some invention.
Consistent with Sources
- Sarah M'Garrity, "Ireland Civil Registration Indexes, 1845-1958" has a date
of June 1835 for birth, which is different from September 1836.
If you look at the index, you'll see there have been baseless changes made to the dates. https://www.familysearch.org/ark:/61903/1:1:FTC3-32L
Name Sarah M'Garrity
Age 56
Birth Year (Estimated)
Jun 1835
Apr 1835
Event Type Death Registration
Event Date
Jun 1891
Apr 1891
Event Place Omagh, County Tyrone, Ireland
Page Number 215
Volume Number 2
There is, of course, no feedback option on the index or the search results. Perhaps someone here will have more luck with having these inventions removed and, better yet, stopped.
Thank you.
Kommentare
-
I see a further issue in Sarah's profile L8P5-LL7 from her Findagrave.com listing. Findagrave uses Northern Ireland for ALL years, so I can't change that, but PQS' Consistent with Sources shows an extra comma in the place that is not present in the Findagrave.com listing. Is that perhaps a PQS algorithm problem that can be corrected?
Sarah Hughes McGarrity, "Find a Grave Index" has a place of Carrickmore, ,
County Tyrone, Northern Ireland for burial, which is different from
Carrickmore, Termonmaguirk, County Tyrone, Ireland.URL of the memorial: https://www.findagrave.com/memorial/115491608/sarah-mcgarrity
Thanks.
0 -
Thank you for the feedback. A ticket was created for this issue.
0
