ruegenbfr
commented
6 years ago Please clarify intent.
Is the use case just to delete a selected set of stations (/products/lots/deliveries) and all dependent data.
Or
Is the focus on deleting data from a certain import? Because, we don't know whether data from other sources were already merged into the data we want to delete. E.g. Import 1 added station A. Import 2 added station B. The user merges station A into B and all dependent products, lots and deliveries in the corresponding items. The user removes the station B because the DB View shows Import 2 as origin. But he looses information about station A. Because it might not have been clear to him station B replace information from station A. Currently, there is no system in place to detect these kind of scenarios.
Make the deletion of a data set possible. Implement a way to handle all the depending data sets. The database should be able to delete single items of a data set. For example, if a station A was imported via two import templates (template 1: A-B, A-C, A-D; template 2: A-E, A-F) and template 2 seems to have been faulty, it should be possible to delete all data from template 2 without deleting station A (because it is still needed in the data sets from template 1). Perhaps a solution could be to include an additional DB table that lists every data set item (station, delivery,...) toghether with the import source (import from template 1, from template 2, from database xy...) and the import date and time.