Changes between Version 5 and Version 6 of Ticket #770


Ignore:
Timestamp:
May 4, 2015, 3:44:30 PM (5 years ago)
Author:
olle
Comment:

Description updated again by reinstating the requirement that a copy of the biosource item be created, but changing the reason to only being that no references to log data are desired.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #770 – Description

    v5 v6  
    44 2. [Tickets #723, #769] Follow-up of step 1, where a web form is presented for a selected retraction object, allowing dates to be entered when different sub-steps are finished. When all sub-steps are marked to have been finished, the items are marked to be ready for deletion/destruction.
    55
    6 This ticket is concerned with the final step, where a retraction object ready for deletion/destruction is selected, after which a list of items to be deleted, and data to be be kept, is displayed. After approval, the items listed for deletion will be deleted from the database, and a copy of the case item will be created, after which the original case item will also be deleted. A copy of the last item is used, in order not to have references to log data for changes of the item data. The reason for keeping a copy of the case item, is to prevent its SCAN-B id value to be reused by a new item.
     6This ticket is concerned with the final step, where a retraction object ready for deletion/destruction is selected, after which a list of items to be deleted, and data to be be kept, is displayed. After approval, the items listed for deletion will be deleted from the database, copies of the case and biosource items will be created, after which the original case and biosource items will also be deleted (biosource here refers to a "patient" item of type `Retract` or `RetroNo`). Copies of the last two items are used, in order not to have references to log data for changes of the item data. The reason for a keeping a copy of the case item, is also to prevent its SCAN-B id value to be reused by new items.