37 save data between views use scenarios

[amynickolls]

Created both Session and Saved Scenarios. Session scenarios are how we will transfer data with the user between views. In this implementation it saves the historic data filters, but it will also save any adjustments or prediction inputs as we develop those pages.

Session scenarios are created/accessed through a router_handler that redirects to the relevant URL.

Dashboard page and relevant code has been deleted as this is not in the designs and was complaining re: the updated scenario model.

[tab1tha]

• When filters such as Placement_type=Residential and Age=10 to 16 are added to the historic data tab and then the user clicks away from the tab, the filters remain in place when the user comes back to the tab. This isn't possible on the main branch.
  So the changes in this pull request successfully make filters persist.

[tab1tha]

Other notes
About this pull request.

• I wasn't sure where to click in order to save a scenario.
• When the user filters the historic view to only see 10-16 year-olds in residential placement. Should the plots in the prediction graph only be those which are relevant to the filters in the historic data tab?. Now, the prediction graph seems to remain unchanged irrespective of the historic data filters.

In general

• When I Empty cache and hard reload the browser page (to delete cookies), the application keeps me logged on. Flagging this because it might be expected that the user is logged out when cookies are cleared. It is also possible that my cookies are not being cleared in the way that I think so feel free to ignore this if it works okay on your end.
• It could be nice if the scenario view page had a button from where the user could run the scenario. (this is a screenshot from the scenarios page in the main branch. Didn't get to try out the one in this branch since I couldn't successfully save a scenario so feel free to ignore this if that feature has already been built)

[amynickolls]

Thanks Tambe! All expected for now. Both saving and loading saved scenarios are coming in an issue down the line. Likewise the historic filters will affect the prediction page but this is yet to be implemented.

As for the log in issue might be that you need to close page then clear cache then return?

[cyramic]

Happy to approve, but a few questions first

• Why are the print() statements there? Would they be better to remove or to switch to logging statements?
• Is deleting Scenario and adding SavedScenario, do we need to worry about the migration of data?

[cyramic]

Is there any reason for the print statements? They tend to get lost. I'd either remove these or use the logging library to log them in a consistent way that can be better captured.

[cyramic]

Also, remove the commented ones as well. If you need them, they're still in the git history.

[amynickolls]

The print statements in sandbox are only for my own testing/debugging, the whole thing will be deleted once developed. Is there a better way to do that? I want to keep the commented code just for returning to.

[cyramic]

Is this an appt hat's already live? Will deleting the scenario table and creating a new table without migrating the data be an issue? Don't worry if not.

[amynickolls]

Not live no!