There is a requirement by model providers to be able to deploy their industry exposure data sets (essentially an OED Location file) with the model data so that it can be used by their users. However, due to certain IP being included in the IED, the Loc file should not be downloadable through the API.
Suggestion to add information into the model settings schema regarding these files, which will set up a pre-canned analysis on the server, which the user will be able to see and run. They should be able to extract the results but not the IED location file.
We could also utilise the approach that we already use for various files which get copied from static data to input data at runtime (events, occurrence, etc.) to keep the data with the model data but include only when selected.
Another consideration is that we need to limit the summary level options on the output, in order to avoid users running by loc number, latitude, longitude, etc, and getting access to the location file through the results
Tasks
[ ] Update Model Data schema to allow details on pre-canned analyses for deployed models
[ ] Add functionality to the server to set up the pre-canned analysis records when the model settings are posted
[ ] add functionality to oasislmf to copy specific location file from static data to input data when selected in the analysis settings
[ ] add functionality to restrict fields allowed for output result summaries
This development will require changes to OasisPlatform, OasisLMF and ODS_Tools
benhayes21
commented
1 month ago
Issue Description
There is a requirement by model providers to be able to deploy their industry exposure data sets (essentially an OED Location file) with the model data so that it can be used by their users. However, due to certain IP being included in the IED, the Loc file should not be downloadable through the API.
Suggestion to add information into the model settings schema regarding these files, which will set up a pre-canned analysis on the server, which the user will be able to see and run. They should be able to extract the results but not the IED location file.
We could also utilise the approach that we already use for various files which get copied from static data to input data at runtime (events, occurrence, etc.) to keep the data with the model data but include only when selected.
Another consideration is that we need to limit the summary level options on the output, in order to avoid users running by loc number, latitude, longitude, etc, and getting access to the location file through the results
Tasks
This development will require changes to OasisPlatform, OasisLMF and ODS_Tools