Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to deploy Industry Exposure Data with models #1082

Open
4 tasks
benhayes21 opened this issue Jul 11, 2024 · 1 comment
Open
4 tasks

Ability to deploy Industry Exposure Data with models #1082

benhayes21 opened this issue Jul 11, 2024 · 1 comment
Assignees

Comments

@benhayes21
Copy link
Contributor

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

  • 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
Copy link
Contributor Author

image

@benhayes21 benhayes21 self-assigned this Jul 24, 2024
@benhayes21 benhayes21 moved this to In Progress in Oasis Dev Team Tasks Jul 24, 2024
@benhayes21 benhayes21 moved this from In Progress to Todo in Oasis Dev Team Tasks Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant