| 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. |
| | 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, 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. |
