Re: Best database structure for tracking class, cohorts weeks and feedback

2829 1
Showing results for 
Search instead for 
Did you mean: 
6 - Interface Innovator
6 - Interface Innovator

I have been working on a system to allow me to track my business educational courses at a client, cohort, week bases with feedback loops.

My design was clients, contacts, products/courses, cohort weeks, and finally, attendance. All was going well until I got to track the attendance/feedback… I want to add multiple students to a cohort week as you can see here…
But when I get to the attendance side of thing I have this

I want to use each row of the attendance table to tack the attendance to each cohort week, and as you can see, it’s adding multiple to the same name… so my attendance checkbox and NPS score are not fit for the purpose…

Any ideas how I break this down to a better structure I would be most grateful

2 Replies 2
7 - App Architect
7 - App Architect

You’ve got a many-to-many relationship there, so if you want to store anything in addition to the basic relationship, you’ll need to look at some kind of junction table. Check out Many-to-Many Relationships - Overview | Airtable Support for more details.

Yes, I have read the article… I just cant see what would be in the join table between the cohort weeks and Attendance