Study-related variable naming patterns

[t-webber]

Currently, the same items have multiple names. The goal of this discussion is to choose a way to name those variables.

Here are those I encountered:

• study / mission / project
• studyId / studyCode / study (resp. with the mission and project prefixes)
• Junior-Enterprise / Junior-Entreprise / Junior Enterprise (NB: French JEs are "Junior-Entreprise" but they are translated to the English version "Junior Enterprise" for JE Europe).

What are your thoughts?

[liviopersonne]

Hey ! I personally prefer study, studyId and Junior Enterprise
We should also consider how we name different missions that are in a convention cadre.
For example: should 223AE be considered a study, or 223AE-06 ?

[liviopersonne]

Quoique, vu qu'on manipule une id dans prisma (qui n'est pas le code de l'étude), je préfère studyCode

[t-webber]

I agree for studyCode and study.

I think I prefer Junior-Enterprise to Junior Enterprise. But the same doesn't seem to be fix on their official website

[t-webber]

Concerning framework agreements, the current schema isn't very adapted to framework agreements; we need to work on that (assignees correspond to a BC, not the whole study).

It is true we need to find 2 different names, one for 224AA-03 and one for 224AA.

Btw, we also need to agree: lower case or upper case?

[liviopersonne]

I believe that a way to do this is to store all BCs as "study", and create a new schema for CCs.
To do this, I would add a string value to "study", something like "parentId", that would be null if the study is a CE, and the CC's id if the study is a BC.

So for 224AA-03, we would keep the name "study", and for 224AA, we could use something like "framework agreement" or "framework study" or simply "framework".

Also, I prefer upper case.