Home› Welcome to the FamilySearch Community!› Ask a Question› Get Involved/Indexing

Should the # symbol be used when indexing . Especially in the Organization name space?

rogerallanmiller1
rogerallanmiller1 ✭
April 11, 2022 edited August 16, 2024 in Get Involved/Indexing

Should the # symbol be used when indexing . Especially in the Organization name space?

0

Best Answer

  • rogerallanmiller1
    rogerallanmiller1 ✭
    April 12, 2022 Answer ✓

    thanks for both of your input. I am more aligned with Barbara as far as not including symbols. However I can also see Marian's point of view.

    0

Answers

  • maryellenstevensbarnes1
    maryellenstevensbarnes1 ✭✭✭✭✭
    April 11, 2022

    @rogerallanmiller1 Please share the Batch Code in [ ] brackets

    0
  • rogerallanmiller1
    rogerallanmiller1 ✭
    April 11, 2022

    Here you go. It is the first entry


    US, New York, Erie—Index to Land Records, Grantees, 1630–1975 [Part B][M32R-ZGW]

    Al

    0
  • Marian McDonald_1
    Marian McDonald_1 ✭✭✭
    April 11, 2022

    @rogerallanmiller1 I see no problem in leaving the # symbol when indexing the information. According to the project instructions: Type the full grantor corporation or organization name as it was written. Do not correct misspellings or expand abbreviations. When indexing we type what we see unless we're told otherwise.

    Thank you for reviewing these records. Have a great afternoon.

    1
  • barbaragailsmith1
    barbaragailsmith1 ✭✭✭✭✭
    April 12, 2022

    We normally don't index symbols. The Field Help says, "If an ampersand (&) or plus symbol (+) was written on a document as a part of information that should normally be indexed, in place of these symbols, type the word And. If parentheses were used, include a space instead of the parentheses." I think the same thing would apply to the #.

    2
  • slotbuddy
    slotbuddy ✭✭✭
    April 12, 2022

    There is no reason to change the # sign. The only reason we change the particular named symbols is because the system used by familysearch cannot recognize them.

    0
  • barbaragailsmith1
    barbaragailsmith1 ✭✭✭✭✭
    April 13, 2022

    Right. Same with the #. We would leave it out as we would ().

    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