D93 Zenodo service » History » Version 3
Lars Holm Nielsen, 27/02/2015 06:16 PM
| 1 | 2 | Paolo Manghi | h1. D9.3 Zenodo service |
|---|---|---|---|
| 2 | 3 | Lars Holm Nielsen | |
| 3 | h2. Task Title and Participants, Task Aim and Description (in bullets) |
||
| 4 | |||
| 5 | T9.3 Catch-all data pilot Services: Zenodo |
||
| 6 | Leader: CERN |
||
| 7 | |||
| 8 | Aim: Deliver data repository services that are capable of satisfying the needs of the Horizon2020 data pilot through provision of Zenodo. |
||
| 9 | |||
| 10 | * Any researcher without an appropriate community data repository should be able to rely on the Zenodo service to share and preserve any data from the EU funded programmes. |
||
| 11 | * Extend Zenodo to support the broad range of data publishing initiatives, making it an appropriate testbed for communities to try out these concepts. |
||
| 12 | * Data linking, data citation, and anonymized data, and the closely related services for software description and preservation. |
||
| 13 | * Develop connections with other data repositories for data export and exchange. |
||
| 14 | * Extended service to align with emerging norms for uniquely identifying researchers (ORCID), funders (FundRef) and other relevant entities. |
||
| 15 | |||
| 16 | h2. Task Timeline (Including Deliverables & Milestones) |
||
| 17 | |||
| 18 | * Road maps: |
||
| 19 | > * Zenodo development is planned 3-6 months in advance using 3-months road map. |
||
| 20 | > * See https://github.com/zenodo/zenodo/milestones |
||
| 21 | * Sprints: |
||
| 22 | > * The 3-months road map is divided into 14-days sprints, where each sprint is planned at the beginning of the sprint cycle. |
||
| 23 | > * See https://github.com/zenodo/zenodo/milestones |
||
| 24 | * Release process: |
||
| 25 | > * Zenodo is released (i.e. deployed) often and early (after each sprint) to ensure high speed in delivering new features/bug fixes. |
||
| 26 | |||
| 27 | Large flexibility is needed in the development process in order to ensure fast delivery of new features as well as align development with use case needs. Thus, |
||
| 28 | |||
| 29 | * Deliverables: |
||
| 30 | > * M6, M18, M30: D9.3 Zenodo Specifications [CERN] |
||
| 31 | > * Specifications are defined by our rolling 3-month road maps and the deliverables will be snapshot of these road maps. |
||
| 32 | * Milestones: |
||
| 33 | > * M12, M24 M36: M9.3 Zenodo release [CERN] |
||
| 34 | > * Releases will instead of actually releases simply be a report describing all features launched during the period and how they support our uses cases. |
||
| 35 | |||
| 36 | See full description of development process on http://zenodo.readthedocs.org/en/latest/projectlifecycle.html |
||
| 37 | |||
| 38 | h2. Areas of priority (where to concentrate first) |
||
| 39 | |||
| 40 | Focus areas for the first year include: |
||
| 41 | * Common needs: |
||
| 42 | > * Preservation model and backend data storage improvements |
||
| 43 | > * Data Seal of Approval certification (with DANS) |
||
| 44 | * Use case clinical trial data: |
||
| 45 | > * Confidential peer-review and restricted sharing. |
||
| 46 | > * Policies and process documentation. |
||
| 47 | > * Legal issues. |
||
| 48 | * Use case small libraries/conference proceedings/small journals: |
||
| 49 | > * Branding of communities |
||
| 50 | > * Sub-collections in communities |
||
| 51 | > * Search improvements |
||
| 52 | > * Authentication (eduGain) |
||
| 53 | > * Persistent identification |
||
| 54 | > * Multiple curators |
||
| 55 | * Use case research software developers: |
||
| 56 | > * Engage in prototyping software citation and discoverability in astronomy with key stakeholders. |
||
| 57 | |||
| 58 | Partners for each use case have been identified. |
||
| 59 | |||
| 60 | h2. Forseen Integration with other Work Packages and Tasks |
||
| 61 | |||
| 62 | * Task 4.4 Guidelines for Data providers and OpenAIRE service APIs |
||
| 63 | > * Test-bed and Implementation of guidelines for publication and data archives. |
||
| 64 | * Task 7.1: Legal issues in context of the Open Research Data Pilot |
||
| 65 | > * Identify legal issues related to sharing clinical trial data, and produce easy to read guides for end-users of Zenodo. |
||
| 66 | * Task 9.6: Data Anonymization Services |
||
| 67 | > * Enable seamless deposit into Zenodo of the output data from the service. |
||
| 68 | * WP4 Training and support |
||
| 69 | > * Help give Zenodo webinars |
||
| 70 | > * Regular updates on Zenodo |
||
| 71 | > * Reuse produced training material on Zenodo |
||
| 72 | |||
| 73 | h2. Communication Strategy: when and how to raise awareness among consortium of updates in task |
||
| 74 | |||
| 75 | * Participation in bi-weekly technical meetings. |
||
| 76 | * Sent road map (every 3 months)/sprint (every 14 day) updates to technical mailing list. |
||
| 77 | * Write newsletter articles. |
||
| 78 |