...
Step | Description of action | Dependency on 3rd party services (EOSC-hub or other) |
|---|---|---|
UC1 | A researcher request requests to access the services of the EPOS-ORFEUS CC. He is redirected to the CC Authentication Service (based relying on B2ACCESS in the background) where he registerscan log in at his home institution or create a local account if needed. He receives a token. Depending on his profile he might be authorised to use the services of the CC. Profiles include for instance: data manager, special user (who has access to restricted data) and normal userinformation about the groups he belongs to (e.g. read permission of particular restricted data). | B2ACCESS |
UC2 | A researcher (authenticated and authorised) searches for datasets of her interest by using an API. She selects one ore more staging nodes from the available ones received by interrogating the API. Finally she initiates the data movement by calling a dedicated method of the same API. | B2STAGE, B2SAFE, EIDA WFCatalog (with Dublin Core extension) |
UC3 | A seismologist (authenticated and authorised) wants to perform an analysis on a datasets previously selected and staged. He logs in the Jupyter environment close to the staged datasets. He selects and launches a kernel containing his preferred seismological libraries. When the correspondent Jupiter notebook is up and running the datasets are available in a local directory and he can perform his analysis. He might choose to pause his work and save it for later. Finally he can download results on his PC, move them to his personal cloud storage folder or made them available on a local folder. | EGI Notebook, B2DROP |
...