Editing List of ENVRIplus Use Cases
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | = | + | === <span style="color: #BBCE00"> Use Case List </span> === |
The first ENVRIplus week discussed various use cases which potentially could serve to provide the project work packages a better understanding of user and infrastructure requirements and to test solutions. Interesting cases depend on two or more research infrastructures. The lists below were collected for the work packages in theme 2, but should preferable also applicable for other themes. The cases are split in three groups with each a specific purpose as clarified below. | The first ENVRIplus week discussed various use cases which potentially could serve to provide the project work packages a better understanding of user and infrastructure requirements and to test solutions. Interesting cases depend on two or more research infrastructures. The lists below were collected for the work packages in theme 2, but should preferable also applicable for other themes. The cases are split in three groups with each a specific purpose as clarified below. | ||
| − | + | :<u>'''Scientific use case'''</u> | |
| − | *A highly visible frontier research project, dependent on several RI services | + | *''A highly visible frontier research project, dependent on several RI services'' |
| − | *Researchers should be willing to serve as a guinea pig: secure the researchers engagement | + | *''Researchers should be willing to serve as a guinea pig: secure the researchers engagement'' |
:{|class="wikitable" style="background-color:#ffffff;" | :{|class="wikitable" style="background-color:#ffffff;" | ||
|- | |- | ||
| − | + | |# | |
| − | + | |'''Scientific Use Cases''' | |
|- | |- | ||
|SC_3 | |SC_3 | ||
| Line 17: | Line 17: | ||
|} | |} | ||
| − | + | :<u>'''Test case'''</u> | |
| − | *Test if cooperating RIs potentially can implement ENVRIPLUS solutions | + | *''Test if cooperating RIs potentially can implement ENVRIPLUS solutions'' |
| − | *Interesting tests cover instrumentation, data, workflows, and training | + | *''Interesting tests cover instrumentation, data, workflows, and training'' |
:{|class="wikitable" style="background-color:#ffffff;" | :{|class="wikitable" style="background-color:#ffffff;" | ||
|- | |- | ||
| − | + | |# | |
| − | + | |'''Test Cases''' | |
|- | |- | ||
|TC_2 | |TC_2 | ||
| Line 37: | Line 37: | ||
|} | |} | ||
| − | + | :<u>'''Implementation case'''</u> | |
| − | *Follows from the requirements analysis (= RI expectations from ENVRIPLUS) BOTH ENVRIPLUS and RIs have to invest in the actual implementation | + | *''Follows from the requirements analysis (= RI expectations from ENVRIPLUS) BOTH ENVRIPLUS and RIs have to invest in the actual implementation'' |
:{|class="wikitable" style="background-color:#ffffff;" | :{|class="wikitable" style="background-color:#ffffff;" | ||
|- | |- | ||
| − | + | |# | |
| − | + | |'''Implementation Cases''' | |
|- | |- | ||
|IC_1 | |IC_1 | ||
| Line 52: | Line 52: | ||
|- | |- | ||
|IC_3 | |IC_3 | ||
| − | |[[ | + | |[[User support to re-process data using their own algorithms (EISCAT 3D)]] |
|- | |- | ||
|IC_8 | |IC_8 | ||
| − | |[[ | + | |[[Cataloguing, curation, provenance]] across RIs WP8 |
|- | |- | ||
|IC_9 | |IC_9 | ||
| − | |[[ | + | |[[Provenance - use of DOI for tracing of data re-use]] |
|- | |- | ||
|IC_10 | |IC_10 | ||
| − | |[[ | + | |[[Domain extension of existing thesauri]] |
|- | |- | ||
|IC_11 | |IC_11 | ||
| − | |[[ | + | |[[Semantic Linking Framework]] |
|- | |- | ||
|IC_12 | |IC_12 | ||
| − | |[[ | + | |[[Implementation of ENVRI RM for EUFAR and LTER]] |
|} | |} | ||
| − | |||
| − | |||
| − | |||
