...
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 | UC1 |
| RQ2 | VLO, B2FIND | No (Is the language-related data already harvested?) | Make B2FIND data accessible in VLO DBR: unsure if this is really wanted | UC1 |
RQ3 | VCR, B2ACCESS | Yes. | AAI integration between CLARIN and EOC-hub. different levels ara conceivable: (a) CLARIN users able to access selected EOSChub services (e.g. B2SHARE) (b) CLARIN users able to access all EOSChub services Note that this (SAML federation interoperability) is not a technological but a legal & administrative problem | UC2 |
RQ4 | 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 |
RQ5 | 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 |
RQ6 | LR Switchboard, B2DROP, B2SHARE, ... | Yes. Link from EOSC-hub services to LR Switchboard | Adding a link to the GUI of relevant EOSC-hub services for accessing the LR-Switchboard | UC3, UC5 |
...