...
Step | Description of action | Dependency on 3rd party services (EOSC-hub or other) |
|---|---|---|
UC1 | User needs to discover the location of all required input data | ESGF Metadata Service/B2FIND |
UC2 | Input data must have a PID associated with it. | Community solutions assigning PIDs, possibly via B2HANDLE |
UC3 | ENES Data Analytics Service must be able to transfer data from its current location to the processing site based on PID (Low priority - I am not sure if we will do this; it is not entirely in the original plan, though I agree it makes sense. It depends on how data input integration ultimately looks like and what can be done with limited effort.) | gridFTP/other? |
| UC4 | Output data must be moved to a site where users can share it for others so they can access it via a link provided by the ECAS system. | B2DROP |
| UC5 | Users will need to register to use the ECAS service | Appropriate EOSC-AAI Solution |
| UC6 | Data must be movable between the output storage in UC4 to a data publication service, where it must be given appropriate metadata and a PID | B2SHARE |
| UC7 | Output data shall have appropriate and sufficient metadata and provenance information associated to enable other users to have trust in the data. | ECAS, B2HANDLE profiles (possibly their usage by B2DROP) |
| UC8 | A link between the output data and the sources must be maintained, in addition to provenance information related to the processing steps. | ECAS, B2HANDLE profiles (possibly their usage by B2DROP) |
| UC9 | Input data must be accessible to the computation regardless of location. | B2HANDLE usage by communities and the DataHub. Support for B2HANDLE PID profiles by DataHub. |
| UC10 | Published output data must be assigned a PID | B2SHARE |
| UC11 | The provenance information must be accessible for published output data | B2SHARE usage of B2HANDLE profiles |
| UC12 | Users will select individual files or entire directories from their ECAS workspace and then select to publish them. The ECAS workspace will inquire a destination location for the files in the user's B2DROP workspace. The publishing workflow for the users will start from the ECAS workspace but end with a view on the publishing repository (B2DROP) showing the newly published files as confirmation. | B2DROP |
...