Home› Welcome to the FamilySearch Community!› FamilySearch Help› Search

Is there a wildcard character, like * on Ancestry?

LegacyUser
LegacyUser ✭✭✭✭
July 11, 2020 edited February 12, 2021 in Search
Is there a wildcard character, like * on Ancestry?
0

Answers

  • Brett .
    Brett . ✭✭✭✭✭
    July 12, 2020

    @Debbie Pavlos​ 

    .

    Debbie

    .

    Provided you are talking/referring to "Searching" ...

    .

    Short Answer: 'Yes'.

    .

    You can just the 'Asterisk' ( * ) symbol, as a "Wildcard" character for searching, both, within "Family Tree" of 'FamilySearch'; and, 'FamilySearch' generally.

    .

    If you are not referring to "Searching", can you please explain.

    .

    Brett

    .

     

    0
  • Melissa S Himes
    Melissa S Himes ✭✭✭✭✭
    July 12, 2020

    Yes. The ? mark is for one unreadable character and the * is for two or more unreadable characters. They also work in searches.

    Here is a link to the FamilySearch knowledge article:

    https://www.familysearch.org/help/helpcenter/article/fields-marked-as-unreadable-in-an-indexed-batch

    0
  • JeffWiseman
    JeffWiseman ✭✭✭
    July 12, 2020

    The original question appeared to have been about wildcards "on Ancestry". Was this about Ancestry.com?

    0
  • Brett .
    Brett . ✭✭✭✭✭
    July 12, 2020

    @JeffWiseman JeffWiseman​ 

    Jeff

    "... like * on Ancestry? ..." [ eg. "like" and "on" being the operative words. ]

    Brett

    ps: I just was not sure it was to do with "Indexing" or not.

    0
  • Dennis J Yancey
    Dennis J Yancey ✭✭✭✭✭
    July 12, 2020

    Assuming you are talking about searching in FS FT or in FS Records

    in most cases the system is doing a "fuzzy" search anyway.

    so in many cases the * is unnecessary.

    FS will automatically find similarly spelled versions.

     

    From those who are providing answers here on this subject - I'd be interested in seeing a very explicit example of how adding the wildcard really brings up something that not using the wild card would not.

     

     

    0
  • Paul W
    Paul W ✭✭✭✭✭
    July 12, 2020

    I use wildcards all the time. For example, earlier today I was looking for a person whose last name I knew to be either FOSTER or FORSTER. I typed FO*STER in the last name field and got the desired results, plus FORRESTER ones. Typing just FOSTER produced FOSTER and FEWSTER results, but no FORSTER. Inputting FORSTER gave me FORSTER, FOREST and FORRESTER results, but no FOSTER ones.

     

    I just now inputted WRIGHTSON, adding "Yorkshire" as a place name and "1800-1820" for the date range. This produced 11,640 results. However, inputting WRIGHTSON* (with these same search limits) gave me only 529 results. The wildcard prevented thousands of WRIGHT results being displayed, which was otherwise the case in the first search.

     

    In these and, I have found, in other situations the wildcard * can make a lot of difference. Try different combinations / alternatives, however. For example, checking the "Exact match" boxes can also help in filtering your results down.

    0
  • JeffWiseman
    JeffWiseman ✭✭✭
    July 13, 2020

    Heh! I missed the comma after the word "character" 😨

    0
  • Melissa S Himes
    Melissa S Himes ✭✭✭✭✭
    July 13, 2020

    I also use wildcards alot to verify information in indexing and in general internet searches. For FamilySearch, especially with cursive, sometimes it is difficult to decipher a name or a place. By using wildcards I am able to bring up possible related images to compare. IMHO, wildcards allow for a more efficient search.

    0
Clear
No Groups Found

Categories

  • 28.7K All Categories
  • 23K FamilySearch Help
  • 115 Get Involved
  • 2.6K General Questions
  • 426 FamilySearch Center
  • 436 FamilySearch Account
  • 4.2K Family Tree
  • 3.2K Search
  • 4.5K Indexing
  • 595 Memories
  • 6.2K Temple
  • 311 Other Languages
  • 34 Community News
  • 6.4K Suggest an Idea
  • Groups