Draft USRSE poster on reusable research metadata - #15
Open
leej3 wants to merge 4 commits into
Open
Conversation
Co-Authored-By: Codex 0.146.0-alpha.9.2 / GPT 5.6-sol <codex@openai.com>
Co-Authored-By: Codex 0.146.0-alpha.9.2 / GPT 5.6-sol <codex@openai.com>
Co-Authored-By: Codex 0.146.0-alpha.9.2 / GPT 5.6-sol <codex@openai.com>
Co-Authored-By: Codex 0.146.0-alpha.9.2 / GPT 5.6-sol <codex@openai.com>
leej3
marked this pull request as ready for review
August 3, 2026 20:40
yarikoptic
reviewed
Aug 3, 2026
|
|
||
| Research-information management is an established field [1]-[3]. CERIF defines connected entities for interoperable research systems; commercial platforms and open systems such as VIVO and DSpace-CRIS maintain institutional research records; and OpenAIRE and OpenAlex show what connected scholarly metadata can support at global scale [1], [4], [5]. This prior art demonstrates the value of modeling research information, but it also reveals a practical gap. A lab often needs finer-grained operational context, local authority over its records, and an immediate benefit that justifies keeping them current. Institutional-scale services and global discovery graphs address many research-information needs, but they do not by themselves give an individual lab a practical, locally governed path for maintaining the finer-grained context it uses day to day. | ||
|
|
||
| Orinoco is an open, self-hostable ecosystem for maintaining and reusing structured research information [6]. Its research-specific model represents people, organizations, projects, grants, datasets, instruments, software, publications, and their relationships as records that can be validated, reviewed, and traced to their sources. The full system provides shared services through which a group can curate those records collaboratively and use them in multiple applications. For labs already familiar with GitHub, we developed Orinoco Lite: a GitHub Action that validates reviewed records and generates a static website [7]. In both cases, the lab maintains connected research information once and derives useful outputs from it. The website is an immediately useful output and an incentive to keep the records current, not the boundary of the system. |
Member
There was a problem hiding this comment.
could replace "developed" to "are developing" to be more factually correct.
Ideally such .md intended for github review better be formatted "one sentence a line" which would simplify suggestions.
Member
There was a problem hiding this comment.
Can mention that in this "lite" version we are touching upon a larger scoped work Orinoco people aiming for with overall LIAB (lab in a box) with deployment of forgejo and dump-things for all data logistics and version control.
yarikoptic
reviewed
Aug 3, 2026
| Research-information management is an established field [1]-[3]. CERIF defines connected entities for interoperable research systems; commercial platforms and open systems such as VIVO and DSpace-CRIS maintain institutional research records; and OpenAIRE and OpenAlex show what connected scholarly metadata can support at global scale [1], [4], [5]. This prior art demonstrates the value of modeling research information, but it also reveals a practical gap. A lab often needs finer-grained operational context, local authority over its records, and an immediate benefit that justifies keeping them current. Institutional-scale services and global discovery graphs address many research-information needs, but they do not by themselves give an individual lab a practical, locally governed path for maintaining the finer-grained context it uses day to day. | ||
|
|
||
| Orinoco is an open, self-hostable ecosystem for maintaining and reusing structured research information [6]. Its research-specific model represents people, organizations, projects, grants, datasets, instruments, software, publications, and their relationships as records that can be validated, reviewed, and traced to their sources. The full system provides shared services through which a group can curate those records collaboratively and use them in multiple applications. For labs already familiar with GitHub, we developed Orinoco Lite: a GitHub Action that validates reviewed records and generates a static website [7]. In both cases, the lab maintains connected research information once and derives useful outputs from it. The website is an immediately useful output and an incentive to keep the records current, not the boundary of the system. | ||
|
|
Member
There was a problem hiding this comment.
can in above make it explicit that https://www.psychoinformatics.de/ website is such a website which is our inspiration etc.
yarikoptic
reviewed
Aug 3, 2026
|
|
||
| Research software engineers often inherit not only research code, but also the information systems through which groups communicate their work to collaborators, funders, institutions, and the public. Designing those systems as maintainable, reusable infrastructure brings together software architecture, data stewardship, interoperability, governance, and long-term sustainability. Orinoco provides a concrete setting in which to make that frequently invisible RSE contribution legible. | ||
|
|
||
| This contribution advances US-RSE's Community, Advocacy, and Resources goals in distinct ways. It gives the community a concrete pattern and vocabulary for exchanging experience across labs and institutions; advocates for metadata modeling and stewardship as consequential RSE work; and contributes open resources, including shared models, validation workflows, and service-backed and GitHub-based implementations, that practitioners can evaluate and adapt. It also highlights the RSE judgment required to connect local needs with community standards and choose an operating model a group can sustain. |
Member
There was a problem hiding this comment.
what "vocabulary" ? smells like if it came from STAMPED poster
yarikoptic
reviewed
Aug 3, 2026
|
|
||
| ## Acknowledgments | ||
|
|
||
| We thank Michael Hanke and the contributors to DataLad Concepts and the Orinoco ecosystem for the underlying schemas, services, and implementation patterns, and the broader Center for Open Neuroscience team for motivating operational use cases. |
Member
There was a problem hiding this comment.
Suggested change
| We thank Michael Hanke and the contributors to DataLad Concepts and the Orinoco ecosystem for the underlying schemas, services, and implementation patterns, and the broader Center for Open Neuroscience team for motivating operational use cases. | |
| We thank Michael Hanke, Stephan Heunis and other contributors to DataLad Concepts and the Orinoco ecosystem for the underlying schemas, services, and implementation patterns, and the broader Center for Open Neuroscience team for motivating operational use cases. |
yarikoptic
requested changes
Aug 3, 2026
yarikoptic
left a comment
yarikoptic
left a comment
Member
There was a problem hiding this comment.
I feel that it is a little too AI slop bloated and too abstract: does not even mention any specific like LinkML (schema to rule it all), YAML files (human and machine readable), Hugo rendering, Zotero for managing bib, -- so overall living to our promise of reuse.
Could also directly also link to https://github.com/con/solidation which is somewhat inspirational here -- creation of reports from a minimalistic data structure listing "work horizon" for a group. So, likely orinoco lite repo, might become that sink of records for relevant work scopes (projects), and achivements (publications), ...
I wonder if there could be a figure added to poster abstracts? we could potentially gather one from Michael or Stefan (and attribute them) for the entire "metadata circle".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Addresses: con/cierge#18