Organisational Interoperability in Practice at Universidad Politécnica de Madrid

Oscar Corcho (with contributions from the members of the Open
Science community at Universidad Politécnica de Madrid)
Ontology Engineering Group
Universidad Politécnica de Madrid, Spain
Organisational Interoperability in Practice at
Universidad Politécnica de Madrid
Webinar ”Addressing Organisational Interoperability”
ocorcho
ocorcho@fi.upm.es Online
10/06/2021

Organisational Interoperability in Practice at Universidad Politécnica de Madrid
License
2
 This work is licensed under the license
CC BY-NC-SA 4.0 International
o http://purl.org/NET/rdflicense/cc-by-sa4.0
 You are free:
o to Share — to copy, distribute and transmit the work
o to Remix — to adapt the work
 Under the following conditions
o Attribution — You must attribute the work by inserting
• “[source Oscar Corcho]” at the footer of each reused slide
• a credits slide stating: “These slides are partially based on “Organisational
Interoperability in Practice at Universidad Politécnica de Madrid” by O. Corcho”
o Share-Alike
o Non-commercial

A summary from the previous presentation
3
 Organisational interoperability is a socio-technical challenge. There is a need for an
integrated approach that considers the technical and social architectures, including
formal and informal structures
 Use common vocabularies and provide clear specifications regarding processes,
services, data, skills and roles internally and externally to ensure coordination,
collaboration and alignment
 Avoid or limit organisational heterogeneity or differences in practices and processes -
this should start internally as departments and areas shouldn’t develop in isolation
from each other
 EOSC IF calls for clear guidelines for organisational interoperability through the Rules
of Participation and a governance structure that will deal with interoperability across
organisations and disciplines (regarding key interoperability
aspects such as data formats, AAI services, metadata
schemas, ontologies etc)
 Interoperability certification mechanisms
 Consider at all times the point of view of the researcher
- who should not face any conflicts in the steps and
processes they follow

Objectives of this talk
4
 Describe briefly the process that we followed towards generatig the
recommendations on Organisational Interoperability that appear in the
EOSC Interoperability Framework
 Discuss on the status of Open Science Adoption at Universidad
Politécnica de Madrid and how this poses challenges in terms of
Organisational Interoperability
 Describe our next steps as an institution towards adopting Open Science
practices

EOSC Working groups (2019-2020)
5
https://www.eoscsecretariat.eu/eosc-working-groups
Task forces:
- FAIR Practice
- Interoperability
- Metrics and certification
- PIDs

EOSC EB Timeline (for 2020)
6

EOSC Interoperability Framework in context
7

8
ISBN 978-92-76-28949-4 doi: 10.2777/620649
https://op.europa.eu/s/oZnu

EOSC IF is based on the European IF layers
9
The European Interoperability Framework four levels of interoperability
Policy
Governance
Frameworks
Services
Infrastructure providers
Rules of participation
Licenses
GDPR
Copyright
Interpretation of meaning
& structure
Metadata & Ontologies
Data protection
Organisational interoperability refers to the way in which organisations
align their business processes, responsibilities and expectations to achieve
commonly agreed and mutually beneficial goals (source: European
Interoperability Framework).

Table of Contents (II)
10

Organisational interoperability
11
 Focus on the documentation, integration or alignment of the processes of different
organisations providing services in EOSC, so as to ensure that researchers can reach
their Open Science goals.
 It should be clear who is responsible for providing (as well as developing,
maintaining and curating) common interoperability services like service catalogues,
registers and common PID services.
 Current impediments (from interviews)
o Additional work required to register their artefacts as Open Science-enabled ones and provide sufficient
metadata
o Lack of recognition for this additional work, both from institutions and colleagues
o Lack of commonly agreed principles across funding agencies and organisations with respect to the Open
Science approach
o …
Reflection: probably this text and recommendations are focused too much on
the macro-level (EOSC-wide) and on service providers
But we have to consider the practices and policies of Research Performing Organisations
and of their groups

12
practices

Open Scientific Data vs Open Government Data (I)
 Is Open Data in Science actually much different from Open Government Data?
o NO
• “freely used, re-used and redistributed by anyone - subject only, at most, to the
requirement to attribute and sharealike”
• Funders encourage the generation of open research data
- E.g., guidelines on FAIR Data Management H2020
http://ec.europa.eu/research/participants/data/ref/h2020/grants_manual/hi/oa_pilot/h
2020-hi-oa-data-mgt_en.pdf
o YES
• Not such a large history of legislation
- Initially, most work focused on open access (papers)
• Not only available for use and reuse, but also for reproducibility
• It is often not useful without the rest of research artefacts that come together with it
(methods, software, protocols, papers)

Open Scientific Data vs Open Government Data (II)
The same explosion of Data Portals
General-purpose Region-specific
Domain-specific (e.g. Astronomy) Institution-specific

Open Scientific Data vs Open Government Data (III)
 And a good number of alternative technologies
 And a good number of metadata schemas
o DataCite
o CrossRef
o CKAN Metadata
o DDI4
o DCAT
o …

Are we applying what we learned from Open Gov Data?
 Some of the same mistakes are being done
o Setting up a portal/infrastructure does not mean that you are better than others
o Having more objects in your repository does not mean that you are doing more or
better Open Science
o No clear instructions for researchers on what to upload or not, and how to
ensure quality (except for mature domains or organisations)
o No clear governance (handled by researchers?, handled by data centers?,
handled by libraries?)
 And a few more things
o No clear relationship among all research artefacts
o No clear relationship between the Data Management Plans and the way in which
data is finally handled

This is one of the results of this lack of governance (just in OpenAIRE)
17
 UPM
(https://explore.openaire.eu/search/organization?organiz
ationId=corda__h2020::7a44a773d0dc629e9af5cef563c2
478a)
 Polytechnic University of MAdrid, Espagne
ationId=anr_________::235a19cd464669ed9cedbb6106
e0a8c5)
 Universidad Polytecnica de Madrid
ationId=anr_________::da5d28c208ebeb6f70ffc7a0e00c
22c9)
 Centro de Biotecnología y Genómica de Plantas
(CBGP), Universidad Politecnica de Madrid (UPM),
Espagne
ationId=anr_________::d63d9e8d358160cb94082e8a99
be8782)
 Polytecnic University of Madrid / Industrial Engineering
and Logistics Research Group
ationId=anr_________::116767d0a90812905ce520a4a6
b046d1)
 Polytechnic University of Madrid UPM
ationId=rcuk________::3721cd9bb9e72b45214de6e0bdf
d353f)

Some key messages...
Open Science ≠ Open Access
Science is not only about papers (other objects exist)
Open Science = Open Access + Research Data Management + Research Object
Management
We need principled approaches and clear guidelines (community or
institution driven) to adopt an Open Science approach
We expect this (non-extra) work to pay off in the future

Open Science initiative at UPM (started in June 2020)
1. Strategic roadmap with actions and practical guides on the deployment of
an Open Science policy, based on an exhaustive analysis of UPM research
communities
2. Analysis of existing infrastructure (domain-specific and domain-neutral,
local/regional/national/international) to ease the storage, deposit and archival of
data and other research outputs. Including dashboards with indicators about
Open Science – ready products.
3. Dissemination and engagement events.
4. Training for junior and senior researchers, including PhD students (via the
International Doctoral School) and MSc students.
Involved researchers
Oscar Corcho (EOSC FAIR WG, Open software/data)
Mark Wilkinson (FAIR data)
Carlos del Cañizo (Responsible Research and Innovation)
Ana Laverón (ESA Scientific Data)
Raquel Cedazo (Citizen Science)
Alberto Brunete (Open hardware)
Open to other UPM members:
Library, Computing center, Open Science ambassadors
OBJECTIVES
Work together with UPM research communities so as to define
an Open Science policy that gathers all their needs and aligns
them to the international, national and regional infrastructures
AI and Robotics for Sustainability
Health Mobility
Digital Innovation Hubs
Collaboratory
Circular UPM Campuses
Emission-free UPM
UPM Water
UPM communities
Open Science

ANALYSIS
M6: Catalogue of
repositories and
systems currently
used at UPM
FIRST STRATEGIC
ROADMAP
M13: Ooen Science
educational materials
M12: Strategic Roadmap for
Open Science Adoption at
UPM (v1)
M15: Dashboards with
indicators on Open Science
adoption
CONSOLIDATION
M24: Practical guides for the
adopting Open Science
M24: Deployment of repositories
and systems at UPM, and
adaptation of existing ones
Year 1: 2020 Year 2: 2021 Year 3: 2022
FUTURE STRATEGY
M36: Strategic Roadmap for Open
Science adoption at UPM (v2)
Year 4: 2023

Where are we in terms of Open Science adoption?
• 56% of tasks have not started
• 24% are almost completed
Strong points:
• Repositories for publications and data
• Integration with OpenAire
• Compliance with the European Code for
Research Integrity (ALLEA)
Weak points:
• Training courses
• Open Science structure (with ambassadors
and staff)
• Rewards (HR policy and funding)
• Indicators
Source checklist: https://www.leru.org/files/LERU-AP24-Open-Science-full-paper.pdf

How do we do it at OEG-UPM?
 Which research artefacts do we handle at OEG-UPM?
o Papers (sure, let’s see the following talk by UPM’s library)
o Data Management Plans (DMPOnline –PaGoDa did not exist)
o Datasets
• Normally in GitHub, e.g. https://github.com/oeg-upm/btn100
o Software source code
• Normally in GitHub: http://www.github.com/oeg-upm
o Docker images, models and APIs
• Normally in DockerHub: https://hub.docker.com/u/oegupm/
o Ontologies, thesauri, etc.
• Normally in GitHub, e.g., https://github.com/CiudadesAbiertas/vocab-sector-publico-
agenda-municipal
• And published online, e.g., http://vocab.ciudadesabiertas.es/def/sector-publico/agenda-
municipal/
o …

And which are our (good) practices?
 Still missing many, but...
o When a research or experiment starts, a new GitHub repository is created
o The repository is connected to Zenodo, so as to get DOIs and ensure archival
• Automated archival process after every release
• DOIs also added to the GitHub repository
o Our papers cite those DOIs
• Bit.ly, dropbox, GDrive links, etc., are strictly prohibited in our papers
o We tweet about them: https://twitter.com/ocorcho/status/1106989518941548544
o Zenodo community
• https://zenodo.org/communities/ontologyengineeringgroup/

Things that we do (another perspective)
https://figshare.com/articles/NPOS_Workflow-perspective-Bosman-Kramer_pptx/5065534/1

25
practices

Actions
26
 Divide into short, medium and long term
o People
• Training material for the International Doctorate School (educational pills)
• A network of ambassadors at each community / school / department
o Organisation
• Guidelines for UPM presence in EOSC-related services
• Organisational push for the publication of other research products beyond
publications and data
• Dashboard
o Communication
• Push for Citizen Science projects
 This may lead into the creation of the Open Science office at UPM

Organisational Interoperability in Practice at Universidad Politécnica de Madrid

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Organisational Interoperability in Practice at Universidad Politécnica de Madrid

Similaire à Organisational Interoperability in Practice at Universidad Politécnica de Madrid (20)

Plus de Oscar Corcho

Plus de Oscar Corcho (20)

Dernier

Dernier (20)

Organisational Interoperability in Practice at Universidad Politécnica de Madrid