alan-turing-institute / data-classification-app

Classification webapp for the Turing Data Safe Haven
MIT License
4 stars 0 forks source link

Default workpackages for egress / ingress #290

Closed bw-faststream closed 4 years ago

bw-faststream commented 4 years ago

As well as the ability to change / remove workpackages

steven-cd commented 4 years ago

Agreed in meeting today that we might actually need two egress packages . @bw-faststream is going to provide titles and descriptions.

I initially said there was already an issue to delete work packages, but there actually wasn't, so I have raised one now (#297)

bw-faststream commented 4 years ago

Egress Work package 1 - Reports and outputs for report finalisation When you're finishing a project, you'll need to complete reports and any other outputs that might be pertinent to the presentation of the research you've done. In this workpackage, you'll be egressing the documents, graphs, pictures and any other data you might need to make it easier to finish the report.

If there are images or details within these outputs that might constitute a tier of 2 or above, these should be removed temporarily for the purposes of the report writing process, to allow you to work outside of the secure environment. A separate discussion should be had between the lead investigator and the data provider representative as to how such items can be suitably redacted so that they can be included in the final document. If the report itself is classified as Tier 2, it will need to be completed and presented within a secure environment.

Datasets: Report inputs including text, images and code snippets.

Egress Work package 2 - Data Provider Handover In this work package, you'll need to include all other outputs, including derived data sets and full code to be returned to the Data Provider for archiving. If this returns a high tier then a conversation needs to take place about where it should be stored, and whether some outputs should be redacted prior to release.

Datasets: All outputs, including text, images, code and any derived datasets.

steven-cd commented 4 years ago

Thanks @bw-faststream . Do you have a description for the ingress work package?

bw-faststream commented 4 years ago

Ingress Work Package

When considering a project, you'll need to consider all the tools and datasets you'll be using (in combination or separately) in a single research environment, as well as what work you'll be doing on the data, to consider the potential sensitivity of the data you'll be using / creating, and how securely it should be handled. Once you're finished with the project, you'll need to carry out separate classifications on the data you'll be taking out of the environment.

Datasets: All inputs, including tools, data and potential products of linking / filtering data.

bw-faststream commented 4 years ago

@steven-cd do those look alright?

steven-cd commented 4 years ago

All the descriptions seem fine to me. The only slight concern I have is with the length of the titles: "Egress - Reports and outputs for report finalisation" is really long, and it interferes with the appearance of some of the buttons (and that's after I've removed the "Work Package 1" bit from it). We can't/probably shouldn't stop people using really long names, but it might be best if we didn't do so by default. I was wondering about just "Egress - Reports and outputs"?

bw-faststream commented 4 years ago

How about Egress - Reports, and Egress - Full

steven-cd commented 4 years ago

Okay, that sounds fine

tomdoel commented 4 years ago

Done in #304