Structuring Database for Different Data Types in a Travel App
TLDR Robert asked for advice on structuring database for a travel app. Jason suggested separate collections for each element type with multi-search, then use a popularity metric to determine the top result.
Jun 04, 2021 (30 months ago)
The UI was very helpful context. I'd recommend storing each of Attractions, Destinations, Countries, Users, etc in separate collections and then do a multi-search to get results from multiple collections.
Then to show the top result, one thing you could do is: assuming you have some sort of metric in each record across different types to indicate popularity (for eg number of reviews, etc), you could pick the first result from each of the individual collections' results, see which one has the max popularity score and display that
Indexed 2776 threads (79% resolved)
Docker Upgrade and Indexing Data Issues for Travel App
The thread discussed upgrading docker while retaining indexing data and addressed search result ranking issues in an app with collections indexed by attractions, destinations, countries, and users. Kishore Nallan provided guidance on adjusting query parameters and weights to improve search outcomes.
Database Management and Personalized Search Queries Discussion
Alexander posed several database and search-related questions. Mac suggested considering GraphQL, considering performance and high availability needs, and leveraging Cloudflare workers. Kishore Nallan provided insights on the capabilities of Typesense and discussed the idea of search personalization using machine learning.
Best Practices for Multisearch Across Collections and Removing Non-important Words
robert asked for best practices on multisearching across collections and deduping results. He later asked about lessening the importance of trivial words in the search results. Kishore Nallan suggested implementing stop words and a proper Q&A model to tackle semantic queries.