Pro Search not indexing names with apostrophes
Development and Programming
Hi all, I have a site that uses Pro Search for all search on the site. Much of the data is personal names. I have found that search results for data containing names with apostrophes (O’Connor, O’Hanlon etc) result in a list of results were the main records appear, but do not include the name or the additional actual record data. Looking at the Pro Search lexicon the names do not exist, even though they are in the main database, and when I attempt to add these words to the lexicon it says the name is not a valid word.
Any thoughts would be most welcome.
It seems like you’re facing an issue with the Pro Search system not recognizing names with apostrophes in the lexicon. Here are some suggestions to help you resolve this:
Lexicon Customization: If the Pro Search lexicon does not accept names with apostrophes, check if there is an option to enable special characters or to create a custom lexicon that allows for such entries. Sometimes, systems have settings that control how words are validated.
Escape Characters: Try using escape characters or different formatting methods when adding these names to the lexicon. Some systems require specific syntax for special characters.
Consult Documentation: Review the Pro Search documentation or user manual for guidance on handling names with special characters. There may be specific instructions or best practices for adding such entries.
Support Contact: If the issue persists, consider reaching out to Pro Search support. They may have encountered similar issues and can provide a solution or workaround.
Alternative Search Methods: As a temporary solution, consider implementing a separate search function that handles names with apostrophes specifically, or preprocess the search queries to normalize the names before they are sent to Pro Search.
By exploring these options, you should be able to improve the search results for names containing apostrophes.
Pro Search currently cannot index names with apostrophes in the lexicon. The solution is to normalize names for search purposes while preserving the original data for display, and optionally preprocess search queries to match the normalized form. This approach is user-friendly and keeps search results accurate for real names. @Geometry Dash Game
The problem stems from the search engine’s dictionary, which has a built-in validation rule that rejects apostrophes. This causes names to not be recognized as “valid words” and therefore not be included in the full search results level devil, even though the data already exists in the main database. This is a serious bug for a system that handles personal names, as it directly affects the accuracy and functionality of the site’s search feature.