Commit 49ab1dd0 authored by Richard Olav Rud's avatar Richard Olav Rud
Browse files

Update atmo-access product description

parent 77d891fc
......@@ -66,7 +66,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 automate parts of the data curation process. A more detailed explanation of RI specific workflows are available [here](#42-workflows)
![Rough sketch of the components in the system](img/atmo-access-description.png)
![Rough sketch of the components in the system](img/atmo-access-homeless-data-portal.png)
Figure 1: Homeless data portal overview
### 2.2 Product Functions
......@@ -74,26 +74,27 @@ Figure 1: Homeless data portal overview
#### User View
* Form:
* Open the website, fill in form with PI information and information describing the dataset or collection of dataset from TNA and/or campaign activities
* Open the website, fill in form with PI information and information describing the dataset or collection of dataset from TNA and/or campaign activities.
* Feedback:
* User will receive an email confirmation and a link to the issue tracking system
* User will receive an email confirmation and a link to the issue tracking system.
* Issue tracking system:
* Open issue tracking system, see "tickets" associated to a specific user, as well as the status
* Open issue tracking system, see "tickets" associated to a specific user, as well as the status.
#### System View
* Form:
* Form information is stored and metadata from form selection is provided to the API of the issue tracking system
* Form information is stored and metadata from form selection is provided to the API of the issue tracking system.
* Workflows:
* Depending on the selected parameters and other relevant metadata from the "Homeless data portal" form, different workflows will be triggered in the issue tracking system.
* Form will trigger storage of data in those cases where the data provider wants to provide examples or send the whole dataset together with the form metadata.
* If a file is provide, the file will be saved to a secondary archive, to ensure backup and traceability
* If a file is provide, the file will be saved to a secondary archive, to ensure backup and traceability.
* Feedback
* Issue tracking system will be "in-charge" of sending feedback upon creation and update of a specific issue.
* Feedback to the data provider from any step in the data curation workflow at each RI, should be provided through the centralized issue tracking system.
#### Research Infrastructure (RI) View
* RI will look through the request for providing data and accept/decline in the issue tracking system
* RI will provide all feedback through the issue tracking system
* RI will look through the request for providing data and accept/decline in the issue tracking system.
* RI will provide all feedback through the issue tracking system.
* It should be possible for RI to utilize issue tracking API for integrating the data curation process with their internal workflow and data curation tools.
### 2.3 User Classes and Characteristics
......@@ -232,7 +233,7 @@ Figure 4: IAGOS workflow
## Other Requirements
* Storage of data and metadata must follow GDPR requirements.
* The system aims to use the common login solution proposed by WP5.
* This system aims to use a common login solution for authentication and authorization in WP5. The authentication and authorization should be done at a higher level, and the specific implementation is not to be considered as a part of this task.
### 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