Configuration

Cohort360 Back-end is configurable

C360 Django apps, their dependencies, and corresponding configurable interfaces

Cohort360 Django Back-end is divided in Django "apps". Here is a description of each app:

• base: this is the main app, it contains shared Django models, users, authentication, logs...

• cohort: this app contains Queries, Cohorts...

• accesses: this app contains the access rights, the roles, the hierarchy of services...

• projects: this app contains "Project", this is not currently used by Cohort360

• workspaces: this app contains "Workspaces", this is not currently used by Cohort360

• export: this app contains Exports models, which are used to let people export data from Cohort360

• voting: this app provides functionalities to vote for the future features, this is not currently used by Cohort360

Configurability:

• You can configure which Django apps you want to use (base, cohort, accesses, database, projects, workspaces, export, voting).

• Some Django apps depends on other apps: for example, the "projects" app needs the "accesses" and "workspaces" app. If you decide not to use the "projects" app, it is fine, but as you can see, the "export" app depends on the "projects" app, so you won't be able to use the "export" app without the "projects" app.

• You can configure parts of the code that interacts with an app: for example, the "cohort" app depends on a "cohort creation interface" that you can configure to send cohort creation requests to a dedicated backend you have developed on your side.