Home› Welcome to the FamilySearch Community!› Ask a Question› Family Tree

Apaseo el Grande, Guanajuato, Mexico events miscoded as San Felipe, Guanajuato, Mexico

davidleelambert
davidleelambert ✭✭✭
December 30, 2023 edited September 26, 2024 in Family Tree

I found another problem like the ones I previously reported for tens of thousands of tree entries in Cuautitlán, State of Mexico (discussion) and Yehaultepec, Puebla (discussion).

Places in the tree listed as "San Juan Bautista,Apatzeo El Grande,Guanajuato,Mexico" (taken from records kept in San Juan Bautista parish, town of Apaseo el Grande, seat of a municipality of the same name, state of Guanajuato) are incorrectly standardized as "San Juan Bautista, San Felipe, Guanajuato, Mexico". Apaseo el Grande and San Felipe are on opposite sides of the state, a two-hour drive from each other over modern roads, or several days' journey on foot.

See for example José Teodoro christend April 3rd, 1797 (9KNN-2GR) or Antonio Manuel Espinoza married February 3rd, 1802 (M6KB-MCD). In both cases the profile hasn't been touched by anyone except FamilySearch itself. Here's a screenshot of the latter profile.

image.png

0

Answers

  • Áine Ní Donnghaile
    Áine Ní Donnghaile ✭✭✭✭✭
    December 30, 2023

    A 2012 date on a record added to a profile does not mean that FamilySearch itself added the record. It simply means that the record was added in a previous version of the tree, and usernames could not be imported from that earlier version.

    You can edit the entry, as you can with any entry on the tree.

    0
  • davidleelambert
    davidleelambert ✭✭✭
    December 31, 2023
    https://community.familysearch.org/en/discussion/comment/538099#Comment_538099

    Right, I fixed the two records that were relevant to my own research. I thought I should report the pattern of errors, however.

    0
  • Maile L
    Maile L ✭✭✭✭✭
    January 11, 2024

    We appreciate your thoughtfulness about reporting the wrong place standard. I have been told that errors like these are not fixed all together by FamilySearch. They are left up to individuals to correct when they come across them in the Tree. I wish I had a better response than that for you.

    1
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 42.7K Ask a Question
  • 3.3K General Questions
  • 570 FamilySearch Center
  • 6.7K Get Involved/Indexing
  • 640 FamilySearch Account
  • 6.5K Family Tree
  • 5.2K Search
  • 1K Memories
  • 2 Suggest an Idea
  • 473 Other Languages
  • 62 Community News
  • Groups