The idea is to make the system usable by different projects while sharing not only the software itself but also materials such as images, collations and editions.
(There's also the idea of supporting institutions, but projects are more general insofar as they can be composed of users coming from different institutions. If a project is sponsored by a particular institution then that can be reflected in a logo, or in an "About" section)
A user can be part of different projects and thus can have access to different sets of materials. After login in, the user can then be presented with a dashboard with the different projects she is enrolled in.
There should be now the figure of the project administrator, who can add and remove users from the project, and who can manage their permissions. Some users may be read-only, others may have write access. (When it comes to permissions it is better to keep it simple, there is always the tendency to micro-manage permissions and to create ad-hoc user categories).
Project administrators should be able to manage the documents and works available, as well as customizing tags, styles, formats and defaults for the whole project.
Projects can also have subprojects. For example, the Averroes Project may consist of common materials plus the De Animalibus Edition, the Physics editions, and so on.
The idea is to make the system usable by different projects while sharing not only the software itself but also materials such as images, collations and editions.
(There's also the idea of supporting institutions, but projects are more general insofar as they can be composed of users coming from different institutions. If a project is sponsored by a particular institution then that can be reflected in a logo, or in an "About" section)
A user can be part of different projects and thus can have access to different sets of materials. After login in, the user can then be presented with a dashboard with the different projects she is enrolled in.
There should be now the figure of the project administrator, who can add and remove users from the project, and who can manage their permissions. Some users may be read-only, others may have write access. (When it comes to permissions it is better to keep it simple, there is always the tendency to micro-manage permissions and to create ad-hoc user categories).
Project administrators should be able to manage the documents and works available, as well as customizing tags, styles, formats and defaults for the whole project.
Projects can also have subprojects. For example, the Averroes Project may consist of common materials plus the De Animalibus Edition, the Physics editions, and so on.