zenodo / horizon-zen

Repository for the EU-funded HORIZON-ZEN project

HORIZON-ZEN

FAIR-enabling deposit services in Zenodo for EU research programme beneficaries

• Call: HORIZON-INFRA-2023-EOSC-REP-ART195-IBA
• Project ID: 101122956

Collaboation tools

• Projects (work plan, user stories, decision log, risks, stakeholders, dissemination activities, KPIs)
• Meetings (Indico) (restricted access)
• Repository (Zenodo-community)
• Google Docs
• [email protected]

Need access? Contact [email protected]

Programme expectations

• Help EU programme beneficiaries to comply with FAIR requirements.
• Enable beneficiaries to see benefits of FAIR data.
• Maximize reuse of EU-funded research outputs.

Expected results

• A new Zenodo-community for the EC's programme beneficaries with a) support for subcommunities for EU-projects and b) identification of programme beneficaries c) visual branding of the EC.
• A workflow to identify a Zenodo user as an EC programme beneficiary.
• A data curation framework that incentivizes programme beneficaries to curate the Zenodo-community supported by automated checks to harmonize curation across beneficaries.
• Integration of FAIR assessment using third-party tools into the deposit form of Zenodo including support for discipline specific metadata/vocabularies.

Work plan

horizon-zen's Issues

Reporting/Review M24

Development: Deposit/curation workflow

Document features for release 1

Development: Subcommunities

FAIR-enabling deposit workflow design (D2.3)

Expected results:

• FAIR metric tracking and translation model
• Interfaces for third-party integration in the deposit/curation workflow.
• FAIR assessment

Dissemination plan update M18

User feedback logbook

Write best practices article

Scope release 1

Release 2 (MS4, Jun 24)

Public training session (MS9, Apr 23)

Tasks

Beta Give feedback

1. Brainstorm: content, announcement channels, tools/services
2. Annoucement of webinar
3. Prepare content/slides

Release and deployment strategy (D4.1)

• Test plan
• Deployment plan
• Acceptance
• Transition

Development: Branded-communities

Horizon-Zen prototype

Context

Prototype theming for specific communities in the framework of the horizon-zen project

Create a theme config for community

• Create a community e.g slug="ec"
• run the code below inside 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)

Resources

RFC in progress

WIP

Invenio-communities branch
Invenio-rdm-records branch
invenio-app-rdm branch
zenodo-rdm branch

Missing action points

• mockups for the two steps solution and community management
• finalize the decision about consistent header for all the communities
• bring back the permission for theme field update
• take into account renaming of the theming variables e.g version the css
• take caching of the community CSS into account

Import MESH vocabulary

Dissemination plan (D5.2)

Tasks

Beta Give feedback

1. Organize meeting with OpenAIRE to align on commnication

Configure and test support for authentication with EU-Login

Tasks

Beta Give feedback

1. Obtain credentials for EU Login from EC
2. Obtain documentation from the EC on integrating EU Login
3. Design login page with the new login option
4. Configure EU Login on QA system
5. Deploy EU Login to production system

Development: Integrated FAIR assessment

Report: Data management plan (D1.2 - Public)

Coordination meeting: Prepare August meeting (30/8 at 09:30)

Deadline to send information Aug 23

Content and curation policy for the Zenodo-communities (D2.2, Sep)

Tasks

Beta Give feedback

1. Prefill EOR-community with existing records #35
   4 of 4
   +0
2. Review EOSC HE requirements
3. Create a QA process for HE requirements
4. Automatically add Open Research Europe platform publications to EOR-community

Dissemination plan update M24

Reporting/Review M12 (dates TBC)

Tools: Setup project on GitHub, Indico and Zenodo

• GitHub: stakeholders, risk registry, decision log, work items/schedule/roadmap, internal documentation
• Indico: Meetings (coordination board, early adopters, event coordination) and minutes
• Zenodo-community: Repository for public deliverables and outputs from the project.

Early adopters: Engagement plan

• Strategy for finding early adopter projects
• Parameters: Small projects, common metadata, FAIRness ready?...
• Quick overview document to present benefits of being an early adopter
• 3 or many?

---

• Extract list of potential projects from Zenodo

Collect early adopter feedback on D2.1 Branded-communities

• Feedback on D2.1

• Feedback on QA system deployments

• Feedback on PROD

• Stakeholders:

  • EC
  • Early adopters
  • BLR
  • InvenioRDM telecons

• Log all dissemination/exploitation activities (RDM telecons, BLR meetings etc) in activities project board.

Dissemination: Project launch (messaging, website, blog post, slides)

• Define initial messaging
• Website: Create a page on zenodo.org describing the HORIZON-ZEN project
• Blog post: Write a blog post about the project.
• Slides: Create 2-3 slides that can be used to disseminate the project (store in GitHub repository)

Partnerships: Reach out to FAIR projects (FAIR-IMPACT, FAIRCORE4EOSC, ...)

Branded EC Zenodo-community design (D2.1)

Tasks

Beta Give feedback

1. RFC: Initial UX of branded communities (mockups + text) #20
   +0
   
2. Scope release 1 #12
   +0
   

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.

Release 1 (MS3, Mar 24)

Project plan: Create initial project plan

ESOC Symposium 2023 preparations

• Lars/German going to ESOC Symposium 2023 in Madrid.
• Requested booth for HORIZON-ZEN

Tasks

Beta Give feedback

1. Brainstorm what to include in booth
2. Make posters for booth
3. Print posters

Data management plan (update 1 - M12)

Data management plan (update 2 - M18)

Sustainability plan (D5.4)

Prefill EOR-community with existing records

Tasks

Beta Give feedback

1. Create dataset of records matching curation policy
2. Automation: it should be possible to continueosly scout for records to include
3. Automatically add Open Research Europe platform publications to EOR-community
4. Quality assurance process for prefilling

Coordination board: Setup coordination board

• Define members
• Define mandate
• Define meeting schedule (and setup Indico)

RFC: Initial UX of branded communities (mockups + text)

• Collect user stories
• Create mockups
• Write RFC

Project handbook: monitoring/control, change management, quality procedures, risk mitigation, transitions

Release 4 (MS7, Dec 24)

Dissemination plan update M12

Release 3 (MS6, Sep 24)

KPIs: Record baseline KPIs

Coordination meeting: Prepare July meeting (26/7 at 09:30)

• Early adopters engagement plan
  • List of candidate projects
  • List of candidate names for the community
• Release 1 scope:
  • Branded-communities - design document (D2.1) - due 3 days later 🚨
  • Content and curation policy for the Zenodo communities - design document (D2.2) due date +2 months
• Deliverables:
  • Release and Deployment strategy (D4.1) - already delivered
  • Project plan and monitoring framework (D1.1) - already delivered
• EU-Login credentials

Deadline to send docs July 19th.

Report: Project plan and monitoring framework (D1.1 - Public)

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).

Release 5 (MS8, Mar 25)