페이지 트리

버전 비교

  • 이 줄이 추가되었습니다.
  • 이 줄이 삭제되었습니다.
  • 서식이 변경되었습니다.

...

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 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.

US7A community manager wants to group related resources from their repository in citable collections.
US8A 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.
US9A 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
US10A 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.
US11A 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.
US12A user of the VLO (CLARIN or other instance) wants to create and exploit semantic annotation added to VLO metadata. Semantic annotations are meaningful texts that describe or comment on the tagged resource.
US13CLARIN centers need to backup & archive their data for persistency.



Use cases

정보
titleInstruction

A use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language as an actor) and a system to achieve a goal.

Include in this section any diagrams that could facilitate the understanding of the use cases and their relationships.

...

Step

Description of action

Dependency on 3rd party services (EOSC-hub or other)

UC1


  • The VLO is a search tool that can be used to find relevant data by searching through metadata
  • Searching can be done various facets, e.g. date, location, genre, collection
  • The primary users are researchers working in a specific domain for which the set of facets is optimised.
  • Different instances for specific domains can be provided
  • Community data managers can use the VLO to make their data available to a larger audience
  • B2FIND is a general metadata catalogue for non-specific researchers an easier to use, but less specific tool to find resources
  • B2FIND to be used for CLARIN collection level metadata and not for individual resource metadata

VLO, B2FIND

(US1-4)

UC2
  • The VCR is a repository of collection metadata
  • In the VCR virtual collections are defined that contain links to resources stored in other repositories
  • Researchers  can use the VCR to group data into virtual collections of their choosing and make these collections  findable and citable
  • Researchers can seamlessly access virtual collection content

VCR, B2ACCESS

(US5-7)

UC3
  • The LR switchboard can provide a set of relevant tools for specific data types

  • It is not meant as a stand-alone service, but as a feature that can be integrated  with other services.

  • Users can use this feature to find relevant tools for processing data objects directly from within the data discovery or hosting service.

  • Tool and service providers can make their tools available via the LR switchboard by specifying its features (tool metadata).

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

(US12)

UC7B2SAFE/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

(US13)



Requirements

Technical Requirements

...