Home› Welcome to the FamilySearch Community!› 1950 US Census

Are we allowed to use ? and * when correcting names in the Family or Names review of the 1950 Census?

System
System admin
April 5 in 1950 US Census
This discussion was created from comments split from: 1950 US Census Keyboard Shortcut for Review Names.
0

Comments

  • John Empoliti
    John Empoliti ✭✭✭✭✭
    April 4

    Are we allowed to use ? and * when correcting names in the Family or Names review of the 1950 Census?

    2
  • maryellenstevensbarnes1
    maryellenstevensbarnes1 ✭✭✭
    April 4

    Good question @John Empoliti - I doubt AI knows about asterisks for unreadable -- I also found a line where AI showed "None" for a name when the census-taker had written "No one home" for a particular apt. # address --- I reviewed it as a transcription error but I don't know how that will work once the document is online -- let's just pray that internet/political powers let us keep the original census visible instead of destroying it leaving only the AI indexing behind😎

    1
  • John Empoliti
    John Empoliti ✭✭✭✭✭
    April 4 edited April 4

    @maryellenstevensbarnes1

    I was thinking about the situation in which I consider a letter or string of letters is unreadable - notwithstanding that the AI has rendered an opinion. Thus the need for "?" or "*" even in these AI-derived indexes. I know we're supposed to be training the AI, but we're also delivering the result that FamilySearch will publish, and their search engine knows about "?" and "*." We could choose "Unsure" in those cases, but I wondered about using our normal practice in cases like that.

    For the "No one home," "Vacant," and similar AI results, I select "Transcription Error>Not a Name "

    0
  • Mary Louise Lillian
    Mary Louise Lillian ✭✭
    April 4

    I think we should try using ? and * for letters we cannot read in a name or place and see what happens!

    1
  • samshicat
    samshicat ✭✭✭
    April 5

    For regular reviewing, using ? and * is correct, but not for the 1950 census. John Empoliti is correct in using UNSURE. Who knows what the HRT is programmed to do when we click on UNSURE. It's like deleting "NO ONE HOME" instead of marking it as NOT A NAME. We need to follow the rules as directed until told otherwise.

    1
  • Janell Vasquez
    Janell Vasquez ✭✭✭
    April 7

    Yes, it's fine to use the ? and * when reviewing the names for the census.

    2
  • MichaelBennett14
    MichaelBennett14 ✭
    April 7

    Often, when a name listed in the census is unreadable or doesn't look quite right, I research the inviduals. For example, I search newspapers.com and findagrave.com to ensure that odd-looking names really do exist. I search for variations, as needed, along with birth states and approximate birth years. I check for relatives listed with them, and so on... When I do so, I can often identify these individuals quite confidently, and I put their "verified" names in the edit box.

    Does this practice interfere with AI-training that we are supposedly doing while we review names?... And could the "verified" names get removed by later reviews and edits done by those who haven't researched them and are merely ensuring correct transcriptions?

    1
  • Sam Sulser
    Sam Sulser mod
    April 11

    The important thing for the AI is to type what you see. It doesn't hurt to do a little investigation on the side as it sometimes helps with unusual names like you pointed out. Just don't make corrections to what the census taker wrote. When the index is available to be searched, then census taker corrections can be made. Each edit or correction is kept in a history and all of them will be searchable and viewable. Hope that answers your question! Sam ☺️

    0
Clear
No Groups Found

Categories

  • 22.6K All Categories
  • 347 1950 US Census
  • 45.9K FamilySearch Help
  • 90 Get Involved
  • 2.3K General Questions
  • 326 Family History Centers
  • 322 FamilySearch Account
  • 3.1K Family Tree
  • 2.5K Search
  • 3.6K Indexing
  • 427 Memories
  • 4.2K Temple
  • 249 Other Languages
  • 28 Community News
  • 5.3K Suggest an Idea
  • Groups