From 7ae5e476e29ee93009529c16be6c21df1cc9d098 Mon Sep 17 00:00:00 2001 From: leej3 Date: Wed, 9 Sep 2026 11:12:19 -0400 Subject: [PATCH 01/15] docs: add editable Orinoco Lite poster for US-RSE 2026 Place the vector poster beside its submitted abstract and document editing, PDF export, and the scope of its development-site results. Keep the SVG in ordinary Git so reviewers can inspect the editable source directly. Co-Authored-By: Codex Desktop 26.901.51231 (runtime codex-cli 0.153.4) / gpt-6-astra Codex-Reasoning-Effort: ultra --- .gitattributes | 2 + 2026-usrse/README.md | 4 +- 2026-usrse/orinoco-lite-poster.svg | 681 +++++++++++++++++++++++++++++ 2026-usrse/poster-notes.md | 52 +++ 4 files changed, 738 insertions(+), 1 deletion(-) create mode 100644 2026-usrse/orinoco-lite-poster.svg create mode 100644 2026-usrse/poster-notes.md diff --git a/.gitattributes b/.gitattributes index e539c858..6f84c9e2 100644 --- a/.gitattributes +++ b/.gitattributes @@ -2,3 +2,5 @@ **/.git* annex.largefiles=nothing * annex.largefiles=((mimeencoding=binary)and(largerthan=0)) *.svg annex.largefiles=(largerthan=100K) +# Keep the editable poster source available directly in Git. +2026-usrse/orinoco-lite-poster.svg annex.largefiles=nothing diff --git a/2026-usrse/README.md b/2026-usrse/README.md index 0e926749..1670d3e3 100644 --- a/2026-usrse/README.md +++ b/2026-usrse/README.md @@ -1,5 +1,8 @@ This is folder to collect ideas/drafts for submissions for https://us-rse.org/usrse26/ as described on https://us-rse.org/usrse26/participate/ . +The Orinoco Lite poster is available as an [editable SVG](orinoco-lite-poster.svg), with [editing and export notes](poster-notes.md). +Its [submitted abstract](orinoco-lite-poster-draft.md) remains alongside it. + ### Meeting theme etc That meeting is about/for Software Research Engineers. And this particular meeting has following @@ -46,4 +49,3 @@ scientific fields. So, it would be great to alert audience to our efforts and efforts of our collaborators (like https://www.distribits.live/ conference etc). - diff --git a/2026-usrse/orinoco-lite-poster.svg b/2026-usrse/orinoco-lite-poster.svg new file mode 100644 index 00000000..1c8ea26d --- /dev/null +++ b/2026-usrse/orinoco-lite-poster.svg @@ -0,0 +1,681 @@ + + + Beyond the Lab Website: Reusing Structured Research Metadata Across Lab Operations + Editable draft for US-RSE 2026. Two operating models for curated research information, a GitHub curation flow, measured development-site results and next evaluation steps. Snapshot 9 September 2026. Authors: John Lee, Isaac To and Yaroslav O. Halchenko. + + + + + + + ORINOCO LITE / US-RSE 2026 + + + Beyond the Lab Website + + + Reusing structured research metadata across lab operations + + + John Lee • Isaac To • Yaroslav O. Halchenko + + + Center for Open Neuroscience | Psychological and Brain Sciences | Dartmouth College + + + + + + + + + + + + + + + + C + + + + + + + + + + + + + + + + + + Center for Open Neuroscience + + + + + + + + 19-21 October 2026 + + + San Jose, California + + + + + + Curate the records once. + + + Make the website one reusable view. + + + + A working development deployment + + + CON is testing the GitHub adaptation. + Production migration remains in progress. + + + + + 01 + + + Same research information. Different operating models. + + + + + + + ORINOCO + + + Psychoinformatics deployment [1] + + + ORINOCO LITE + + + CON development deployment [2] + + + RECORDS + + + Curated collection exposed by a metadata service + + + RECORDS + + + Reviewed YAML records in a GitHub repository + + + REVIEW + + + Submissions enter a service inbox for curation + + + REVIEW + + + Pull requests provide the review surface for proposed changes + + + OPERATIONS + + + Maintain metadata services and their storage + + + OPERATIONS + + + Run GitHub Actions, static hosting and an editing App + + + + www.psychoinformatics.de + + + + + dev.centerforopenneuroscience.org + + + + + + + ORINOCO components + + + Schemas, validation, graph processing and presentation + + + are selected by + + + Orinoco Lite package and template + + + supply + + + the downstream build + + + + + 02 + + + The GitHub curation design + + + CON workflow integration remains in progress [2, 3] + + + + Pull requests + + + Edits and source proposals + + + + YAML records + + + Accepted metadata in Git + + + + GitHub Actions + + + Validation and composition + + + + Knowledge graph + + + Connected records + + + + Static website + + + Pages and graph explorer + + + + + update + on merge + + + + + are read + by + + + + + generates + + + + + is projected + into + + + People review and merge proposed metadata changes. + + + The static /edit/ and /review/ pages use a stateless GitHub App for signed-in operations. + + + Public reading and website builds do not require the curation service. + + + + could support + + + + NEXT: REUSE THE GRAPH FOR REPORTS + + + A CON reporting workflow remains to be demonstrated. + + + + + + 03 What works today + + + What we learned + + + What to evaluate next + + + 224 + + + 193 + + + canonical records + + + generated pages + + + Fresh validation and the latest GitHub Pages + deployment passed. [2] + + + Development-site snapshot: 9 September 2026 + + + + AI can propose. People curate. + + + Validation constrains structure; people still decide identity, attribution + and meaning. + + + A static website reduces service coupling. Online edits still need + secure authentication and careful authorization. + + + + Demonstrate a second use of the records. + + + Measure editing effort, correction rates and successful upgrades with + real curators. + + + Complete the CON curation workflow, App hardening and a reversible + production cutover. + + + + + + [1] hub.psychoinformatics.de/orinoco [2] github.com/con/dev-centerforopenneuroscience.org + + + [3] github.com/ORINOCO-Lite/orinoco-lite-dev • Project design and released implementation + + + Thanks to Michael Hanke, Stephan Heunis, DataLad Concepts and ORINOCO contributors, and the CON team. + + + Draft text, diagram and layout assisted by OpenAI Codex; author review pending. | CC BY-SA 4.0 + + + ... + ... + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Explore + the code + + + \ No newline at end of file diff --git a/2026-usrse/poster-notes.md b/2026-usrse/poster-notes.md new file mode 100644 index 00000000..901f810e --- /dev/null +++ b/2026-usrse/poster-notes.md @@ -0,0 +1,52 @@ +# Orinoco Lite poster + +The editable source is [orinoco-lite-poster.svg](orinoco-lite-poster.svg). +It preserves the title and presenter order of the [submitted abstract](orinoco-lite-poster-draft.md). +The draft leads with the deployment comparison requested by the reviewers, followed by the GitHub curation design, observed results and next evaluation steps. + +## Editing and export + +Open the SVG in Inkscape or another SVG editor. +The title, comparison, diagram, results and footer have named layers. +Text remains editable text, and the CON logo and QR code are embedded vectors with no linked image dependencies. +The SVG is kept in ordinary Git so GitHub reviewers and a fresh clone can read the complete source without fetching Annex content. + +Use the text tool to revise text and adjust its line breaks. +The font is Arial with Helvetica and generic sans-serif fallbacks; check the layout after font substitution or substantial text changes. +The provisional canvas is **48 inches wide by 36 inches high**. +This is a draft choice, not a verified conference mounting requirement; confirm the accepted-presenter instructions before printing. + +Export a PDF in the editor, or run from this directory: + +```bash +rsvg-convert --format pdf --output orinoco-lite-poster.pdf \ + orinoco-lite-poster.svg +``` + +The PDF is a generated preview and follows this directory's existing PDF ignore rule. +The initial export was checked as one 48-by-36-inch page with searchable text and visually inspected for layout. +The QR code points to the public Orinoco Lite development repository. + +## Results and claim boundaries + +The approximately 390-word poster describes a development case study, using a **9 September 2026** snapshot: + +- The CON downstream at [commit `ee2e568`](https://github.com/con/dev-centerforopenneuroscience.org/commit/ee2e56839f5b3e0ffb42437a3918387b95ed2d75) selects package `0.3.0rc5` and template `v0.3.0rc3`. +- Fresh frozen validation/build checks reported **224 canonical records** and **193 projected pages**. + These are counts of different artifacts, not a conversion ratio or a usability result. +- Its [validation](https://github.com/con/dev-centerforopenneuroscience.org/actions/runs/34319183393) and [Pages deployment](https://github.com/con/dev-centerforopenneuroscience.org/actions/runs/34319183434) succeeded. +- The operating comparison follows the [ORINOCO components](https://hub.psychoinformatics.de/orinoco), [metadata service](https://hub.psychoinformatics.de/orinoco/dump-things-service), and [Orinoco Lite design charter](https://github.com/ORINOCO-Lite/orinoco-lite-dev/blob/9417f90cb8989555cf71f41d9f982970c8402828/docs/project-design.md). + +The curation diagram describes the intended integrated workflow. +At the snapshot, CON's automated source-import/review workflow was not yet wired into the default branch, and complete authenticated curation had not been exercised in this review. +The poster marks CON integration and App hardening as ongoing work. +It does not assert enforced GitHub branch protections or a completed security assessment of the private deployment configuration. + +Broader reuse is explicitly future work: the review did not demonstrate a CON report/CV workflow or measure editing time, error reduction, maintenance cost or independent adoption. +Before finalizing the poster, update the snapshot if the release or dataset changes and review the text, acknowledgments and physical dimensions. + +## Attribution + +The embedded CON logo comes from [the existing vector artwork](../pics/con-logo_blue_big.svg). +The poster follows the talks repository's CC BY-SA 4.0 license and acknowledges the ORINOCO and DataLad contributors named in the abstract. +The footer discloses OpenAI Codex assistance with draft text, diagram and layout and retains the draft's author-review status. From 44659269102f89eefe25c8fc118ec02d2d1a914f Mon Sep 17 00:00:00 2001 From: leej3 Date: Tue, 13 Oct 2026 02:52:38 -0400 Subject: [PATCH 02/15] docs: revise US-RSE poster as editable HTML Replace the SVG source with an HTML/CSS poster and exact-size PDF export. Show both deployment workflows, authentic UI screenshots, upstream artwork, and the TRR379 reporting example. Cite the four tagged CON components. Co-Authored-By: Codex Desktop 26.1007.30912 (runtime codex-cli 0.162.0-alpha.17.2) / gpt-6-astra Codex-Reasoning-Effort: ultra --- .gitattributes | 2 - .pre-commit-config.yaml | 2 +- 2026-usrse/Makefile | 9 +- 2026-usrse/README.md | 2 +- 2026-usrse/build-orinoco-poster.py | 63 ++ 2026-usrse/orinoco-lite-poster.html | 227 ++++++ 2026-usrse/orinoco-lite-poster.svg | 681 ------------------ 2026-usrse/poster-notes.md | 124 +++- INDEX.md | 7 + REUSE.toml | 13 + pics/borrowed/orinoco-con-editor-20261013.png | 1 + pics/borrowed/orinoco-con-graph-20261013.png | 1 + pics/borrowed/orinoco-con-home-20261013.png | 1 + .../orinoco-psychoinformatics-20261013.png | 1 + .../orinoco-selfhost-components-poster.svg | 1 + .../orinoco-trr379-survey-20261013.png | 1 + pics/orinoco-qr-con.svg | 2 + pics/orinoco-qr-lite.svg | 2 + pics/orinoco-qr-upstream.svg | 2 + pics/orinoco-qr-video.svg | 2 + 20 files changed, 422 insertions(+), 722 deletions(-) create mode 100644 2026-usrse/build-orinoco-poster.py create mode 100644 2026-usrse/orinoco-lite-poster.html delete mode 100644 2026-usrse/orinoco-lite-poster.svg create mode 120000 pics/borrowed/orinoco-con-editor-20261013.png create mode 120000 pics/borrowed/orinoco-con-graph-20261013.png create mode 120000 pics/borrowed/orinoco-con-home-20261013.png create mode 120000 pics/borrowed/orinoco-psychoinformatics-20261013.png create mode 120000 pics/borrowed/orinoco-selfhost-components-poster.svg create mode 120000 pics/borrowed/orinoco-trr379-survey-20261013.png create mode 100644 pics/orinoco-qr-con.svg create mode 100644 pics/orinoco-qr-lite.svg create mode 100644 pics/orinoco-qr-upstream.svg create mode 100644 pics/orinoco-qr-video.svg diff --git a/.gitattributes b/.gitattributes index 6f84c9e2..e539c858 100644 --- a/.gitattributes +++ b/.gitattributes @@ -2,5 +2,3 @@ **/.git* annex.largefiles=nothing * annex.largefiles=((mimeencoding=binary)and(largerthan=0)) *.svg annex.largefiles=(largerthan=100K) -# Keep the editable poster source available directly in Git. -2026-usrse/orinoco-lite-poster.svg annex.largefiles=nothing diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index 0b40b2df..efd0e06a 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -7,4 +7,4 @@ repos: rev: v0.9.1 hooks: - id: snapper - files: ^2026-usrse/stamped-abcd-poster-draft\.md$ + files: ^2026-usrse/(stamped-abcd-poster-draft|poster-notes)\.md$ diff --git a/2026-usrse/Makefile b/2026-usrse/Makefile index c03928c4..c3714d63 100644 --- a/2026-usrse/Makefile +++ b/2026-usrse/Makefile @@ -12,6 +12,7 @@ # make pdf -- builds .pdf for every *.md (needs a PDF engine) # make html -- explicit alias for the default # make diagram -- rebuilds the Orinoco metadata-flow figure +# make poster -- prints the editable Orinoco poster HTML to PDF # make proposal -- just 2026-usrse-con-talk-abstract.html + 2026-usrse-con-talk-abstract.pdf # make clean -- remove generated *.html / *.pdf # @@ -77,7 +78,7 @@ stamped-abcd-poster-draft.pdf: PDF_LATEX_OPTS := $(subst fontsize=11pt,fontsize= # PDF via HTML (wkhtmltopdf / weasyprint) — same look as the HTML render PDF_HTML_OPTS := --to html5 --css=https://cdn.jsdelivr.net/npm/water.css@2/out/water.css -.PHONY: all html pdf diagram proposal clean help check +.PHONY: all html pdf diagram proposal poster clean help check all: pdf @@ -87,6 +88,12 @@ pdf: $(PDFS) diagram: orinoco-metadata-flow.png +# Browser setup: uv run --with playwright playwright install chromium +# Or use POSTER_BROWSER_ARGS='--channel chrome' for installed Google Chrome. +POSTER_BROWSER_ARGS ?= +poster: + uv run --with playwright python build-orinoco-poster.py $(POSTER_BROWSER_ARGS) + proposal: 2026-usrse-con-talk-abstract.html 2026-usrse-con-talk-abstract.pdf orinoco-metadata-flow.png: orinoco-metadata-flow.mmd diff --git a/2026-usrse/README.md b/2026-usrse/README.md index 1670d3e3..01313152 100644 --- a/2026-usrse/README.md +++ b/2026-usrse/README.md @@ -1,6 +1,6 @@ This is folder to collect ideas/drafts for submissions for https://us-rse.org/usrse26/ as described on https://us-rse.org/usrse26/participate/ . -The Orinoco Lite poster is available as an [editable SVG](orinoco-lite-poster.svg), with [editing and export notes](poster-notes.md). +The Orinoco Lite poster is available as [editable HTML](orinoco-lite-poster.html), with [editing, PDF export and release notes](poster-notes.md). Its [submitted abstract](orinoco-lite-poster-draft.md) remains alongside it. ### Meeting theme etc diff --git a/2026-usrse/build-orinoco-poster.py b/2026-usrse/build-orinoco-poster.py new file mode 100644 index 00000000..77987696 --- /dev/null +++ b/2026-usrse/build-orinoco-poster.py @@ -0,0 +1,63 @@ +#!/usr/bin/env python3 +# SPDX-FileCopyrightText: 2026 Center for Open Neuroscience +# SPDX-License-Identifier: Apache-2.0 +"""Print the editable HTML poster to PDF and optionally save a screen preview. + +From the repository root: + uv run --with playwright playwright install chromium # once + uv run --with playwright python 2026-usrse/build-orinoco-poster.py + +Use --channel chrome to use an installed Google Chrome instead. +""" + +from __future__ import annotations + +import argparse +import asyncio +from pathlib import Path + +from playwright.async_api import async_playwright + + +async def build(channel: str | None, preview: Path | None) -> None: + source = Path(__file__).with_name("orinoco-lite-poster.html") + output = source.with_suffix(".pdf") + async with async_playwright() as playwright: + browser = await playwright.chromium.launch(channel=channel) + page = await browser.new_page(viewport={"width": 1640, "height": 1300}) + await page.goto(source.as_uri(), wait_until="networkidle") + await page.evaluate("document.fonts.ready") + problems = await page.evaluate("""() => { + const issues = []; + for (const img of document.images) { + if (!img.complete || !img.naturalWidth) issues.push(`Missing image: ${img.getAttribute('src')}`); + } + for (const el of document.querySelectorAll('.poster, .column, .masthead, .footer')) { + if (el.scrollHeight > el.clientHeight + 2 || el.scrollWidth > el.clientWidth + 2) + issues.push(`Overflow: ${el.className}`); + } + if (document.querySelectorAll('h1').length !== 1) issues.push('Expected one poster title'); + return issues; + }""") + if preview: + await page.locator(".poster").screenshot(path=str(preview)) + if problems: + await browser.close() + raise RuntimeError("\n".join(problems)) + await page.pdf( + path=str(output), + print_background=True, + prefer_css_page_size=True, + display_header_footer=False, + margin={"top": "0", "right": "0", "bottom": "0", "left": "0"}, + ) + await browser.close() + print(f"Created {output} ({output.stat().st_size / 1e6:.2f} MB)") + + +if __name__ == "__main__": + parser = argparse.ArgumentParser(description=__doc__) + parser.add_argument("--channel", help="Browser channel, e.g. chrome; default: Playwright Chromium") + parser.add_argument("--preview", type=Path, help="Optional PNG preview path") + args = parser.parse_args() + asyncio.run(build(args.channel, args.preview)) diff --git a/2026-usrse/orinoco-lite-poster.html b/2026-usrse/orinoco-lite-poster.html new file mode 100644 index 00000000..b2baa414 --- /dev/null +++ b/2026-usrse/orinoco-lite-poster.html @@ -0,0 +1,227 @@ + + + + + + Beyond the Lab Website: Reusing Structured Research Metadata Across Lab Operations + + + + + +
+
+
+
+

ORINOCO / ORINOCO Lite · US-RSE 2026

+

Beyond the Lab WebsiteReusing Structured Research Metadata
Across Lab Operations

+
+ +
+

John Lee · Isaac To
Yaroslav O. Halchenko

+

Center for Open Neuroscience
Psychological and Brain Sciences
Dartmouth College

+
+
+ +
+

We compare two ways to deploy ORINOCO, a system for collaboratively managing and reusing structured research metadata.

+

Dedicated services or GitHub pull requests: curate people, projects and publications together, then reuse their relationships across lab operations.

+
+ +
+
+

Deployment 1 · Dedicated services

+

ORINOCO

+

Developed by Michael Hanke and colleagues in the Psychoinformatics group, INM-7, Forschungszentrum Jülich. Shared LinkML schemas connect records and drive forms and validation.

+
+ Contributorssubmit records + Service inboxcurators review + Collectionquery and reuse +
+
+
ORINOCO's own diagram: a schema connects SHACL Vue forms, Forgejo curation and the Dump Things service to catalogs, websites and reports.
+
ORINOCO’s metadata-curation components. A common model connects editing, review and reuse. + Artwork: Stephan Heunis (2026), CC BY 4.0. Text outlined for display. Source. +
+
+
+
The Psychoinformatics group homepage, showing its research-group website produced from linked metadata.
+
A website built from linked records.
psychoinformatics.de
+
+ +
+ +
+

Deployment 2 · GitHub collaboration

+

ORINOCO Lite at CON

+

We retain ORINOCO’s schemas and processing tools, adapting their operation to YAML records in Git, pull-request review and automated website builds.

+
+ Pull requestspeople review + YAML in Gitmerge records + Actionsvalidate + build +
+
+
SHACL Vue's Project form displaying the identifier, title and description of CON's DataLad project record.
+
Shared, schema-driven forms. SHACL Vue edits a CON project record. A GitHub App connects signed-in edits to pull requests.
+
+
+
The CON development homepage, displaying the center's open-science mission and principles with research-information navigation.
+
CON’s development website.
dev.centerforopenneuroscience.org
+
+ +
+ +
+

One collection · Multiple uses

+

Follow the relationships

+

Shared identifiers link people to projects and research outputs. The same structured information supports discovery, public communication and reporting.

+
+
CON's graph explorer connects people, projects, publications, organizations, datasets and topics; DataLad, DANDI and CON are visible.
+
Explore the CON knowledge graph. Relationships also drive related-item lists and links between website pages.
+
+

Beyond the website: a funder report

+

TRR379 already uses this approach for its DFG annual survey. Its central metadata infrastructure gathers personnel information and generates the funder’s census PDF.

+
+
TRR379's public article announcing its DFG annual survey and describing generation of the personnel-census PDF.
+
TRR379’s DFG survey deployment · An upstream example of reusing metadata for a second output.
+
+ +
+
+ +
+
+

Reproducible CON snapshot · 13 October 2026
+ Tag usrse-2026-10-13 in + package · + template · + CON content · + website. + Exact revisions and image sources accompany the editable poster.

+

Thanks to Michael Hanke, Stephan Heunis, the ORINOCO and DataLad contributors, and the CON team.
+ OpenAI Codex assisted with source review, text, diagrams and layout. Poster: CC BY-SA 4.0; third-party artwork and screenshots retain their respective notices.

+
+ +
+
+
+ + + diff --git a/2026-usrse/orinoco-lite-poster.svg b/2026-usrse/orinoco-lite-poster.svg deleted file mode 100644 index 1c8ea26d..00000000 --- a/2026-usrse/orinoco-lite-poster.svg +++ /dev/null @@ -1,681 +0,0 @@ - - - Beyond the Lab Website: Reusing Structured Research Metadata Across Lab Operations - Editable draft for US-RSE 2026. Two operating models for curated research information, a GitHub curation flow, measured development-site results and next evaluation steps. Snapshot 9 September 2026. Authors: John Lee, Isaac To and Yaroslav O. Halchenko. - - - - - - - ORINOCO LITE / US-RSE 2026 - - - Beyond the Lab Website - - - Reusing structured research metadata across lab operations - - - John Lee • Isaac To • Yaroslav O. Halchenko - - - Center for Open Neuroscience | Psychological and Brain Sciences | Dartmouth College - - - - - - - - - - - - - - - - C - - - - - - - - - - - - - - - - - - Center for Open Neuroscience - - - - - - - - 19-21 October 2026 - - - San Jose, California - - - - - - Curate the records once. - - - Make the website one reusable view. - - - - A working development deployment - - - CON is testing the GitHub adaptation. - Production migration remains in progress. - - - - - 01 - - - Same research information. Different operating models. - - - - - - - ORINOCO - - - Psychoinformatics deployment [1] - - - ORINOCO LITE - - - CON development deployment [2] - - - RECORDS - - - Curated collection exposed by a metadata service - - - RECORDS - - - Reviewed YAML records in a GitHub repository - - - REVIEW - - - Submissions enter a service inbox for curation - - - REVIEW - - - Pull requests provide the review surface for proposed changes - - - OPERATIONS - - - Maintain metadata services and their storage - - - OPERATIONS - - - Run GitHub Actions, static hosting and an editing App - - - - www.psychoinformatics.de - - - - - dev.centerforopenneuroscience.org - - - - - - - ORINOCO components - - - Schemas, validation, graph processing and presentation - - - are selected by - - - Orinoco Lite package and template - - - supply - - - the downstream build - - - - - 02 - - - The GitHub curation design - - - CON workflow integration remains in progress [2, 3] - - - - Pull requests - - - Edits and source proposals - - - - YAML records - - - Accepted metadata in Git - - - - GitHub Actions - - - Validation and composition - - - - Knowledge graph - - - Connected records - - - - Static website - - - Pages and graph explorer - - - - - update - on merge - - - - - are read - by - - - - - generates - - - - - is projected - into - - - People review and merge proposed metadata changes. - - - The static /edit/ and /review/ pages use a stateless GitHub App for signed-in operations. - - - Public reading and website builds do not require the curation service. - - - - could support - - - - NEXT: REUSE THE GRAPH FOR REPORTS - - - A CON reporting workflow remains to be demonstrated. - - - - - - 03 What works today - - - What we learned - - - What to evaluate next - - - 224 - - - 193 - - - canonical records - - - generated pages - - - Fresh validation and the latest GitHub Pages - deployment passed. [2] - - - Development-site snapshot: 9 September 2026 - - - - AI can propose. People curate. - - - Validation constrains structure; people still decide identity, attribution - and meaning. - - - A static website reduces service coupling. Online edits still need - secure authentication and careful authorization. - - - - Demonstrate a second use of the records. - - - Measure editing effort, correction rates and successful upgrades with - real curators. - - - Complete the CON curation workflow, App hardening and a reversible - production cutover. - - - - - - [1] hub.psychoinformatics.de/orinoco [2] github.com/con/dev-centerforopenneuroscience.org - - - [3] github.com/ORINOCO-Lite/orinoco-lite-dev • Project design and released implementation - - - Thanks to Michael Hanke, Stephan Heunis, DataLad Concepts and ORINOCO contributors, and the CON team. - - - Draft text, diagram and layout assisted by OpenAI Codex; author review pending. | CC BY-SA 4.0 - - - ... - ... - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Explore - the code - - - \ No newline at end of file diff --git a/2026-usrse/poster-notes.md b/2026-usrse/poster-notes.md index 901f810e..cbe5245d 100644 --- a/2026-usrse/poster-notes.md +++ b/2026-usrse/poster-notes.md @@ -1,52 +1,104 @@ -# Orinoco Lite poster +# ORINOCO Lite poster -The editable source is [orinoco-lite-poster.svg](orinoco-lite-poster.svg). -It preserves the title and presenter order of the [submitted abstract](orinoco-lite-poster-draft.md). -The draft leads with the deployment comparison requested by the reviewers, followed by the GitHub curation design, observed results and next evaluation steps. +The editable source is [orinoco-lite-poster.html](orinoco-lite-poster.html). +It preserves the title, presenter order and comparison in the [accepted abstract](orinoco-lite-poster-draft.md). +HTML replaces the September SVG as the maintained poster source; the earlier drawing remains in Git history. -## Editing and export +## Editing and rebuilding -Open the SVG in Inkscape or another SVG editor. -The title, comparison, diagram, results and footer have named layers. -Text remains editable text, and the CON logo and QR code are embedded vectors with no linked image dependencies. -The SVG is kept in ordinary Git so GitHub reviewers and a fresh clone can read the complete source without fetching Annex content. +Open the HTML in a browser to view it, or edit it in any text editor. +Text is ordinary HTML, colors and layout are in the opening ` @@ -104,85 +134,140 @@

Beyond the Lab WebsiteReusing Structured Research Metadata
Across L
-

John Lee · Isaac To
Yaroslav O. Halchenko

+

John LeeIsaac ToYaroslav O. Halchenko

Center for Open Neuroscience
Psychological and Brain Sciences
Dartmouth College

-

We compare two ways to deploy ORINOCO, a system for collaboratively managing and reusing structured research metadata.

-

Dedicated services or GitHub pull requests: curate people, projects and publications together, then reuse their relationships across lab operations.

+

Who works on which project, and what has it produced? Labs repeatedly assemble these facts for websites, grants and reports. ORINOCO makes them a shared collection of structured, connected records that people, software and AI tools can use.

+

Deploy with dedicated services, or use our GitHub-based model with no services for your lab to deploy.We compare two ways to run the same metadata approach: the service deployment at Psychoinformatics and ORINOCO Lite at the Center for Open Neuroscience (CON).

-

Deployment 1 · Dedicated services

-

ORINOCO

-

Developed by Michael Hanke and colleagues in the Psychoinformatics group, INM-7, Forschungszentrum Jülich. Shared LinkML schemas connect records and drive forms and validation.

-
- Contributorssubmit records - Service inboxcurators review - Collectionquery and reuse +
+

1 · Dedicated services

+

ORINOCO

+

Developed by Michael Hanke and colleagues at Psychoinformatics, INM-7, Forschungszentrum Jülich, ORINOCO connects open tools for research information. A metadata service accepts submissions from people and software; curation tools turn them into a reusable collection.

-
-
ORINOCO's own diagram: a schema connects SHACL Vue forms, Forgejo curation and the Dump Things service to catalogs, websites and reports.
-
ORINOCO’s metadata-curation components. A common model connects editing, review and reuse. - Artwork: Stephan Heunis (2026), CC BY 4.0. Text outlined for display. Source. -
-
-
-
The Psychoinformatics group homepage, showing its research-group website produced from linked metadata.
-
A website built from linked records.
psychoinformatics.de
-
+
+
+
+

Shared model: LinkML schemas

+
ContributionsForms and source tools
+
submit records
+
ProposalsService inboxes
+
curators promote
+
Accepted metadataService collection
+
build views
+
ReuseLinked graph and views
+
+
Dump Things holds the inboxes and collection. Curation connects them; details below.
+
+
+
The Psychoinformatics group homepage generated from connected research-information records.
+
The Psychoinformatics website is one view of this information.
psychoinformatics.de
+
+
+

A schema defines record types, fields and relationships, such as a person’s role in a project. The same definition generates editing forms and checks whether submitted records have the expected structure.

+
+

How a change becomes reusable data

+
+
A person editsSHACL Vue presents a form derived from the schema.
+
A tool submitsAn automated process prepares structured records.
+
+

Both submit records ↓

+
    +
  1. Validate and stageThe Dump Things Service checks incoming records against the schema and holds submissions separately from the curated collection.
    2. +
  2. Review the submissionCurators inspect, modify, accept or reject submissions using tools outside the storage service. Curation can be performed by people or automated processes.
    3. +
  3. Update the collectionAccepted records are promoted into the service’s curated collection, where identifiers connect people, projects, publications and other entities.
    4. +
  4. Query and presentquery-things selects and joins records. www-from-model supplies page templates and the graph generator; Hugo renders the website. Other consumers can generate reports or catalogs.
    5. +
+
-

Deployment 2 · GitHub collaboration

-

ORINOCO Lite at CON

-

We retain ORINOCO’s schemas and processing tools, adapting their operation to YAML records in Git, pull-request review and automated website builds.

-
- Pull requestspeople review - YAML in Gitmerge records - Actionsvalidate + build +
+

2 · GitHub-based deployment

+

ORINOCO Lite at CON

+

Lite keeps ORINOCO’s schemas, editor and processing tools, while placing records in Git and review in GitHub pull requests. A reusable package and repository template bring these components together for a static website.

-
-
SHACL Vue's Project form displaying the identifier, title and description of CON's DataLad project record.
-
Shared, schema-driven forms. SHACL Vue edits a CON project record. A GitHub App connects signed-in edits to pull requests.
-
-
-
The CON development homepage, displaying the center's open-science mission and principles with research-information navigation.
-
CON’s development website.
dev.centerforopenneuroscience.org
-
+
+
+
+

Shared model: LinkML schemas

+
ContributionsForms and source tools
+
propose changes
+
ProposalsGitHub pull requests
+
reviewers merge
+
Accepted metadataYAML files in Git
+
build views
+
ReuseLinked graph and views
+
+
The highlighted components change; the model and reusable tools stay shared.
+
+
+
The Center for Open Neuroscience development homepage generated with ORINOCO Lite.
+
The CON development website uses the GitHub deployment.
dev.centerforopenneuroscience.org
+
+
+

The repository becomes the group’s official metadata collection. Records are readable text files with a change history. GitHub Actions runs validation and publication, so the lab maintains its information without operating a metadata server.

+
+

How a change becomes reusable data

+
+
A person editsThe static /edit/ page opens a pull request from a SHACL Vue form.
+
A tool proposesAn adapter workflow opens a pull request; /review/ records which proposals to keep.
+
+

Both produce a pull request ↓

+
    +
  1. Validate and stageGitHub Actions converts the submitted edits or selected proposals into schema-validated metadata changes in the pull request.
    2. +
  2. Review the changesGitHub shows the proposed record changes for discussion and approval. Adapters can draw on existing sources, such as the lab’s Zotero publication library.
    3. +
  3. Update the collectionMerging the pull request updates the YAML records on the repository’s default branch. Git retains the accepted changes and their attribution.
    4. +
  4. Query and presentActions selects and joins records using the same www-from-model templates and graph generator. Hugo renders the site for GitHub Pages; the source records remain in Git.
    5. +
+
-

One collection · Multiple uses

-

Follow the relationships

-

Shared identifiers link people to projects and research outputs. The same structured information supports discovery, public communication and reporting.

-
-
CON's graph explorer connects people, projects, publications, organizations, datasets and topics; DataLad, DANDI and CON are visible.
-
Explore the CON knowledge graph. Relationships also drive related-item lists and links between website pages.
-
-

Beyond the website: a funder report

-

TRR379 already uses this approach for its DFG annual survey. Its central metadata infrastructure gathers personnel information and generates the funder’s census PDF.

-
-
TRR379's public article announcing its DFG annual survey and describing generation of the personnel-census PDF.
-
TRR379’s DFG survey deployment · An upstream example of reusing metadata for a second output.
+
+

3 · Local use, global connections

+

Useful in the lab.
Connected beyond it.

+

Both deployments serve the same purpose: maintain information where a group knows it best, and describe it in ways that other tools and organizations can understand.

+
+
+
The SHACL Vue form used in both deployment patterns, shown here editing the DataLad project record at CON.
+
One schema-driven editor in both deployments. SHACL Vue turns the data model into forms, so contributors can edit structured records without writing YAML or learning semantic-web syntax.
+
+

Within a group: collect once, reuse

+

Link people, projects, publications and datasets. Validation checks the structure; explicit relationships let websites, reports and queries reuse the same records instead of maintaining separate lists.

+
+
CON’s knowledge graph connects people, organizations, projects, publications, datasets and topics.
+
CON’s graph explorer: the relationships behind pages, related-item lists and cross-links.
+
+
+
+

Across groups: shared meaning

+

Ontologies give concepts and relationships shared definitions. Mapping local records to these terms makes them linkable to independently maintained research information.

+
ORCID identifies people; DOI identifies publications. schema.org supplies a shared term for names; W3C PROV supplies one for roles.
+

For AI-assisted work, explicit fields, identifiers and relationships provide context that tools can query, validate and update without having to infer the data model from scattered prose.

+
+
Already beyond the website: the upstream TRR379 deployment uses its central metadata infrastructure to collect personnel information and generate a DFG annual-survey PDF.
@@ -195,28 +280,39 @@

Keep the records reusable

template · CON content · website. - Exact revisions and image sources accompany the editable poster.

-

Thanks to Michael Hanke, Stephan Heunis, the ORINOCO and DataLad contributors, and the CON team.
- OpenAI Codex assisted with source review, text, diagrams and layout. Poster: CC BY-SA 4.0; third-party artwork and screenshots retain their respective notices.

+ Exact revisions and sources accompany the editable poster.

+

Architecture: ORINOCO Lite design charter · ORINOCO tools and documentation.

+

Thanks to Michael Hanke, Stephan Heunis, the ORINOCO and DataLad contributors, and the CON team.
+ OpenAI Codex assisted with source review, text, diagrams and layout. Poster: CC BY-SA 4.0; third-party screenshots and logos retain their respective notices.

+
+
Dartmouth College sealPsychological and Brain SciencesDartmouth College
+ ReproNim +
+ +
+ +
-