Sections per course

[sbarber2]

On the 2024-10-11 dev call, @ericdbrenner mentioned that the "Biology 101" course that will use the webapp in Spring 2025 has 3 separate sections of 20 students each, with separate instructors per section.

This structure raises the question of whether the webapp ought to support a notion of sections per webapp course or whether each section of the IRL course should be its own webapp course.

The following points were made pro and con:

Pro:

• The overall IRL course has a lead instructor who will want access to each section's data
• Doing statistical analysis over a larger population of samples tends to give more reliable statistics so aggregating across all sections might be desirable, assuming the webapp ever gets the ability to create statistics on more than one movie at a time

Con:

• Adds complexity to the webapp, along with the attendant specification, design, implementation and test effort
• The webapp is not a generalized statistical analysis tool and making it one is not a goal of the project, so perhaps any effort might be better expended in supporting batch exports of per movie analytics (for example, download a spreadsheet with data for all published movies in Course X)

Let's discuss whether to add section features, and maybe define them better as we go.