Actions
feature request #7026
closedRegistrationVoter evaluates CdmAuthorities with RegistrationStatus properties
Status:
Closed
Priority:
Highest
Assignee:
Category:
cdm-vaadin
Target version:
Start date:
Due date:
% Done:
50%
Estimated time:
Severity:
normal
Description
- Registration Stage changes will be triggered via the REST services, (see #7012) this will require the remote user to be granted with the CdmAuthoritiy (REGISTRATION.[UPDATE]{${uuid}}) or with REGISTRATION(${RegistrationStatusTypes}).[UPDATE]{${uuid}} whereas ${RegistrationStatusTypes is a comma separated list of status types (see also below)
- Once a Registration has left the state PREPARATION a per entity permission for this registration must be revoked. Once the curator decides to give the Registration back to the submitter the state will change again to PREPARATION` and the submitter again needs to be able to add typeDesignations. This is rather complicated and could rather easily be achieved by extending the Registration authorities by an optional property which refers to the state of the Registration: REGISTRATION(${RegistrationStatusTypes}).[UPDATE]{${uuid}}, whereas ${RegistrationStatusTypes is a comma separated list of status types . The authoritiy is only applicable as long as the Registration is in the named status.
(both statements copied from #6655)
Related issues
Updated by Andreas Kohlbecker over 6 years ago
- Related to feature request #6655: Implement a RegistrationManager with state machine added
Updated by Andreas Kohlbecker over 6 years ago
- Description updated (diff)
- Status changed from New to In Progress
Updated by Andreas Kohlbecker over 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 50
Applied in changeset cdmlib|77b7dd7606494f59a6134bcc84aa95714b997ffb.
Updated by Andreas Kohlbecker about 6 years ago
- Priority changed from New to Highest
Updated by Andreas Kohlbecker about 6 years ago
- Related to bug #7323: RegistrationVoter ignores uuid if propery given added
Updated by Andreas Kohlbecker about 6 years ago
- Status changed from Resolved to Closed
fully solved now after the bug described in #7323 has been fixed
Actions