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

Commas in film numbers: remove, or allow commas in search box

LegacyUser
LegacyUser ✭✭✭✭
March 3, 2020 edited September 28, 2020 in Suggest an Idea
David Townsend Palmer said: In film numbers, please remove the commas, or, allow commas to be used when searching for a film number. The DGS has no commas, so there is no problem copy/pasting it into the search box to search on it. Please make the Film number the same.

It is a small frustration that appears to be easily solved.
Tagged:
  • New
  • Other
0

Comments

  • LegacyUser
    LegacyUser ✭✭✭✭
    March 1, 2020
    Paul said: I agree. A similar problem occurs with a "copy and paste" of certain place names. The records have often been indexed with brackets - e.g. Yorkshire (North Riding) - but this throws up an error message once pasted into a Place field, then making the search.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    March 2, 2020
    Jacob Reid said: Can you give some specific examples of where you are seeing the issue? urls and screenshots would help as well.
    Thanks
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    March 2, 2020
    David Townsend Palmer said: Wa! Today when I do this, put a film number into the film/fiche search box with commas, it takes it and returns results, no problem.

    I hope it stays this way.

    Many thanks.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    March 3, 2020
    Paul said: Jacob

    Here is an example of my problem, although I appreciate it is slightly off-topic and is probably more of an indexing - rather than a programming - problem.

    (URL https://www.familysearch.org/search/r...)



    I use copy & paste to get only results with an exact match of how the place name is recorded (i.e. to hopefully eliminate - in this example, Yorkshire (North Riding) results), so would like to see place names indexed without the parenthesis, in future. Alternatively. please make parentheses valid characters when making a search!
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    March 3, 2020
    Adrian Bruce said: "probably more of an indexing - rather than a programming - problem"
    Well, it's the combination that doesn't work so no-one involved in programming the enquiry screen can blame the indexers nor vice versa.

    The point, however, is well made - the enquiry screen should not reject characters that are valid in place names (or any of the other entries).

    Whether the solution is adjusting the validation or adjusting the data values is up to FamilySearch.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    March 3, 2020
    Adrian Bruce said: Minor aside - looks like Westward Ho! should be OK in a search parameter then! :-)

    Wonder if there are any other oddities?
    0
Clear
No Groups Found

Categories

  • 30.1K All Categories
  • 24.2K FamilySearch Help
  • 126 Get Involved
  • 2.7K General Questions
  • 442 FamilySearch Center
  • 462 FamilySearch Account
  • 4.5K Family Tree
  • 3.4K Search
  • 4.7K Indexing
  • 641 Memories
  • 6.5K Temple
  • 325 Other Languages
  • 34 Community News
  • 6.6K Suggest an Idea
  • Groups