move the input of project information details from the catalog into the project creation form

[MyPyDavid]

Rationale / Begründung

A researcher wants to fill in the project information when creating a project and start to plan the RDM when answering the questionnaire.

An editor wants to keep the catalogs lean, specific for a theme and avoid redundant questions.

Project information details (start and end date, responsible persons, project ID, Funder, etc.) are currently asked at the beginning of a questions catalog. This can be confusing for a user who wants to start to plan their RDM with RDMO.
An improvement could be to move these type of questions (related to detailed information on the project) out of the catalog and into some general questions at project creation or project details model. These formal questions do not need to be necessarily integrated in the questions catalog, since these type of formal information questions do not require elaborate help texts or option sets.
In this case, the catalogs can be kept leaner, more specific and avoid asking for redundant or general project information.

Affected

Users, Managers

Minimal functionality

• add a project details model or expand the project model and form to contain more fields with details that are usually found in the catalogs.
• allow these details to be filled in by the user at some point during project creation or later at any given time.

Nice-to-have functionality

Suggestions

• the filling in of project details is optional, except for the title and chosen catalog
• add new fields to the Project model
  • start and end date of the project
  • project ID (e.g. funding ID, project ID from institution, etc. )
  • funding agency
  • ... other related fields (tbd. with respect to the question catalogs)

References / Verweise

• Project model
• ProjectForm
• more or less the same as Overview of basic project information #477

[jochenklar]

We have as little information as possible in the Project model, since it is not customizable. This is debatable of course.

[jwindeck]

For the new UI/UX design, we discussed adding a project status field. So far, no decision has been made on whether we want to include it. But it is part of the design draft.

This field could be optional for sites and configurable through the server settings for each site, allowing every RDMO instance to define its own project phases. If no configuration is provided, the status field would simply not be available.

So, while setting up the new UI, should we go ahead and implement this?

In the future, this could be used to automate certain processes, e.g. it could be combined with conditions and related tasks, exports, or scripts for tasks like archiving projects.

[jochenklar]

There is an experimental PR for this: #1454