Curation: Feature request - Restrict self publishing to organizational accounts only

[sbarbosadataverse]

Objective:

To help limit spam and other non-data deposits and improve deposits into HDV

Goal:

Restrict depositor "self-publishing" to shibb accounts only; all other "depositors" use "submit for review" once.

Additional requirements:

OK to publish:

• all Shibboleth logins are considered organizational accounts
• anyone publishing into an existing "collection"

Workflow

1. Depositors with non-organization accounts go through submit for review 1x only
2. After the initial published deposit, they are allowed to self-deposit
3. Document this workflow on the repository landing page

How to implement

Open questions:

1. All Shibb accounts are organization accounts
2. All non-shibb accounts are not organization accounts
3. How many ORCID accounts do we have in HDV?
4. How would other installations envision a similar workflow for verifying depositor accounts at any point in the deposit process?

[sbarbosadataverse]

@landreev Can you help us define organizational accounts here? Thnx

[scolapasta]

This would require a change in both how permissions for new depositors work (right now any new depositior for a dataverse collection is of one kind), and a change to the UI / UX for how to define it (since right now it's just a radio button with one of two options).

[cmbz]

Assigning to @sbarbosadataverse for monitoring.