Retraction wizard - Step 3: Destruction

[olle]

Retraction wizard steps:

1. [Ticket #526] Marking extracts for retraction, produce lists and protocols to simplify finding these in the lab or external storage.
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.

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.

[olle]

Ticket accepted.

[olle]

Traceability note:

• The retraction wizard was introduced in Ticket #526 (Retraction wizard), which covered step 1.
• It was updated in Ticket #723 (Retraction wizard - Step 2: Follow up), which covered step 2.
• Retraction wizard step 2 was updated in Ticket #769 (Retraction wizard - Additions to Step 2: Follow up).
• Step 3 of the retraction wizard was introduced in Ticket #770 (Retraction wizard - Step 3: Destruction) - This ticket.
• The retraction wizard servlet was cleaned up in Ticket #781 (Clean up code in retraction wizard)
• The retraction wizard was updated to support BloodDNA in Ticket #787 (Add support for BloodDNA items), where also support for Blood items without any Case item was added.

[olle]

Background:

The full retraction module is intended to contain 3 parts:
1. Mark extracts for retraction. (Ticket #526)
2. Retraction follow-up (Tickets #723 and #769)
3. Destruction (this ticket)

1. When part 1, "Mark extracts for retraction", is finished, the patient type is changed from "Patient" to "Retract" or "RetroNo". However, for simplicity, it will be referred to as a patient item in this description.
2. Biosource items of type "Retract" or "RetroNo" keep track of what parts in the retraction module have been finished through enumerated string annotation "RetractStatus" with options "ReadyForDestruction" and "RetractionCompleted" (null is default; option "RetractionCompleted" is intended to be set in part 3 "Destruction"). When part 2, "Retraction follow-up", is finished, annotation "RetractStatus" is set to value "ReadyForDestruction".

Functional specification for the retraction destruction part:

3. Step 1: A case name or personal number should be input:
   a. If a case name is input, the patient related to that case should be found. As is described in the next section, the "patient" item will technically be a biosource item of type "Retract" or "RetroNo", instead of "Patient", but for for simplicity, it will be referred to as a patient item in this description.
   b. Part 3, "Retraction destruction", is not intended to be used until parts 1 and 2 are finished, so it is natural to include a check that the patient type is correct for retraction ("Retract" or "RetroNo"). In addition, annotation "RetractStatus" should have value "ReadyForDestruction".

[olle]

Description updated by only requiring that a copy of the case item be created, but not the biosource item.