Project

General

Profile

Actions

bug #8192

closed

The curator must be able to unlock a published registration for edition

Added by Andreas Kohlbecker over 3 years ago. Updated over 3 years ago.

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

100%

Estimated time:
Severity:
critical
Found in Version:
Tags:

Description

The curator sometimes needs to modify the data for a registration after it has been published.

Currently it is required to set the registration to another status than published, edit the data and restore the published status. When doing this the registration date is updated, though.

To avoid the registration date to be changed when the curator needs to make modifications we agreed on providing a button for curators by which the registration can be "unlocked" even if it is published or "rejected".

Actions #2

Updated by Andreas Kohlbecker over 3 years ago

  • Status changed from New to Resolved
  • Assignee changed from Andreas Kohlbecker to Wolf-Henning Kusber
  • % Done changed from 0 to 50

done, please review

Actions #3

Updated by Wolf-Henning Kusber over 3 years ago

  • Assignee changed from Wolf-Henning Kusber to Andreas Kohlbecker
  • % Done changed from 50 to 90

Checked in Test-System with two names of Nupela, registered 2018-11-02.

TypeSpecimen: unlock and add a type: works
TypeSpecimen: add locality: works
TypeSpecimen: correct accession number: works
TypeSpecimen: add field number: works
TypeSpecimen: add Geo reference: works

Name: correct epithet: works
Name: add incorrect name: works
Name: correct or add reference detail: works

Im all cases the origninal registration date was kept, as agreed.

These are examples which occur in real life.

Question: are the changes tracked in the system (changed content, updated who, when)?

The critical point is the correction of the epithet (needed if it turns out, that a name published was incorrect in terms of orthography).

Once the nomenclatural status can be added, this will be a major issue for later corrections, e.g. change status from [NULL] to inval. or illeg. This should be tested.

Please check the last lines. If there are no doubts, this ticket can be set to 100% and to closed.

Actions #4

Updated by Andreas Kohlbecker over 3 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF