Project

General

Profile

D101 Visual workflow editor » History » Version 3

Paolo Manghi, 27/02/2015 06:31 PM

1 3 Paolo Manghi
h1. Task 10.1 Visual workflow editor
2 1 Paolo Manghi
3
*Task leader*: ICM. *Participants*: ICM, CNR, ARC.
4
5
* Aim: Make Information Inference Service (IIS) more flexible.
6
* Description:
7
** Implement tools for enhanced resource management within IIS.
8
** Implement “training workflows” to automate calibration of machine learning algorithms in order to accommodate to Information Space data changing in time.
9
** Implement IIS-internal “visual workflow editor” for an easier way to manage data flow between modules (i.e., functionalities) of IIS.
10
** Implement tools to provide an easier feedback from OpenAIRE portal on modules of IIS.
11
12
h2.	Task Timeline (Including Deliverables & Milestones) 
13
14
* Aug 2015 (deliverable D10.1): “Visual workflow editor”: report on design, implementation, rationale, and main functionalities of the solution.
15
* Dec 2015 (milestone M10.1): “Visual workflow editor”: production version of the solution integrated with IIS.
16
* Aug 2017 (deliverable D10.4): “Training workflows”: report on architecture and implementation
17
* Dec 2017 (milestone M10.4): “Training workflows”: production version of the solution integrated with the rest of the system.
18
19
h2. Areas of priority (where to concentrate first)
20 2 Paolo Manghi
21 1 Paolo Manghi
* Finish activities (integrations etc.) that were started in OpenAIRE+.
22
* Migrate code to GitHub.
23
* Deliver deliverables explicitly required by DOW (“visual workflow editor”, “training workflows”).
24
* Improve flexibility and ease of use of IIS.
25
26
h2. Forseen Integration with other Work Packages and Tasks
27
28
* The functionalities delivered in this tasks influence all other tasks in this Work Package.
29
30
h2. Communication Strategy: when and how to raise awareness among consortium of updates in task
31
32
* We plan to continue the tradition established in OpenAIRE+ project of holding monthly technical “status update” teleconferences for parties interested in developments in the work package.
33
* Communication with technical teams through openaire-mining@bwnmail.icm.edu.pl mailing list, issue tracker, mail, and wiki pages (or some similar system).
34
* The code will be published and later developed in the most popular open code repository: GitHub.
35
* At least one scientific paper describing functionality of the system is planned to be published.