Best setup
-
I am trying to build a tool that allows our cyclist member to register to a cycling event.
Basically:
– We have an event every Sunday
– We have a list of predefined routes
– We have a list of our members.
– We ride in three groupsEach week we would like to register who has ridden in which group and what route they have ridden that week.
I would like to get an idea of:
– How many and which people participated on each day
– How many times a person participated.I have now set it up with three pods:
– Routes (with distance and three relationships to events))
– Members (with three relationships to events)
– Events (with title and relationships to routes and members)On each event I can select three routes and choose participants three times. All are relationship fields. This setup works well if I do it for one group, but as soon as I add multiple groups (so basically have three routes/members connected to events), it becomes impossible to retrieve the data.
E.g. for a member Ruud I would like to get:
Event X, participated in group A who did route S with a distance of 50km
Event Z, participated in group B who did route T with a distance of 55kmThis works well as long as there is one group and a single relation, but it becomes problematic to distinguish which rider was in which group, and which route they did.
I find it very difficult to explain better, hope this makes sense.
Should I rethink my setup?
Alternative thoughts:
On each pod ‘events’ it would be great if I could list all members and allow to add a checkbox ‘Group A, B or C’, but I couldn’t find a setup that matched this.The page I need help with: [log in to see the link]
The topic ‘Best setup’ is closed to new replies.