bug #10116
closedCreate a new name denied for users
100%
Description
Blocker (2, role user)
Not able to create a new name in a given reference (submitted by curator or admin)
Title: Create a new name denied
Background: to register a new combination, an external user must be able to add a name in an available reference.
Files
Related issues
Updated by Andreas Müller about 2 years ago
- Target version changed from Unassigned CDM tickets to Release 5.33
Updated by Andreas Müller about 2 years ago
- Related to bug #10115: Create new reference denied for users added
Updated by Andreas Müller almost 2 years ago
- File clipboard-202209072214-vwsjd.png clipboard-202209072214-vwsjd.png added
- Description updated (diff)
Updated by Andreas Müller almost 2 years ago
- Priority changed from New to Highest
Updated by Andreas Müller almost 2 years ago
- Tags changed from phycobank-ready-for-submitters to phycobank-ready-for-submitters, phycobank
Updated by Andreas Müller almost 2 years ago
- Status changed from New to Feedback
- Assignee changed from Andreas Müller to Wolf-Henning Kusber
- % Done changed from 0 to 20
Can you please check in phycobank on test if user "testuserWHK" still has these problems? I added the user manually to the group "submitter" which may solve the problem.
This still needs to be done automatically during self-registration.
Updated by Andreas Müller almost 2 years ago
- Related to deleted (bug #10115: Create new reference denied for users)
Updated by Andreas Müller almost 2 years ago
- Has duplicate bug #10115: Create new reference denied for users added
Updated by Wolf-Henning Kusber almost 2 years ago
Used Testsystem and testuserwhk,
Successful tested:
Create new reference, edit new reference
Create new species, select genus
Select available in-author team
create and save new in-author team
create new author
create new specimen type
create new note
Next step: check what is not possible
Updated by Wolf-Henning Kusber almost 2 years ago
REference: Kusber, W.-H.: TestuserTitle revised. – Phytotaxa 12345: 12345
Task: create a new specimen type for a different reference:
Case 1: different reference not available in PhycoBank
Testuser:
creates new (old) reference
create new (old) name
goto: testuser's new reference
Select the name recently entered, push safe and add new type (for an already published name)
Case 2: different reference available, but needed name not available
Testuser:
select given reference
Testuser adds new (old) name,
goto: tesuser's new reference
Select the name recently entered, push safe and add new type (for an already published name)
Case 3 (buggy): different reference available, needed name available
Testuser select available name
Click on existing name
Popup selected name,
Bug: "Safe" not possible, thus the name [of a different submitter or curator] cannot be used for a new type.
Case 1: often
Case 2: once in a while
Case 3: often
Updated by Andreas Müller almost 2 years ago
Upps, for some reason I did not receive the ticket notification and have not see that you had answered already.
Can you say in short words if the behavior is now as expected or not, and if not, what exactly is not as expected. For me, from the above protocols it is not really clear what the results of your tests are finally.
Updated by Wolf-Henning Kusber almost 2 years ago
Not working as expected (user):
User wants to use an existing name to insert a new lecto-, neo- or epitype designation in a current workingset.
This is blocked because the user gets only the protected view of an existing name.
It is expected to have a button "save" to be availabele to use the given name for a new typification.
Step one: select a given name OK
Push "existing name" OK
See: existing name OK
Safe this existing name: not possible (this is the main problem).
Updated by Wolf-Henning Kusber almost 2 years ago
- Assignee changed from Wolf-Henning Kusber to Andreas Müller
Updated by Andreas Müller almost 2 years ago
- Related to bug #10164: Self registration failed with AuthenticationCredentialsNotFoundException added
Updated by Andreas Müller almost 2 years ago
- Related to bug #10165: email and person data are not stored when creating a new account added
Updated by Andreas Müller almost 2 years ago
- Status changed from Feedback to Resolved
- Assignee changed from Andreas Müller to Wolf-Henning Kusber
- % Done changed from 20 to 80
Wolf-Henning Kusber wrote in #note-15:
Not working as expected (user):
User wants to use an existing name to insert a new lecto-, neo- or epitype designation in a current workingset.
This is blocked because the user gets only the protected view of an existing name.
It is expected to have a button "save" to be availabele to use the given name for a new typification.Step one: select a given name OK
Push "existing name" OK
See: existing name OK
Safe this existing name: not possible (this is the main problem).
This is a new issue and therefore I copied it to a new ticket: #10167.
As the user account is now created with group "Submitter" and all user account information (email, family+given name, prefix) is now correctly stored (#10165) I think we can close this ticket here. Please do final review.
Updated by Wolf-Henning Kusber almost 2 years ago
- Assignee changed from Wolf-Henning Kusber to Andreas Müller
- % Done changed from 80 to 100
Description (was): Blocker (2, role user),
Not able to create a new name in a given reference (submitted by curator or admin)
Test (test system 7 Oct 2022): Now able to create a new name in a given reference for a user (submitter rights): works as expected, thanks!
This ticket can be closed.
Further test: User (see above) is editing a name in a given reference he/she has previously entered and which has the status "in preparation": works as expected.
Further test: User (see above) tried to edit a name in a given reference that has been entered previously by another person and which has the status "in preparation, ready, under curation": Editing is not possible: this works also as expected, because PhycoBank does not allow to change entered data by other users.
Updated by Andreas Müller almost 2 years ago
- Status changed from Resolved to Closed