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
Other literature type . 2025
License: CC BY
Data sources: ZENODO
ZENODO
Project deliverable . 2025
License: CC BY
Data sources: Datacite
ZENODO
Project deliverable . 2025
License: CC BY
Data sources: Datacite
versions View all 2 versions
addClaim

D6.3 - MoU and SLA templates for data interoperability

Authors: LANDEL, Salomé; Kraaikamp, Emilie; Thorpe, Deborah Ellen; Ashley, Kevin; Davidson, Joy; Jasinska, Agnes; Boerman, Sandra; +2 Authors

D6.3 - MoU and SLA templates for data interoperability

Abstract

This deliverable, produced by Work Package 6 (interoperability) of the FAIR-IMPACT project, examines how MoUs and SLAs could promote data interoperability within the EOSC Federation. In the context of EOSC, data interoperability depends on all four interoperability dimensions: Legal, Organisational, Semantic and Technical. Research data repositories, as intermediaries between data producers (researchers) and data users, are identified in this deliverable as central to establishing and maintaining data interoperability as a service (section 3.1). SLAs and MoUs should be used as tools to enhance all levels of interoperability. An SLA is a written document that defines the expected level of service and outlines specific metrics, responsibilities and remedies to ensure accountability between service providers and users / customers. Conversely, an MoU is an agreement between parties that outlines their mutual intentions, roles and shared objectives, creating legally binding obligations (may be very limited effects) for parties. These agreements can enable more user-centred and efficient service and process development. Including data interoperability in relevant documents or if feasible writing separate documents would be important to take interoperability forward. While both types of agreements clearly enhance organisational interoperability by enabling stakeholders to align business processes towards common goals, there is currently a significant gap in accessing and harmonising all the guidelines to support interoperability in the legal, semantic and technical dimensions. Today, the evolving EOSC federation lacks a robust, community-endorsed framework for systematically describing and enforcing data interoperability, highlighting the need for such guidelines. Given this lack of compliance to common standards, the considerable diversity of service providers (with over 500 providers registered in the previous EOSC portal) and the EOSC's transition to a federation, the provision of standard templates for agreements is premature. A fundamental step before developing agreements is to assess the capacity of the organisations involved to inform the development of effective agreements. Rather than providing agreement templates, this deliverable proposes recommendations and guidelines to help service providers self-assess their capabilities and thus enable them to design agreements that are appropriate to their specific capabilities. The guidelines in the appendices support the development of SLAs and MoUs for data interoperability by providing structured recommendations that offer both a model for drafting agreements and the flexibility to adapt to different contexts.

Keywords

Memorandum of understanding, EOSC, data interoperability, Service level agreement, organisational interoperability

  • 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
Powered by OpenAIRE graph
Found an issue? Give us feedback
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!
0
Average
Average
Average
Green