We are starting development of a meteor app that allows users to create a profile, submit a set of search criteria and receive products (held in the app's db) curated by an administrator. I am wondering what the most elegant way of setting up the collections for this would be.
So far, our thinking is to:
- Automatically generate user id's (accounts-ui package) and roles (alanning:meteor-roles package) as soon as the search process is started
- Add all user information, including the user id and role generated in step 1, to a "clients" collection
- Add all search criteria selected by the user, as well as the user-id, to a separate "searches" collection.
- Use search criteria to filter objects in a "products" collection, and deliver results to an admin who then manually curates from filtered results.
Given the information I've provided, does this sound like the most elegant structure?