Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Project deliverable . 2021
License: CC BY
Data sources: Datacite
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Other literature type . 2021
License: CC BY
Data sources: ZENODO
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Project deliverable . 2021
License: CC BY
Data sources: Datacite
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
https://doi.org/10.5281/zenodo...
Article . 2021
License: CC BY
Data sources: Sygma
versions View all 4 versions
addClaim

ELIXIR-CONVERGE D5.1 Categorisation of the pilot projects

Authors: Adam-Blondon, Anne-Françoise; Alper, Pinar; Capella-Gutierrez, Salvador; Faria, Daniel; Portell Silva, Laura; Hospital, Adam; Willassen, Nils-Peder;

ELIXIR-CONVERGE D5.1 Categorisation of the pilot projects

Abstract

Task 5.1 aims to analyse the different demonstrators in light of the process necessary to implement their DMPs and to propose a categorisation based on users’ needs. This effort will provide input to WP1 with respect to needs in terms of experts and resources across ELIXIR Nodes (Task 1.3, Business plans). It is expected that some of them will be generic whereas others will be very specific to projects, which is an important factor for establishing a strategy towards the sustainability of such a service in all its diversity. D5.1 therefore describes the needs in terms of DMP of the demonstrator use-cases and proposes a project categorisation from the point of view of: - Area of expertise - The resources they use / toolkit - Training needs The first challenge was to develop a method to describe the needs of the users and their current practices in terms of data management as a prerequisite to the development of an adequate toolkit. The method adopted with the guidance of WP2 and WP3 relied on the description of users stories, and scenarios for different types of personas. In addition, a table was also developed to collect knowledge on the current practices and existing resources in terms of data management with guidance from WP1 and WP3. The six demonstrator use-cases are divided into two waves to facilitate having a broad diversity of data types, potential users and variable expertise and, at the same time, have first mature demonstrator use-cases that can start providing input to other WPs in the projects. The Plant and the Marine Metagenomics demonstrator use-cases were used as testers for the method developed as they are the two selected ones for the first wave. Federated access to human genomics data belongs to the second wave of demonstrator use-cases. However, considering its broad reach, it has been partially developed for this deliverable. User stories and scenarios with personas were developed by WP5 partners on the Plant, Marine metagenomics and Federated access to human genomics data: GDPR use-cases. The table on existing tools and resources was also filled in by WP5 partners and target interviews of researchers for some of the demonstrator use-cases. Additional input was sought from the ELIXIR communities for the demonstrator use-cases mentioned before. This method implemented to describe the demonstrator use-cases in detail has been efficient to isolate the specific context of each case, and to identify specific tools/resources in relation with the use-cases that can be used for data management. The main aspect used to classify a new use-case is the type of biological material linked to the data that links to many specific requirements, e.g. legal and scientific metadata. The second is the relation of the personas with the data, e.g. consumers/producers, and the type of data, including workflows, models, and the various types of experimental data. The landscape analysis of the resources already available in relation with the demonstrator use-cases and the different stages of a data management plan, showed that the guidelines developed by WP1 are very useful to clarify the scope of these stages before filling such a survey. The personas/users related to the use-cases are very diverse but always include the researchers in various positions, e.g. data consumer, data producer, data owner, PI writing a proposal, and the data curators. This will be further developed in collaboration with WP2. Finally, the work achieved to deliver D5.1 facilitated the development of pages dedicated to the “domains” in the RDMKit website (https://rdmkit.elixir-europe.org/) for demonstrator use-case 1, 3, 4 and 6. In these pages, specific challenges linked with the demonstrator use-cases are highlighted, and dedicated resources to solve them are listed. These tools have also been flagged in bio.tools with the domain name.

Keywords

RDMKit, DMP Use Cases, Data Management Plan, CONVERGE, DMP, Demonstrators, ELIXIR

  • BIP!
    Impact byBIP!
    selected citations
    These citations are derived from selected sources.
    This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    0
    popularity
    This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
    Average
    influence
    This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    Average
    impulse
    This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
    Average
    OpenAIRE UsageCounts
    Usage byUsageCounts
    visibility views 9
    download downloads 6
  • 9
    views
    6
    downloads
    Powered byOpenAIRE UsageCounts
Powered by OpenAIRE graph
Found an issue? Give us feedback
visibility
download
selected citations
These citations are derived from selected sources.
This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Citations provided by BIP!
popularity
This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
BIP!Popularity provided by BIP!
influence
This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Influence provided by BIP!
impulse
This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
BIP!Impulse provided by BIP!
views
OpenAIRE UsageCountsViews provided by UsageCounts
downloads
OpenAIRE UsageCountsDownloads provided by UsageCounts
0
Average
Average
Average
9
6
Green