Home› Welcome to the FamilySearch Community!› Ask a Question› Search

Incorrect information on a record that is not editable

osoggy
osoggy ✭
February 24, 2022 edited July 30, 2024 in Search

On this record from the Ohio Death Index:

https://www.familysearch.org/ark:/61903/1:1:VKYB-LJ5 : 30 June 2021

It says that he died in Lucas County, Iowa (which is a real location but NOT in Ohio), instead of the correct location of Lucas County, Ohio. The "edit" button is grayed out so I am unable to correct the location.

Please assist.

0

Answers

  • Julia Szent-Györgyi
    Julia Szent-Györgyi ✭✭✭✭✭
    February 25, 2022 edited February 25, 2022

    This is yet another auto-standardization error: the "Event Place (Original)" field is correct, but the associated standard "Event Place" field is in the wrong state.

    @N Tychonievich, is there any possibility of communicating with the Powers That Be that this problem is ENORMOUS and needs to be addressed with drastic measures as soon as possible? Like, starting with reverting ALL of the changes made by automated processes? They've made an utter travesty of the entire database.

    2
  • Paul W
    Paul W ✭✭✭✭✭
    February 25, 2022 edited February 25, 2022

    It would sometimes appear that the plain, everyday users of FamilySearch have more concern for its reputation and integrity than its engineers and managers. If not, surely there should be a complete hold on any intended enhancements while the engineers concentrate on dealing with problems that have arisen since the introduction of the auto-standardization process, as well as the Search interface.

    It's always good to have enhancements that make our research on the website so much easier, but the grief caused to users by the two aforementioned items really does need to be addressed urgently.

    I (like many others) use FamilySearch practically every day of the year - please don't continue to make things unnecessarily difficult for us by introducing projects like the auto-standardization process, which has had the negative affect of changing perfectly correct placenames into a format that no longer represent the locations in question.

    1
  • PiperTWilson
    PiperTWilson ✭✭✭
    March 2, 2022 edited March 2, 2022

    Hello,

    This is something where I need to thoroughly understand the situation and confirmation, aka more evidence. I am not a subject matter expert, so bear with me. Here is what I think.

    When I look at the record, I see this.

    image.png

    If I understand correctly, the location of residence and the location of death should match in this situation. Since they don't, @osoggy wants to correct the location of death.

    Normally, the Edit button should be blue, which indicates that the member can edit the record. In this case, the edit button is gray so that nothing can be changed.

    We want to make it, so the edit button works.

    If all that is correct, may I have more examples, please? I need to have evidence to take to the team. One example isn't enough.

    0
  • Áine Ní Donnghaile
    Áine Ní Donnghaile ✭✭✭✭✭
    March 2, 2022

    Piper, the example is an index-only record, with no image available. To the best of my knowledge, the Edit option is not available when there is no image. It would be impossible (or at least VERY difficult) to know if the error exists in the index or in the original record.

    The issue here is the one we have discussed in multiple threads about the placename standardization program that went off the rails.

    3
  • PiperTWilson
    PiperTWilson ✭✭✭
    March 2, 2022

    @Áine Ní Donnghaile - I've seen some of them. I'll search to see what I can find on my own, but having a consolidated list would help so very much!

    0
  • Áine Ní Donnghaile
    Áine Ní Donnghaile ✭✭✭✭✭
    March 2, 2022

    A consolidated list would be outdated before it could be compiled. The placename standardization errors are widespread and are only found as we research.

    2
  • PiperTWilson
    PiperTWilson ✭✭✭
    March 2, 2022

    Well, heck!

    0
  • ymsmith
    ymsmith ✭
    March 3, 2022 edited March 3, 2022
    Home

    Home› FamilySearch Help› General Questions

    1901 Census England and Wales

    ymsmith ✭

    March 2

    Why has this 1901 census entry been transcribed as in Newington Green, Middlesex (north of the River Thames), whereas it is clearly located in Newington, Southwark which is in Surrey and south of the River Thames? Please correct, there is no excuse for this kind of error.

    Household Identifier

    676282Record Type

    Household

    Collection Information

    England and Wales Census, 1901


    Learn more about this collection through the FamilySearch Wiki."England and Wales Census, 1901," database, FamilySearch (https://familysearch.org/ark:/61903/1:1:X9H8-YFX : 20 May 2019), John J Soanes, Newington Green, Middlesex, England, United Kingdom; from "1901 England, Scotland and Wales census," database and images, findmypast (http://www.findmypast.com : n.d.); citing St Mary Newington subdistrict, PRO RG 13, The National Archives, Kew, Surrey.

    • Newington Green, Middlesex, is an entirely different location and all references to both need to be removed.
    • See FindMyPast transcript:
    • Registration district St Saviour Southwark
    • Sub-district St Mary Newington
    • Full address is 82, Ash Street, Newington, St Saviour Southwark, London which is in Surrey, England


    image.png


    0
  • Mike357
    Mike357 ✭✭✭✭
    March 3, 2022

    @osoggy, thank you for reporting this auto standardization error. I will forward this information so that it can get into the engineer's queue for resolution.

    You can determine that this is an auto standardization error for place names by (1) noting that there are 2 Event Places; one appearing as '<Event Place> (Original)' and the 2nd as just '<Event Place>'; and (2) noting that the location in the two Event Places are different and unreason - such as your case where the "original" location is Ohio and the other location is Iowa.

    Unfortunately, this is a persistent problem that we have seen for some time, now; and in many difference collections. We know that the engineers are actively working these problems as they are discovered - generally by such diligent user as you. Thus we are anxious to see all instances of this problem reported, so that they can be addressed and resolved.

    @ymsmith, thank you for you input. the auto standardization problem that you describe will not be addressed here, but within the community thread that you began.

    1
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 43K Ask a Question
  • 3.4K General Questions
  • 571 FamilySearch Center
  • 6.8K Get Involved/Indexing
  • 645 FamilySearch Account
  • 6.6K Family Tree
  • 5.2K Search
  • 1K Memories
  • 2 Suggest an Idea
  • 478 Other Languages
  • 62 Community News
  • Groups