...
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 Humanities researcher 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. The resource could have been found through an EOSC compatible repository or discovery service or it may have been produced by the researcher. 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 data discovery tool wants to be able to find and access 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. |
...