For an upcoming conference, people submitted around 150 abstracts.
Each one has been reviewed, with a numeric score and optional text content.
So each abstract is a singular thing, with one average score. But each abstract has multiple comments
And each reviewer is one person, but has multiple comments.
I kind of think this page: https://support.airtable.com/hc/en-us/articles/218734758-A-beginner-s-guide-to-many-to-many-relationships
is what I’m looking for but I got lost after pretty much the first step.
Do I need a junction table? Multiple junction tables?
Is the example at the bottom of the page, Example 3: Clients, client orders, products, and manufacturers, what I’m looking for?
Hi @John_Bakum - A junction table is the right way to go here. You’re trying to track 3 different entities here - abstracts, abstract comments and reviewers - with the following relationships:
- belongs to: abstract
- belongs to: reviewer
Additionally, an abstract has many reviewers through comments and a reviewer has many abstracts through comments. So, comments is a junction table and would look something like this:
Text comments and rating scores (total or average) could be pulled back to the Abstracts table (lookup/rollup fields) or back to the Reviewers table.
This was super helpful, thank you so much!
I have set it up as you described and it’s working.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.