Indexing Contact Information with Separators
TLDR CDoe is indexing contact info and asked if the appropriate separators were recommended in the article. @4L5c7 affirms and suggests adding _ for emails.
Powered by Struct AI
1
3
4mo
Solved
Jul 14, 2023 (4 months ago)
CDoe
CDoe
02:56 PMI have a
profiles collection where I'm looking to index basic contact information like people's names, phone numbers, emails, physical addresses, and general notes. I read through the 'tips for common data types' article. Would combining the recommended separators for phone and email seem to work for a use case like this?token_separators: ['(', ')', '-', '+', '@', '.']Jason
Jason
03:48 PMYup that should work
03:48
Jason
03:48 PMMay be add
_ as well for email addresses1
Typesense
Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI
Indexed 3005 threads (79% resolved)
Similar Threads
Restricting `token_separators` to a Specific Field in Typesense
Loic asked Jason about applying `token_separators` to a specific field in Typesense. Jason suggested opening a github issue to add this feature.
3
17mo
Solved
Dealing with Hyphenated Search Results in Typesense
Martin faced issues with hyphenated search results in Typesense. Jainil suggested using `token_separators` to index such search terms separately.
6
2w
Solved
Handling Zero-width Non-joiner in Typesense
Arad inquires about managing a Persian character equivalence in Typesense. Jason advises adding the unicode character to `token_separators` but accepts that single byte characters are only supported currently. A GitHub issue was created.
9
1mo