Multiple entry for Project code

[GaelleChapuis]

What we want:

• Multiple project selection at the Subject level ; the current project(s) code(s) is the one displayed on the Admin interface
• The Session acts as a history log of the Subject change, i.e. many-to-many field from Subject to Session
• The Session project code can be change retrospectively in the Session page
• A way to query for a list of all the unique project code a Subject has been listed under

What we have:

• The Session only takes 1 input (alphabetical order, first chosing amongst project code containing ibl)
• No query method

[rossant]

Why is there a need for multiple projects per session?

[GaelleChapuis]

We want to add a project code "practice" onto the current project code, so that it is clear that the intent is to collect data with the main pipeline, but some pipeline guidelines might not be totally followed (e.g. Mouse habituated differently).

As the data can be still valuable, we do not want to only put the project code "practice".
This is different from the project code "test" where only that project code is added into the Subject.

One can later query for sessions with a specific project code and without "practice" if there is a need for refinement.

[nsteinme]

I am strongly in favor of multiple projects being allowed per session!! I will note that this idea of project tags was my proposal originally (#300) and we had agreed at that time to have many-to-many projects-to-sessions... I still think this is correct. I very frequently collect data for multiple purposes in a single session.