...
‘CLARIN user’ is a user working in the CLARIN infrastructure environment. Typical CLARIN users are humanities researchers, most of them are linguists or historians.
‘CLARIN data’ is data specific for the CLARIN community and stored and avaliable from CLARIN centers
...
No. | User stories |
|---|---|
US1 | A researcher wants to find relevant resources by the available metadata, using keywords or other search dimensions (facets) such as date, location, language, format, etc. to use in their work. Many of such resources are available through the CLARIN infrastructure. |
US2 | A linguist wants to be able to find (software) tools that can be used to process the data that they have found. For instance, they want to find a tokenizer for the Dutch language. |
| US3 | A repository manager wants to make a repository and its resources findable for researchers. There may be various forms of resources which may have anywhere from no metadata to well-defined elaborate metadata based on specific schema. |
| US4 | A community manager wants to make some language technology tools findable for researchers. The tools have minimal metadata. |
| US5 | A user wants to be able to discover & access the content associated with a (virtual) collection. The collection can be discovered via a search engine or other means. |
| US6 | A researcher wants to manage a group of resources (not limited to a single existing collection or site) that are relevant for her in a way that they are easily findable, accessible, and citable. |
| US7 | A community manager wants to group related resources from their repository in citable collections. |
| US8 | A researcher wants to know what tools can be used to process a given resource that they have. They may . The resource could have been have found the resource through a EOSC compatible repository or discovery service or have produced it themselves. The resource itself may also be a virtual collection. The researcher would like to have an overview quickly showing a selection of tools that are relevant and useful. |
| US9 | A researcher or software engineer has developed a tool for processing resources. They want to make this tool available, findable, and accessible to as many researchers and users as possible. They prefer if they can make the tool available and maintain it themselves without having to ask help from a middle layer |
| US10 | A user of an EOSC-hub compatible repository or data discovery tool wants to be able to find and access CLARIN data resources and virtual collections from within the service they are using. |
| US11 | A linguist using one of the EOSC-hub compatible discovery or repository services wants to be able to see what linguistic tools they can use to process a given data object, without leaving the environment of the service that they are using. |
...
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 | Make B2FIND data accessible in VLO DBR: unsure if this is really wanted | UC1 | RQ3 | 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. Note that this (SAML federation interoperability) is not a technological but a legal & administrative problem. | UC2 | |
RQ4RQ3 | 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 | |||||
RQ5RQ4 | 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 | |||||
RQ6RQ5 | 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 |
...