D101 Visual workflow editor » History » Version 5
Mateusz Kobos, 06/03/2015 02:31 PM
| 1 | 4 | Mateusz Kobos | h1. Task 10.1 Visual workflow editor with other internal enhancements |
|---|---|---|---|
| 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 IIS-internal “visual workflow editor” for an easier way to manage data flow between modules (i.e., functionalities) of IIS. |
||
| 9 | ** Implement tools to provide an easier feedback from OpenAIRE portal on modules of IIS. |
||
| 10 | |||
| 11 | 4 | Mateusz Kobos | h2. Task Timeline (Including Deliverables & Milestones) |
| 12 | 1 | Paolo Manghi | |
| 13 | 5 | Mateusz Kobos | * Aug 2015 (error in DoW: Oct 2015) (deliverable D10.1): “Visual workflow editor”: report on design, implementation, rationale, and main functionalities of the solution. |
| 14 | 1 | Paolo Manghi | * Dec 2015 (milestone M10.1): “Visual workflow editor”: production version of the solution integrated with IIS. |
| 15 | |||
| 16 | h2. Areas of priority (where to concentrate first) |
||
| 17 | |||
| 18 | * Finish activities (integrations etc.) that were started in OpenAIRE+. |
||
| 19 | * Migrate code to GitHub. |
||
| 20 | 4 | Mateusz Kobos | * Deliver deliverables explicitly required by DOW ("visual workflow editor"). |
| 21 | 1 | Paolo Manghi | * Improve flexibility and ease of use of IIS. |
| 22 | |||
| 23 | h2. Forseen Integration with other Work Packages and Tasks |
||
| 24 | |||
| 25 | * The functionalities delivered in this tasks influence all other tasks in this Work Package. |
||
| 26 | |||
| 27 | h2. Communication Strategy: when and how to raise awareness among consortium of updates in task |
||
| 28 | |||
| 29 | 4 | Mateusz Kobos | * 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. |
| 30 | 1 | Paolo Manghi | * Communication with technical teams through openaire-mining@bwnmail.icm.edu.pl mailing list, issue tracker, mail, and wiki pages (or some similar system). |
| 31 | * The code will be published and later developed in the most popular open code repository: GitHub. |
||
| 32 | * At least one scientific paper describing functionality of the system is planned to be published. |