Database consolidation support

[dgets]

Much the same as this issue already implemented in the mobile app along the same lines, we're going to implement database consolidation for when some of the administrations were implemented over a short period of time and should be consolidated into single entries. I think instead of deleting the aforementioned records, as was originally implemented in the mobile app, we are going to mark them invalid in this case, thus keeping track of the original unconsolidated entries in case they are required for some purpose. I'm actually going to add that feature to the mobile version, as well. Too bad I didn't think of it sooner.

[dgets]

Ugh forgot to check and see if the ones that I'm looking at are currently valid. :|

[dgets]

Also, the conditional that attempts to consolidate 3 entries will have to be massaged for correct calculation and comparison of the timedelta as I had to do with the consolidate_two method.

[dgets]

After all of this is done we'll have to add filtering for valid entries in applicable locations throughout the code. :|

[dgets]

Got to make a list of wiped & inserted entries in order to display a status page after completion.

[dgets]

Trial run (debugging):

New Consolidated Records
None: caffeine (1,3,7-Trimethylxanthine Theine) (14.000) administered to: sprite at 2019-07-07 03:37:15+00:00
None: caffeine (1,3,7-Trimethylxanthine Theine) (8.000) administered to: sprite at 2019-07-07 03:37:03+00:00
None: caffeine (1,3,7-Trimethylxanthine Theine) (8.000) administered to: sprite at 2019-07-07 03:36:57+00:00
Old Invalid Entries
34: caffeine (1,3,7-Trimethylxanthine Theine) (10.000) administered to: sprite at 2019-07-07 03:39:39+00:00
32: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:15+00:00
34: caffeine (1,3,7-Trimethylxanthine Theine) (10.000) administered to: sprite at 2019-07-07 03:39:39+00:00
32: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:15+00:00
31: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:03+00:00
32: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:15+00:00
31: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:03+00:00
33: caffeine (1,3,7-Trimethylxanthine Theine) (4.000) administered to: sprite at 2019-07-07 03:36:57+00:00
31: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:03+00:00

Trial run (non-debugging):

New Consolidated Records
36: caffeine (1,3,7-Trimethylxanthine Theine) (14.000) administered to: sprite at 2019-07-07 03:37:15+00:00
37: caffeine (1,3,7-Trimethylxanthine Theine) (8.000) administered to: sprite at 2019-07-07 03:37:03+00:00
38: caffeine (1,3,7-Trimethylxanthine Theine) (8.000) administered to: sprite at 2019-07-07 03:36:57+00:00
Old Invalid Entries
34: caffeine (1,3,7-Trimethylxanthine Theine) (10.000) administered to: sprite at 2019-07-07 03:39:39+00:00
32: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:15+00:00
34: caffeine (1,3,7-Trimethylxanthine Theine) (10.000) administered to: sprite at 2019-07-07 03:39:39+00:00
32: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:15+00:00
31: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:03+00:00
32: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:15+00:00
31: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:03+00:00
33: caffeine (1,3,7-Trimethylxanthine Theine) (4.000) administered to: sprite at 2019-07-07 03:36:57+00:00
31: caffeine (1,3,7-Trimethylxanthine Theine) (2.000) administered to: sprite at 2019-07-07 03:37:03+00:00

[dgets]

In order to avoid processing entries that have already been consolidated multiple times, it would be necessary to go back into applicable_usages and mark them invalid in that array, as well. Of course this would also necessitate testing to make sure that the usages are valid when checking them for timespan inclusion relevance, as well.