D83 Research impact services » History » Version 1
Paolo Manghi, 27/02/2015 09:45 AM
1 | 1 | Paolo Manghi | h1. D83 Research impact services |
---|---|---|---|
2 | |||
3 | *Leader*: ARC. *Participants*: CNR |
||
4 | |||
5 | The task will focus on the realization of general-purpose services for measurement of research impact w.r.t. a “research initiative”. Such services will identify relationships between publications/datasets and a given “research initiative” (e.g. research infrastructures) by offering: |
||
6 | |||
7 | # inference by mining functionality |
||
8 | # end-user claim functionality (i.e. end-users declare links) |
||
9 | |||
10 | Services will also offer UIs for visualizing statistics and measuring research impact over time. As a use-case, the task will focus on the development of pilots with selected National funding agencies (e.g. NWO, DFG, NCBR) and infrastructure initiatives (e.g. EGI, PRACE) in order to serve them with the OpenAIRE research impact suit of services. |
||
11 | |||
12 | h2. Task Timeline (Including Deliverables & Milestones) |
||
13 | |||
14 | The basic task are: |
||
15 | |||
16 | # Selection of funding agencies with the help of the NOADs. |
||
17 | # Technical support for interoperability with funding agencies data sources in order to collect project information from them. |
||
18 | # Identification of the data model changes required to support the integration. |
||
19 | # Interaction with CNR to integrate with back-end services |
||
20 | # Interaction with ICM to integrate inference modules |
||
21 | |||
22 | |||
23 | These tasks will be supported repeatedly throughout the whole lifecycle of the project, as each case of funding agency can result to new technical requirements and data model updates. |
||
24 | |||
25 | h2. Areas of priority (where to concentrate first) |
||
26 | |||
27 | * Work together with NWO and have results by Month 6. |
||
28 | |||
29 | h2. Foreseen Integration with other Work Packages and Tasks |
||
30 | |||
31 | * WP8, WP9 and WP10. |
||
32 | |||
33 | h2. Communication Strategy: when and how to raise awareness among consortium of updates in task |
||
34 | |||
35 | * Participation in technical meetings and Skype calls. |
||
36 | * Communication via e-mail list with NOADs and Skype calls. |
||
37 | * Announcements in the portal. |