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

Multiple Townships in Wrong County [1820 Federal Census]

Mark McKenzie_1
Mark McKenzie_1 ✭✭✭
February 1, 2024 edited December 20, 2024 in Search

This is the first time I've seen, potentially, a place error when using the 'Browse' method to view a Federal Census record Image.... It appears the Townships of Brush Creek, Hillsboro, Jackson, Liberty, Middletown, New Market, and Salem, .. should be shown in Highland County, vice Fayette County

https://www.familysearch.org/search/image/index?owc=3L7F-6TT%3A1586985003%2C1586986301%3Fcc%3D1803955

Complicating this issue is that there are Townships of the same name in both Fayette and Highland County, e.g. Concord, Madison, Paint and Union

If you want to look at the entire Reel for this portion of Ohio [Roll 92], Fayette County starts at Image #14, Highland County at Image #58

https://www.familysearch.org/ark:/61903/3:1:33SQ-GYBS-7JL

This co-mingling will impact search results as well

1

Answers

  • Áine Ní Donnghaile
    Áine Ní Donnghaile ✭✭✭✭✭
    February 1, 2024 edited February 1, 2024

    @N Tychonievich Placename standardization (what else?), please and thanks. It's not just townships, but states.

    Pulling an example from the DGS, https://www.familysearch.org/ark:/61903/1:1:XHGQ-W8R

    image.png


    0
  • Mark McKenzie_1
    Mark McKenzie_1 ✭✭✭
    February 1, 2024

    Hadn't noticed the state being 'off' as shown in your example. Although I've seen that in other numerous cases

    What I find odd in this case is that these are all misplaced in the 'Browse' ordering structure as well. In the past I had found that to be 'right' when it came to finding images in a particular/correct place....

    https://www.familysearch.org/search/collection/1803955

    And sadly, when I went back to look thru Roll 92, it didn't take long to find images that were not indexed at all--- Images 28, 33, 36, 38, 40, 42, 47, 49.... I'm sure there more as I stopped there. My goodness what a gordian knot we've made....

    0
  • Áine Ní Donnghaile
    Áine Ní Donnghaile ✭✭✭✭✭
    February 1, 2024

    @Mark McKenzie_1 An automated process gone wrong. N Tychonievich has taken the lead on eventual correction.

    0
  • Mark McKenzie_1
    Mark McKenzie_1 ✭✭✭
    February 1, 2024

    Thanks!!

    0
  • Áine Ní Donnghaile
    Áine Ní Donnghaile ✭✭✭✭✭
    February 1, 2024

    When you see the Event Place (Original) field, as in my screenshot, that's the clue that the standardization bot is the cause. If you'll report those, in Search, with a URL and screenshot, and tagging N Tychonievich, each will be put on the list for eventual correction.

    0
  • Mark McKenzie_1
    Mark McKenzie_1 ✭✭✭
    February 1, 2024

    Thanks!!

    0
  • N Tychonievich
    N Tychonievich ✭✭✭✭✭
    February 3, 2024

    @Mark McKenzie_1 Thank you for reporting the error. I've sent it on to the group that can make corrections. Unfortunately, they are a small team with a large backlog of similar errors, so we can't predict how long it will be before you see a correction.

    1
This discussion has been closed.
Clear
No Groups Found

Categories

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