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

Is familysearch aware?

S. Stults
S. Stults ✭
July 23, 2021 edited August 15, 2024 in Search

I was just wondering if FamilySearch is aware that a majority of U.S. 1830 and 1840 census records are indexed incorrectly?

I spend a lot of time submitting edits to the records, however, there is no way to correct them all.

I can only correct one record at a time, when in all actuality the entire page of search results are in need of correction.

Example: There will a be a record that appears in search results for "Rhea, Oklahoma", however it should be for "Rhea, Tennessee" and when you actually go to the image of the document across the top (the location info the that page) is correct.

Another example of what I am talking about in the images below.

Pending image.png

When looking at a particular film, where all locations are in the same state, there are many incorrect results. They should be Sullivan County, Tennessee and Stewart County, Tennessee.

If I go to view the record image for Wm Crutsinger, the correct information is listed above the record image. as you can see below.

Pending image.png

All of the names on this page above would only be found in search under Sullivan, Scott, Arkansas instead of Sullivan, Tennessee.

As far as I can tell this is only an issue for the 1830 and 1840 US Census'. And I wasn't sure if FamilySearch was aware that this needed to be fixed.

Tagged:
  • Record Searching
  • Indexing
  • Known issues
  • Report problem
1

Answers

  • Marie4Joy
    Marie4Joy ✭✭✭
    July 24, 2021

    Yes, we are very much aware of these errors. We apologize for this difficulty. Thanks for the detailed report.

    https://www.familysearch.org/help/helpcenter/article/how-do-i-fix-indexing-or-transcription-errors-in-historical-records


    0
  • Julia Szent-Györgyi
    Julia Szent-Györgyi ✭✭✭✭✭
    July 24, 2021

    This sounds to me like a post-processing or metadata error, not an indexing error. The placenames were indexed correctly, but the results were incomplete as locations, and a subsequent process for completing the locations got large parts of it wrong.

    2
  • N Tychonievich
    N Tychonievich ✭✭✭✭✭
    July 25, 2021

    @S. Stults We can forward this auto-standardization of places error to a team of specialists. Someone on that team will be in touch if they need additional information.

    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
  • 644 FamilySearch Account
  • 6.5K Family Tree
  • 5.2K Search
  • 1K Memories
  • 2 Suggest an Idea
  • 476 Other Languages
  • 62 Community News
  • Groups