Home› Welcome to the FamilySearch Community!› FamilySearch Help› Search

Should complete or standardized places be preferred? Why are standardized places not specific?

Rollins, Spencer Dee
Rollins, Spencer Dee ✭
March 23, 2022 edited March 25, 2022 in Search

For example this record: https://www.familysearch.org/ark:/61903/1:1:MJWM-JJF?from=lynx1UIV8&treeref=LK5K-1J3 seems to have a wrong place name. It should be 4119 West Jackson Boulevard, Chicago, Cook, Illinois, United states. With the standardized place being Chicago, Cook, Illinois, United States. Was it indexed incorrectly? Why do we not want to include additional information?

0

Best Answer

  • maryellenstevensbarnes1
    maryellenstevensbarnes1 ✭✭✭✭
    March 23, 2022 Answer ✓

    Street Names and Numbers change over time, as do city and county boundaries - this record of a Census seems to me to have been indexed correctly with the information requested by the record owners/custodians

    1

Answers

  • Sam Sulser
    Sam Sulser Community Manager
    March 23, 2022

    @Rollins, Spencer Dee the beauty of the index is it provides enough information to search for the record which in this case leads to the image where you can see the exact address of your ancestor. It was indexed correctly based on what was requested of the indexer. People wouldn't likely search by a full address but they would search by a city or county so that was what was requested. Standardized places are meant to capture the jurisdictions of a location, usually city, state, country or the equivalent but something lower jurisdictions like a cemetery, parish, township, and others. I hope this helps! 🙂

    1
Clear
No Groups Found

Categories

  • 30.2K All Categories
  • 24.4K FamilySearch Help
  • 127 Get Involved
  • 2.7K General Questions
  • 444 FamilySearch Center
  • 467 FamilySearch Account
  • 4.5K Family Tree
  • 3.4K Search
  • 4.7K Indexing
  • 643 Memories
  • 6.6K Temple
  • 326 Other Languages
  • 34 Community News
  • 6.7K Suggest an Idea
  • Groups