Home› Welcome to the FamilySearch Community!› Suggest an Idea

Some 1840 US census reports are no longer indexed to the right place

LegacyUser
LegacyUser ✭✭✭✭
June 22, 2020 edited September 28, 2020 in Suggest an Idea
Ryan Torchia said: I'm seeing this happen more often. The search and record lists a different place, although the images are in the correct catalog. Here's two examples:

https://www.familysearch.org/ark:/619...
https://www.familysearch.org/ark:/619...
Indexed as Surry, Virginia, but for Surry, North Carolina

https://www.familysearch.org/ark:/619...
https://www.familysearch.org/ark:/619...
Indexed as Wayne, Mississippi, but for Wayne, Kentucky

These were indexed correctly before -- the residence entries for them show the correct location. They're not found if you search for the location.

I've also seen a lot of entries where they can't resolve the location, so it just links to "United States", even though they're filed into the right catalogs:
https://www.familysearch.org/search/r...
Tagged:
  • Record Searching
0

Comments

  • LegacyUser
    LegacyUser ✭✭✭✭
    June 10, 2020
    Tom Huber said: I suspect these were early indexes so when the films were digitized and matched to the indexes, someone missed getting the right image with the associated index entries.

    I can see where this can happen with the same name for a county used in more than one state.

    FamilySearch will need to address this issue and verify the situation in the instances you've found and all other instances where a county name is found in more than one state at the time of the census enumeration.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    June 12, 2020
    Ryan Torchia said: I don't think it's just a problem with how they were indexed, because these used to be working correctly. This is a recently introduced bug, where however the system determines the record location got disconnected from the geographic location the individual volumes were assigned to.

    I honestly think it's affecting the entire 1840 census database, but just isn't apparent when the indexed location is complete enough for the system to guess the right place. My guess is it'd be a relatively easy fix.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    June 22, 2020
    Ryan Torchia said: Any update on this? Is somebody at least looking into it? It's still happening and severely impeding progress.
    0
Clear
No Groups Found

Categories

  • 22.6K All Categories
  • 347 1950 US Census
  • 45.9K FamilySearch Help
  • 90 Get Involved
  • 2.3K General Questions
  • 326 Family History Centers
  • 322 FamilySearch Account
  • 3.1K Family Tree
  • 2.5K Search
  • 3.6K Indexing
  • 427 Memories
  • 4.2K Temple
  • 249 Other Languages
  • 28 Community News
  • 5.3K Suggest an Idea
  • Groups