Home› Ask a Question› Search

Global change of a location name: how to correct?

MarkHeinze
MarkHeinze ✭
February 12 edited February 12 in Search

The location name has changed globally:
Walheim, Behigheim, Württemberg, Germany
has been changed recently and is incorrect. It should read:
Walheim, Besigheim, Württemberg, Germany
It affects hundreds of entries. How to correct this?

0

Answers

  • Áine.ní.Donnghaile
    Áine.ní.Donnghaile ✭✭✭✭✭
    February 12

    @MarkHeinze
    Could you share the URL of an example, please?

    Based on your description, I suspect this may be another instance of the place name standardization problem. It is a known issue, and engineers have been working to correct. They need the specifics, please.

    0
  • Nyx773
    Nyx773 ✭✭✭
    February 12

    @MarkHeinze

    Please define "recently." On what specific date did this name change occur? Only sources and entries after that date would be affected.

    1
  • MarkHeinze
    MarkHeinze ✭
    February 13 edited February 13

    As an example, see the location shown when you query this person's death:
    https://www.familysearch.org/en/tree/person/details/MHYZ-RYP

    As for the date this location name change occurred, I can only say I started noticing this effect this week.

    0
  • Alan E. Brown
    Alan E. Brown ✭✭✭✭✭
    February 13

    @MarkHeinze

    You can go directly to the Places Database and suggest an update. You'll find this particular place here:

    https://www.familysearch.org/en/research/places/?focusedId=2962537

    Note that there are 3 instances for this place, covering 3 different time periods. You can click the Improve This Place button and give your reasons for the fix. This one seems very obvious, since every bit of supporting documentation in the Places Database itself spells the name of the district "Besigheim."

    Since this district is a parent place for Walheim and many other towns, once the parent place is fixed, all locations that are within that district will automatically be fixed.

    0
  • SerraNola
    SerraNola mod
    February 14

    @MarkHeinze I went ahead and reported this error in Places, but for future reference you can do it yourself by following Alan's excellent instructions. Once it is corrected it should update in your sources. Thank you for helping to improve the accuracy of our records!

    0
  • MarkHeinze
    MarkHeinze ✭
    February 14

    Thank you both for your help. Without the link you provided though, I don't know how I would have found that tool for asking for correction. Just curious, for an ask like this name correction, what is a typical turn around time? Should I refrain from using these places till corrected?

    0
  • SerraNola
    SerraNola mod
    February 14 edited February 14

    @MarkHeinze The turnaround time is usually at least two weeks. When it is corrected, it will not automatically update data in Family Tree. That will need to be done manually and if you are manually entering data into the tree for this place name, yes you would want to wait to choose the correct standardized name. However, for attaching records—especially if they were indexed correctly and display correctly in Record Details, add through Source Linker: For example:

    image.png image.png image.png

    Hope that helps.

    0
Clear
No Groups Found

Categories

  • All Categories
  • 45.7K Ask a Question
  • 3.9K General Questions
  • 632 FamilySearch Center
  • 6.9K Get Involved
  • 698 FamilySearch Account
  • 7.2K Family Tree
  • 5.7K Search
  • 1.1K Memories
  • 512 Other Languages
  • 76 Community News
  • Groups