D81 OpenAIRE data model » History » Version 1
Paolo Manghi, 27/02/2015 10:36 AM
| 1 | 1 | Paolo Manghi | h1. D81 OpenAIRE data model |
|---|---|---|---|
| 2 | |||
| 3 | *Leader*: CNR. *Participants*: All technical partners. |
||
| 4 | |||
| 5 | h2. Subtasks |
||
| 6 | |||
| 7 | * Exchange requirements with technical partners (and OpenAIRE guidelines management team) involved into parallel technical activities in order to identify and agree on changes to the data model; |
||
| 8 | * Change the data model accordingly; |
||
| 9 | * Notify all tasks leaders of changes to the data model that may impact on their activity. |
||
| 10 | |||
| 11 | h2. Task Timeline (Including Deliverables & Milestones) |
||
| 12 | |||
| 13 | * The data model will be updated with three official releases at M4, M18, M30 to reflect the changes required by the new services and end-user requirements. |
||
| 14 | |||
| 15 | h2. Areas of priority (where to concentrate first) |
||
| 16 | |||
| 17 | h2. Discussion (https://issue.openaire.research-infrastructures.eu/issues/1089) |
||
| 18 | |||
| 19 | h2. Forseen Integration with other Work Packages and Tasks |
||
| 20 | |||
| 21 | * All tasks need to interact with this task in order to set changes to the data model and to be notified of changes that may impact on their development. |
||
| 22 | |||
| 23 | h2. Communication Strategy: when and how to raise awareness among consortium of updates in task |
||
| 24 | |||
| 25 | * Changes to the data model may impact on our end-users and third-party services (http://api.openaire.eu). When this is the case, such actors need to be informed via OpenAIRE networking communication channels, and the new schema be published. |