The content you are editing has changed. Please copy your edits and refresh the page.
-
-
-
-
Task 2.1: EU Open Research-community (M1 - M2) – 1 PM
Design the user experience and technical specifications for the EOR-community based on the measurable results in specific objectives SO1. This includes designing the support for the EC’s visual identity, subcommunities, verification workflow (for setting up a subcommunity for a project which identifies programme beneficiaries), the deposit workflow and authentication/signup workflow. The design will be done through several iterations and based on collected user stories for the SOs which is translated into a visual prototype for verification by the EC. The prototype will be tested with early adopters and presented to Zenodo/InvenioRDM partners for feedback by WP5. The prototype will be translated into a specification for WP3.
Task 2.2: Data curation framework (M3 - M4) – 1 PM
Design the user experience and technical specifications for the data curation framework (SO2), including the content/curation policy, curation workflow, the automated basic curation checks, and enhanced role-based authorization system. The design will be done and used in same manner as in task 2.1.
Task 2.3 FAIR-enabling deposit workflow (M7 - M8) – 1 PM
Design the user experience and technical specifications for the FAIR-enabling deposit workflow (SO3). This includes how the FAIR assessment tools and discipline-specific metadata will be integrated into the deposit form to provide a seamless user experience, the interfaces for integrating third-party tools as well as support for subject classification. We will evaluate and analyse a suite of FAIR assessment tools based on existing records in Zenodo and select two for integration. Based on the analysis we will develop a model for translating the assessment tools results into actionable advice to the end-user, and for tracking results of FAIRness for records over time. The design will be done and used in same manner as in task 2.1.
Task 3.1: Branded communities (M6 - M9) – 3 PM
Develop the branded community feature designed in Task 2.1, by expanding the Zenodo-community feature to support a custom visual identity with minimal Zenodo branding and use it to implement the EC’s visual identity. The feature will be developed in iterations (see section 1.3) focusing on delivering tangible results to our sandbox system in each iteration, so that user testing can be performed in WP5. The feature will be integrated, documented, and released in InvenioRDM, so that it can deployed in the production system in WP4, and exploited by other InvenioRDM partners.
Task 3.2: Subcommunities (M11 - M15) – 6 PM
Develop the subcommunities feature which supports the identification of programme beneficiaries (verification workflow) as well as the curation workflow designed in Task 2.1 and Task 2.2 by expanding the current Zenodo-community feature to support hierarchies, implement a specialised workflow for requesting subcommunities for EU projects, support EU projects in managing members of their project, and restricting submissions to the EOR-subcommunity to project participants. The subcommunities feature is required for Task 3.3. The feature will be realised in same manner as Task 3.1
Task 3.3: Deposit/curation workflow (M15 – M18) – 4 PM
Develop the designed improvements to the deposit workflow from both Task 2.1, Task 2.2, and Task 2.3 including the means to ensure deposits comply with HE requirements through basic automated curation and its integration into the user interface for the end-user and curator. The feature will be developed in same manner as T3.1.