페이지 트리

버전 비교

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

...

Requirement ID

EOSC-hub service

GAP (Yes/No) + description

Requirement description

Source Use Case

Related ticket

Example

EOSC-hub AAI

Yes: EOSC-hub AAI doesn’t support the Marine IdP

EOSC-hub AAI should accept Marine IDs

UC1


RQ1VLO, 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. This is an adapted technical req (orig. harvest collection metadata through a managed VLO OAI-endpoint.)


UC1

Jira
serverEGI JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId89b2a620-0cec-34da-8cfe-a343203be114
keyEOSCWP10-13

Jira
serverEGI JIRA
serverId89b2a620-0cec-34da-8cfe-a343203be114
keyEOSCWP10-48

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

Jira
serverEGI JIRA
serverId89b2a620-0cec-34da-8cfe-a343203be114
keyEOSCWP10-17

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

Jira
serverEGI JIRA
serverId89b2a620-0cec-34da-8cfe-a343203be114
keyEOSCWP10-17

RQ5

LR Switchboard, B2DROP, B2SHARE, B2FIND, ...

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

Jira
serverEGI JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId89b2a620-0cec-34da-8cfe-a343203be114
keyEOSCWP10-16

Jira
serverEGI JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId89b2a620-0cec-34da-8cfe-a343203be114
keyEOSCWP10-78


RQ6B2NOTE

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

Jira
serverEGI JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId89b2a620-0cec-34da-8cfe-a343203be114
keyEOSCWP10-14

RQ7B2SAFE/B2STAGE

Yes

No single costs and condition listing available

Provide information on all relevant aspects including costs and conditionsUC7

...