Import experience for researcher

[ikethecoder]

OCWA Issue

User Story

As a researcher,

I want to be able to import my own data sets into the Secure Analysis Environment (SAE)

so that I can use them as part of my research.

Test Case

ENV

• DEV
• TEST
• PROD

TESTCASE

• Log into importer-ocwa-cddi-dlt-dev.bgddi.com
• Create a new request
• Upload files
• Submit request

EXPECTED

• Title should show "OCWA Importer Tool"
• Language on the site should have "Input" instead of "Output" (i.e./ Input Checker, Input Files)
• Input Package Descriptions same as the Output Package Descriptions

Technical Notes

• add two new frontend deployments: importer-ocwa and importer-ocwa-download
• introduce a Request "direction" attribute - which can be "out" or "in"
• use a new attribute 'zone' in the JWT, to identify whether the user is inside or outside the Secure Analysis Environment (inside_sae, outside_sae)
• add filtering to the request api based on the 'zone' - if outside_sae, requests must either be of direction "in" or (direction = "out" and state = 4). If inside_sae, if user part of exporter group, requests must either by of direction "out" or (direction = "in" and state = 4). If user part of outputchecker, then zone must be inside_sae and requests can be either "in" or "out" - any state.
• in PolicyApi, add support for named policies that can be specified when calling the ValidateApi
• in frontend server side, use a config parameter to set the 'zone' on the JWT
• in frontend, use a config parameter to affect the language of 'input' vs 'output' (import vs export)