Home› Welcome to the FamilySearch Community!› Suggest an Idea

Standardization sign

ecrasband
ecrasband ✭
February 1 edited February 2 in Suggest an Idea

Why aren't we able to see that the place name is standardized without checking the places place by place. It was MUCH better on the "old" version because of this. Please, "correct" this small problem.

Tagged:
  • Standardizing place name
  • Places Enhancement
  • Places Usability
1
1
Up Down
3 votes

Active · Last Updated February 1

Comments

  • Gordon Collett
    Gordon Collett ✭✭✭✭✭
    February 2 edited February 2

    You can easily see if a place name is standardized or not:

    Not standardized:

    Screen Shot 2023-02-01 at 4.20.26 PM.png

    Standardized:

    Screen Shot 2023-02-01 at 4.20.45 PM.png

    This is even more clear than in the old pages where there was just the red exclamation point with the explanation of what this meant way over in the right hand column.

    Now if you are really referring to the map pin, which never had anything to do with whether a place name was standardized or not, please carefully examine these three examples of place names that are correctly entered in Family Tree, are correctly standardized, but never had one of those exceedingly misunderstood and misused map pins:

    Screen Shot 2023-02-01 at 4.31.03 PM.png
    Screen Shot 2023-02-01 at 4.33.05 PM.png
    Screen Shot 2023-02-01 at 4.33.57 PM.png

    I repeat: All of these are correctly entered. None of these would have a map pin on the old pages. None of them need any correction at all.

    Here is how the editing box looks for each of them:

    place name examples.png

    All of these are correctly standardized as shown by the fact that none of them look like this:

    Screen Shot 2023-02-01 at 4.37.42 PM.png

    The trouble with those map pins is that they led people to "correct" entries like those above that are all correct and degrade the originally entered data.

    2
  • Julia Szent-Györgyi
    Julia Szent-Györgyi ✭✭✭✭✭
    February 2

    There's a very common logical fallacy at the bottom of this. The thinking is that if A implies B, then not-A must imply not-B:

    "Tom is a cat; Bob is not Tom, therefore Bob must not be a cat."

    "Entries with a pin are standardized. This entry doesn't have a pin, therefore it must not be standardized."

    The conclusions "Bob is not a cat" and "this entry isn't standardized" make exactly the same amount of sense -- which is to say, none whatsoever.

    0
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