Why keep "contributors" separate from real plan users?

[nicolasfranck]

Please complete the following fields as applicable:

What version of the DMPRoadmap code are you running? (e.g. v2.2.0)

3.0.1

Expected behaviour:

The model Contributor allows you to add administrative information about the data managers and the like. But there are restrictions:

• these are not real users. They do not have any access, unless you add them to the plan explicitly in the tab "share".
• their functionality overlaps with "share". E.g. what is the difference between a contributor with role "project administrator" and an "administrator" in the "share" tab?

Of course I can add an initializer that automagically updates the plan roles when I try to add/update a contributor, but that only works well for adding or updating, not for deleting one.

[briri]

Hi @nicolasfranck. This just came up in a conversation we had yesterday. We will be doing some reorganization of the plan tabs in the near future. The 'project contributors' and 'dmp collaborators' will appear on the same tab which will hopefully help clarify this issue. We're also considering consolidating the functionality as you described above but have not yet defined all of the details.

Here is a screenshot of the combined tab in my development environment:

[nicolasfranck]

What do you mean by "consolidating the functionality"? Merging the functionality of the contributors into the collaborators (would be helpfull)? That would require also adding bitfields for those new roles, rewriting code that checks rights..