mih-talks/decentralized-consortium-rdm-concept
1
0
Fork 0
Code Pull requests Packages Activity
decentralized-consortium-rd.../index.html
Michael Hanke 19c65ce289
 Final tweaks
2025-02-13 11:11:27 +01:00

400 lines
14 KiB
HTML
Raw Permalink Blame History

<!doctype html>
<html lang="en">
<head>
<title>TRR379 information management</title>
<meta name="description" content="Talk at the 2025 TRR379 retreat">
<meta name="author" content="Michael Hanke">
<meta charset="utf-8">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="common/css/main.css" id="theme">
<script src="common/js/printpdf.js"></script>
</head>
<body>
<div class="reveal">
<div class="slides">
<section>
<h1>TRR379<br><small>Information management approach</small></h1>
<p style="margin-top:-50px">Michael Hanke (Q02)</p>
<p>
<small>Institute of Neuroscience and Medicine, Brain &amp; Behavior (INM-7),
Research Center Jülich</small><br>
<small>Institute of Systems Neuroscience, Medical Faculty, Heinrich Heine University Düsseldorf</small></br>
<p><img style="height:50px;margin-bottom:-12px;margin-right:10px" data-src="common/img/mastodon.svg" />@mih@mas.to &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a href="http://psychoinformatics.de">http://psychoinformatics.de</a></p>
<p style="margin-top:50px"><img style="height:100px;margin-right:100px" data-src="common/img/fzj_logo.svg" />
<img style="height:100px" data-src="common/img/hhu_logo.svg" /></p>
<a href="https://creativecommons.org/licenses/by/4.0">
<img data-src="img/cc-by.svg" />
</a>
</section>
<section data-markdown data-transition="none"><script type="text/template">
## Q02 team
<div style="float:left;margin-left:160px">
<strong>Aachen<br>&nbsp;</strong>
![Klaus](img/mathiak.webp)<br>Klaus Mathiak
![Arezoo](img/taebi.webp)<br>Arezoo Taebi
</div>
<div style="float:left">
<strong>Frankfurt<br>&nbsp;</strong>
![Christine](img/ecker.webp)<br>Christine Ecker
![Wiebke](img/hennig.webp)<br>Wiebke Hennig
</div>
<div style="float:left">
<strong>Mannheim<br>Heidelberg</strong>
![Gabi](img/ende.webp)<br>Gabi Ende
![Richard](img/nkrumah.webp)<br>Richard Nkrumah
</div>
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Special thanks!
<video data-autoplay width="1280" height="720" controls loop>
<source src="vid/special_thanks.webm" type="video/webm">
</video>
</script></section>
<section>
<section data-markdown data-transition="none"><script type="text/template">
# Talk is cheap.<br > This is what we have<br>- right now -
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Things to keep in mind
- **Focus is on tools, not online services**.
Every component can be self-hosted by TRR379, at an institution, a lab, or by an individual person.
- **Everything is free and open-source software**.
No contract, no license cost, no proprietary formats, or processes.
- **Everything is incomplete,
but set up for 10+ years of research** and the anticipated changes of
infrastructure, processes, and demands.
- **It's an ecosytem**.
All components interoperable, and connect across institutional boundaries
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Main website: [www.trr379.de](https://www.trr379.de)
![Website screenshot](img/main_website.webp)
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Main website: a key RDM component/output
![Website screenshots and sources](img/website.svg)
<div style="font-size:70%;float:right;margin-top:-735px;margin-right:40px">
<ul>
<li>Version-controlled metadata records</li>
<li>Media files under distributed data management</li>
</ul>
</div>
<div style="float:left;margin-top:-190px">
<small>
<p style="margin-left:-30px;padding-left:0px">Central TRR379 namespace</p>
<ul>
<li>https://trr379.de/contributors/</li>
<li>https://trr379.de/projects/</li>
<li>https://trr379.de/roles/</li>
<li>https://trr379.de/sites/</li>
<li>https://trr379.de/topics/</li>
<li>...</li>
</ul>
</div>
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Cohort data discovery [nb-query.trr379.de](https://nb-query.trr379.de)
<video data-autoplay width="1280" height="720" controls loop>
<source src="vid/bagel_query.webm" type="video/webm">
</video>
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Data access after discovery
![NeuroBagel query](img/neurobagel_query.webp)
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Where is the information coming from?
- Connect metadata infrastructure to existing/enforced administrative processes
- **Make what has to be done easier,**
then use this information for additional purposes to boost return of investment.
- **Example 1: DFG-required personnel census.** Gather `Person` records (with status info,
and project associations) to generate the report. Afterwards, confirmed valid
`Person` records are available for role associations with publications, and datasets.
Website updates for contributor pages can be auto-generated.
- **Example 2: DFG-required productivity report.** Gather `Publication` and `Dataset`
records to generate the report. Afterward, confirmed valid records can be used to
auto-generate a data catalog, project-wise publication lists, and inform dataset
discovery system.
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Machine-driven metadata reporting
![Screenshots](img/machine_driven_metadata.svg)<!-- .element: style="height:650px;margin-bottom:-30px" -->
Formal "open-world" model, query and validated submission<br>
RDF-compatible *and* simultaneously scripting-ready<br>
[concepts.trr379.de](https://concepts.trr379.de) &nbsp;&nbsp;&nbsp; [metadata.trr379.de/docs](https://metadata.trr379.de/docs)
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Manual annotation and description
<video data-autoplay width="1280" height="720" controls loop>
<source src="vid/annotate_demo.webm" type="video/webm">
</video>
Preview the live editor: https://annotate.trr379.de/s/demo
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Key take-aways
- **manual labor is limited** to information that does not yet exist as structured metadata
- manual metadata actions are mainly about **linking existing information** in a particular context<br>
(e.g. stimulation protocol used for an fMRI acquisition)
- **persistent identifiers** are essential
- metadata system becomes **single point of truth**
**Tedious tasks become automated** (e.g., Person info updates on website)
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Central collaboration site: [hub.trr379.de](https://hub.trr379.de)
<video data-autoplay width="1280" height="720" controls loop>
<source src="vid/hub.webm" type="video/webm">
</video>
TRR379-global node of a network of (envisioned) sister sites.
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## But GitLab?
Advantages over GitLab:<!-- .element: style="float:left" -->
- Easily self-hostable, even for a small lab (Raspberry Pi is enough)
- Hosts extremely large datasets (https://atris.fz-juelich.de hosts data in the PB range)
- Developed by a German Non-Profit (e.V.) with guaranteed software freedom
- Extremely customizable for our purposes (MR data viewer integration, BIDS dataset compatibility, etc.)
- Full DataLad compatibility
</script></section>
</section>
<section>
<section data-markdown data-transition="none"><script type="text/template">
# Our approach
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Independent, mutually interested actors
![Venn diagram](img/mutual_interest.svg)<!-- .element: style="height:400px" -->
<div style="float:left;max-width:50%">
<ul>
<li>maximum contributor benefit</li>
<li>self-hostable, independently governed solutions</li>
</ul>
</div>
<div style="float:left;max-width:50%">
<ul>
<li>minimum contributor cost</li>
<li>self-contained contributor scopes, not inheriting complexity of others</li>
</ul>
</div>
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Preserve existing work/data flows
![Established infrastructure](img/established_infrastructure.svg)
every contributor already has a functional research environment
Notes:
This includes the compliance with DFG requirements like data safety and preservation mandates
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Extend with TRR379 *metadata* infrastructure
![Enhanced infrastructure](img/enhanced_infrastructure.svg)
contributors are free to use central services or self-deploy
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Connect to established workflows
![Enhanced infrastructure](img/enhanced_infrastructure_interaction.svg)
provide contributor-specific connectors where needed
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## A network of collaborators
![Consortium RDM setup](img/mutual_interest.svg)
Notes:
- scale-free organization
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Indiosyncratic setup at each site...
![Enhanced infrastructure](img/enhanced_infrastructure_interaction.svg)
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## ...but standardized *metadata* interface
![Enhanced infrastructure](img/collaborating_site_zoomed_out.svg)
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## A network of *interoperable* collaborators
![Consortium RDM setup](img/consortium_rdm_setup.svg)
scale-free organization: consortium, institution, lab, researcher
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Wider interoperability via standards adherence
![Wider RDM setup](img/wider_rdm_setup.svg)
possibility to reuse, and connect to larger or different networks
</script></section>
</section>
<section>
<section data-markdown data-transition="none"><script type="text/template">
# Where we are going?
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Conversations with projects and sites
We are ready to talk about:<!-- .element: style="float:left" -->
- Identifier schemes (done for Q1)
- Connecting acquisition workflows
- (Meta)data ingestion pipelines
- Infrastructure hosting at individual sites, and their federation
**Please approach us!**<!-- .element: style="font-size:120%" -->
Notes:
DataLad office our (Tue 16:00)
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Study management / DMP monitoring
- **electronic case reporting form (eCRF) solution** funded and under development (target for initial release end of 2026/Q1)
- **built on the metadata approach used for TRR379**
- graphical environment for study management and data management plan monitoring
- **interoperable with all presented solutions** (incl. DataLad and JTrack)
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Automated data catalogs
![SFB1451 catalog](img/SFB1451_catalog_screenshot.png)<!-- .element: style="width:49%" -->
![NN catalog](img/naturalistic_imaging_catalog.webp)<!-- .element: style="width:49%" -->
for global findability, populated from existing metadata
</script></section>
<section data-markdown data-transition="none"><script type="text/template">
## Remote/distributed data processing
![Remote analysis](img/remote_analysis.svg)
minimize risk related to personal data processing, simplify legal setup
</script></section>
</section>
<section data-markdown data-transition="none"><script type="text/template">
# Follow us on...
https://docs.trr379.de<!-- .element: style="font-size:200%" -->
</script></section>
</div> <!-- /.slides -->
</div> <!-- /.reveal -->
<script src="common/reveal.js/js/reveal.js"></script>
<script>
// Full list of configuration options available at:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
// The "normal" size of the presentation, aspect ratio will be preserved
// when the presentation is scaled to fit different resolutions. Can be
// specified using percentage units.
width: 1280,
height: 960,
// Factor of the display size that should remain empty around the content
margin: 0.1,
// Bounds for smallest/largest possible scale to apply to content
minScale: 0.2,
maxScale: 1.0,
controls: true,
progress: true,
history: true,
center: true,
transition: 'slide', // none/fade/slide/convex/concave/zoom
// Optional reveal.js plugins
dependencies: [
{ src: 'common/reveal.js/plugin/highlight/highlight.js', async: true, condition: function() { return !!document.querySelector( 'pre code' ); }, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'common/reveal.js/plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'common/reveal.js/plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'common/reveal.js/plugin/zoom-js/zoom.js', async: true },
{ src: 'common/reveal.js/plugin/notes/notes.js', async: true }
]
});
</script>
</body>
</html>
View git blame Copy permalink