zenodo / horizon-zen Goto Github PK
View Code? Open in Web Editor NEWRepository for the EU-funded HORIZON-ZEN project
Repository for the EU-funded HORIZON-ZEN project
Feedback on D2.1
Feedback on QA system deployments
Feedback on PROD
Stakeholders:
Log all dissemination/exploitation activities (RDM telecons, BLR meetings etc) in activities project board.
Deadline to send docs July 19th.
Short report explaining processes and procedures including scheduling, change management, and quality procedures for internal reporting as well as risk mitigation strategy and updates.
Task 1.1: Project management, financial and administrative coordination (M1 - M24) β 1 PM
Perform the overall project administration to manage financial, administrative, and legal obligations of the project (including reporting and quality assurance of it) through a dedicated project management team at CERN. This will include setting up and running the project coordination board, as well as monitoring and control activity throughout the project including management of the schedule, requirements, change, risk, decisions, quality, and transitions to keep the project ton time, budget, and high quality. We will setup the project collaboration infrastructure on GitHub (work items, roadmap, decision log, risk register, issue management, internal documentation), Zenodo (repository for documents and deliverables), and Indico (event/meeting management with agendas and minutes).
Task 1.2: Technical coordination (M1 - M24) β 2 PM
Overall management of the technical part of the project. This will be done by organising and prioritising user needs and requirements, produce and maintain a project roadmap in coordination with the EC. The technical coordination is also in charge of the scoping and planning of the development iterations and releases. We will organise two in-person planning meetings with the EC and conduct regular virtual meetings with the EC. The task is also responsible for producing the projectβs data management plan and maintain throughout the project lifetime (see section 1.2.8 for open science practices).
Deadline to send information Aug 23
Expected results:
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.
Prototype theming for specific communities in the framework of the horizon-zen project
invenio-cli pyshell
from invenio_communities.proxies import current_communities
from invenio_access.permissions import system_identity
service = current_communities.service
ec = service.read(system_identity, "test")
ec_theme = {
"config": {
"primaryColor": "#004494",
"tertiaryColor": "#e3eefd",
"secondaryColor": "#FFD617",
"primaryTextColor": "#FFFFFF",
"tertiaryTextColor": "#1c5694",
"secondaryTextColor": "#000000",
"mainHeaderBackgroundColor": "#FFFFFF",
"font": {"size": "16px", "family": "Arial, sans-serif", "weight": 600},
} ,
"brand": "horizon"
}
res = service.update(system_identity, "test", {**ec.data, "theme": ec_theme)
Invenio-communities branch
Invenio-rdm-records branch
invenio-app-rdm branch
zenodo-rdm branch
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.