...
Step | Description of action | Dependency on 3rd party services (EOSC-hub or other) |
|---|---|---|
| UC1 |
| VLO, B2FIND (US1-4) |
| UC2 |
| VCR, B2ACCESS (US5-7) |
| UC3 |
| LR Switchboard (US8-9) |
UC4 | Reverse integration of VCR with B2SHARE (B2DROP/B2STAGE?). Users can access and use the VCR from within relevant EOSC services to download or copy the data to a new destination. | VCR, B2SHARE, B2DROP (US10) |
UC5 | Reverse integration of LR Switchboard with B2FIND/B2SHARE/B2DROP The LR Switchboard can be accessed by users from within relevant EOSC services to show what tools can be applied on a given resource | LR Switchboard, B2SHARE, B2DROP (US11) |
| UC6 | Integration of B2NOTE with the VLO. B2NOTE can be used from the VLO as an added discovery mechanism using semantic annotations in addition to metadata. Users can add semantic annotations and search for them. | B2NOTE, VLO |
| UC7 | B2SAFE/B2STAGE use for safe data replication. This already occurs, but CLARIN needs clear costs and SLA statements. The B2SAFE HTTP API is used for connecting Space with B2SAFE. | B2STAGE, B2SAFE, B2SAFE HTTP API |
Requirements
Technical Requirements
...
Requirement ID | EOSC-hub service | GAP (Yes/No) + description | Requirement description | Source Use Case |
|---|---|---|---|---|
Example | EOSC-hub AAI | Yes: EOSC-hub AAI doesn’t support the Marine IdP | EOSC-hub AAI should accept Marine IDs | UC1 |
| RQ1 | VLO, B2FIND | Yes, not all CLARIN metadata is harvested (scaling and mapping problem on the B2FIND side) | Make VLO metadata also findable in B2FIND. At least the available collection metadata should be harvested through a managed VLO OAI-endpoint. B2FIND to harvest CLARIN collection level metadata only | UC1 |
RQ2 | VCR, B2ACCESS | Yes. | AAI integration between CLARIN and EOSC-hub. different levels of integration are conceivable: (a) CLARIN thematic services part of EOSChub ID federation (b) CLARIN users able to access EOSChub services. CLARIN can indicate which extra users (IdPs) will be enabled using EOSC services in this way. Note that this (SAML federation interoperability) is not a technological but a legal & administrative problem. | UC2 |
RQ3 | VCR, B2FIND, B2SHARE | Yes. Link from VCR to EOSC-hub services | Make metadata resources available in relevant EOSC-hub services, e.g. B2SHARE, B2FIND, etc., accessible from the VCR and in suitable format for building virtual collections | UC2 |
RQ4 | VCR, B2SHARE, B2FIND, EGI DataHub, … | Yes. Link from EOSC-hub services to VCR | Make the VCR available when using EOSC-hub repository and discovery services, such that this data can be downloaded e.g. used to make new collections | UC4 |
RQ5 | LR Switchboard, B2DROP, B2SHARE, ... | Yes. Invoking the LR Switchboard from within EOSC-hub services | Adding a capability to EOSC-hub services to invoke the LR switchboard for a data item. This requires information about the data items to be sent to the LR switchboard via a call to its API | UC3, UC5 |
| RQ6 | B2NOTE | Yes B2NOTE not integrated with CLARIN VLO nor connected to CLARIN SPF | Integrate B2NOTE in the VLO, add B2NOTE to CLARIN SPF (note any legal requirements) | UC6 |
| RQ7 | B2SAFE/B2STAGE | Yes No single costs and condition listing available | Provide information on all relevant aspects including costs and conditions | UC7 |
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|
| hosting | hosting services for VLO, VCR and LR-Switchboard | indefinite if suitable SLA and costs |
...