Home› Welcome to the FamilySearch Community!› Ask a Question› General Questions

Standard Event Place bug on Census Source Linker

J.T. Sobiesczyk
J.T. Sobiesczyk ✭
August 25, 2021 edited July 10, 2024 in General Questions

I have just been linking sources of censuses to individuals in the extended family. As the default text of location in the census sometimes includes 'ward', 'city', or 'side', I have been changing the default to the correct location from the drop-down list. To my dismay, after entering many of these, I discovered that all of my 'corrections' now show as being without a Standard Event Place. Definitely a bug in the programming.


I've included pictures to help show the problem:


  1. The default Residence on the left includes 'Ward 2', which oddly is interpreted as the Town of Oshkosh, not city. (another bug that can't handle Wisconsin's ability to have two municipalities with the same name ('Town of' next to a 'City of' or 'Village of'))
  2. I enter 'Oshkosh' and the drop-down shows.
  3. I select the city entry. All shows well.
Standardized Date entry error 01.jpg
  1. 4. When going to the individual, I notice the red exclamation point, indicating no Standard Location.
  2. 5. On clicking Edit to the Residence, the Standardized Event Place is showing the error triangle and 'No standard is selected'.
Standardized Date entry error 02a.jpg Standardized Date entry error 03a.jpg


  1. 6. I can correct it there and all is well.


In retrospect, trying to keep the data clean has only caused more work overall.

Tagged:
  • Standardized places
  • Field errors
0

Answers

  • dontiknowyou
    dontiknowyou ✭✭✭✭✭
    August 25, 2021

    Yes, this is a known bug.

    Work-around at this time is to not standardize in the source linker, just edit later on the person page.

    0
  • Julia Szent-Györgyi
    Julia Szent-Györgyi ✭✭✭✭✭
    August 25, 2021

    It's a "known bug" in that we've all noticed it, and there have been multiple posts about it here, but I'm not sure anyone from FS has ever officially acknowledged its existence.

    It's not just census records. Any location added using Source Linker is subject to the problem, and it happens even if the Source-Linker-supplied placename is letter-for-letter identical to the standardized placename.

    0
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 43K Ask a Question
  • 3.4K General Questions
  • 571 FamilySearch Center
  • 6.8K Get Involved/Indexing
  • 644 FamilySearch Account
  • 6.5K Family Tree
  • 5.2K Search
  • 1K Memories
  • 2 Suggest an Idea
  • 476 Other Languages
  • 62 Community News
  • Groups