Commit 688e6cab authored by Richard Olav Rud's avatar Richard Olav Rud
Browse files

Minor updates of text and figures

parent e17eaa63
......@@ -70,7 +70,7 @@ All requests will end up in a issue tracking system, where tasks are delegated t
In addition, it should be possible for the different RIs, to connect their specific data curation workflows to the API of the issue tracking systems, in cases where it is possible to aumotate parts of the data curation process. A more detailed explanation of RI specific workflows are available [here](#42-workflows)
![Rought sketch of the components in the system](img/atmo-access-description.png)
Figure 1: Rough sketch
Figure x: Homeless data portal overview
### 2.2 Product Functions
......@@ -123,13 +123,8 @@ The application will run in the browser, and therefore it will not require any s
Details of the user interface design will be documented in a separate user interface specification (MS 5.2).
### 3.3 Software Interfaces
The "Homeless data portal" will connect to the issue tracking system through an API
The "Homeless data portal" will connect to a secondary storage system through an API
**Will need to describe connection the connection through the Mantis API and workflow tools at the RI level, if this should be a part of the scope?**
![Rought sketch of the components in the system](img/atmo-access-description.png)
Figure x: Components and software interfaces
The "Homeless data portal" will need to connect to the issue tracking system through an API.
The "Homeless data portal" will need to connect to a secondary storage system through an API.
## System Features
......@@ -220,13 +215,12 @@ Figure x: Components and software interfaces
##### ACTRIS InSitu
Within ACTRIS, the data submission & curation process is tracked in an issue tracker to have traceable quality control. The issue status indicates where the submission is located in the process. The issue status also indicates who is responsible for the next step.
Below the workflow description and figure describing the ACTRIS In Situ workflow is included.
Figure ![ACTRIS InSitu workflow description](img/in-situ-workflow-description.png)
![ACTRIS InSitu workflow description](img/in-situ-workflow-description.png)
Table x: ACTRIS InSitu workflow description
Below the figure describing the ACTRIS In Situ workflow is included.
Figure ![Workflow ACTRIS InSitu](img/actris-insitu-workflow.png)
![Workflow ACTRIS InSitu](img/actris-insitu-workflow.png)
Figure x: ACTRIS InSitu workflow
##### ACTRIS CLU
......@@ -237,18 +231,10 @@ Figure x: ACTRIS InSitu workflow
#### ICOS
#### Other
Figure ![Workflow ACTRIS InSitu](img/figure3.png)
Figure 3: Workflow for the Homless data portal
## Other Nonfunctional Requirements
## Other Requirements
### 5.1 Safety and Security Requirements
Storage of data and metadata must follow GDPR requirements.
## Other Requirements
Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.
### Appendix A: Glossary
* **Homeless Data:** Data resulting from research campaigns and TNA activities are normally not included into any data management and data curation system and activity. These data sets are “homeless data”, not associated with any long-term projects nor sustainable data centres. The objective of this task is to develop tools facilitating access to TNA data and campaign data for future use through long term, sustainable data centres”
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment