Project

General

Profile

bug #7366

TeamOrPersonField readonly if users lacks edit permissions

Added by Andreas Kohlbecker 8 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Highest
Category:
cdm-vaadin
Target version:
Start date:
04/23/2018
Due date:
% Done:

100%

Severity:
critical
Found in Version:

Description

User without sufficient GrantedAuthorities to edit the team or persons in TeamOrPersonField data must be blocked from modifying the data.

Is the visual feedback on the readonly state sufficient?


Related issues

Related to Edit - bug #7586: com.vaadin.data.Property$ReadOnlyException on opening TypeSpecimenWorkingsetEditor Closed 07/26/2018

Associated revisions

Revision 6d29f629 (diff)
Added by Andreas Kohlbecker 8 months ago

ref #7366 TeamOrPersonField read only if user lacks editing permissions

Revision fbae3d00 (diff)
Added by Andreas Kohlbecker 8 months ago

ref #7366 fixing problems with readonly states in TeamOrPersonField and subcomponents and fixing problems with removal and re-adding of entities

Revision c8cf806c (diff)
Added by Andreas Kohlbecker 8 months ago

ref #7366 fixing problems with readonly states while setting values

Revision a8ce6934 (diff)
Added by Andreas Kohlbecker 8 months ago

consistent readonly state of TeamOrPersonField in TaxonNameEditor

Revision 420e07bf (diff)
Added by Andreas Kohlbecker 7 months ago

ref #7366 allowing to remove related TeamOrPerson when TeamOrPerson is readonly

Revision f173032b (diff)
Added by Andreas Kohlbecker 7 months ago

ref #7366 disabling readonly during commmit when TaxonOrPersonField-Editor is write enabled

History

#1 Updated by Wolf-Henning Kusber 8 months ago

Andreas Kohlbecker wrote:

User without sufficient GrantedAuthorities to edit the team or persons in TeamOrPersonField data must be blocked from modifying the data.

Kommentar whk: inhaltlich würde das für den Workflow bedeuten, dass user neue Autoren, Teams anlegen würden und die Kuration dann ggf. Datacleaning macht?

#2 Updated by Andreas Kohlbecker 8 months ago

Wolf-Henning Kusber wrote:

Andreas Kohlbecker wrote:

User without sufficient GrantedAuthorities to edit the team or persons in TeamOrPersonField data must be blocked from modifying the data.

Kommentar whk: inhaltlich würde das für den Workflow bedeuten, dass user neue Autoren, Teams anlegen würden und die Kuration dann ggf. Datacleaning macht?

So in etwa.

Ein Submitter kann ein neues Autorenteam anlegen und auch bearbeiten. Sobald eine Registrierung die dieses Teams oder Personen verwendet den Status published erreicht, also als Autor oder als Collector, werden dem Submitter die Bearbeitungsrechte entzogen.

Von anderen Usern erzeugte Autoren und Teams dürfen nur verwendet aber nicht verändert werden.

Alles verständlich?

#3 Updated by Andreas Kohlbecker 8 months ago

  • Description updated (diff)

#4 Updated by Andreas Kohlbecker 8 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 40

#5 Updated by Andreas Kohlbecker 8 months ago

  • Status changed from In Progress to Closed
  • % Done changed from 40 to 100

finally fixed!

#6 Updated by Andreas Kohlbecker 5 months ago

  • Related to bug #7586: com.vaadin.data.Property$ReadOnlyException on opening TypeSpecimenWorkingsetEditor added

#7 Updated by Andreas Kohlbecker 5 months ago

setting the datasource to readonly as it was implemented for this issue was causing problems with the ToOneRelatedEntityReloader, see #7586

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)