Project

General

Profile

Actions

bug #7366

closed

TeamOrPersonField readonly if users lacks edit permissions

Added by Andreas Kohlbecker almost 5 years ago. Updated over 4 years ago.

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

100%

Estimated time:
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 ClosedAndreas Kohlbecker

Actions
Actions #1

Updated by Wolf-Henning Kusber almost 5 years 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?

Actions #2

Updated by Andreas Kohlbecker almost 5 years 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?

Actions #3

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
Actions #4

Updated by Andreas Kohlbecker almost 5 years ago

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

Updated by Andreas Kohlbecker almost 5 years ago

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

finally fixed!

Actions #6

Updated by Andreas Kohlbecker over 4 years ago

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

Updated by Andreas Kohlbecker over 4 years ago

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

Actions

Also available in: Atom PDF