You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a dataset has been updated in OpenNeuro and it is already in Nemar, assuming there is no new changes in Nemar, could there be a simple command to bring the Nemar dataset up to date?
It is a little more complicated than that:
We are allowing PRs on our website, and provide a version patch, so basically each version import from ON is a major version bump (not yet implemented), then we update with monitor and patch versions. Does this sound good?
Yes, as long as there is a mechanism in place and the DOIs are pointing to the right location (the updated NEMAR needs to point to the updated OpenNeuro version). Tx
Documenting the versioning policy here so it's a single source of truth.
OpenNeuro-pull = major bump on NEMAR side. Period.
Each pull from OpenNeuro bumps the NEMAR major version — regardless of whether the upstream OpenNeuro change was minor or major. NEMAR-side modifications between pulls take minor/patch bumps.
Concretely for an on* dataset:
NEMAR version
What it represents
Source
v1.0.0
Initial import from OpenNeuro
as-imported mirror
v1.0.1, v1.1.0, ...
NEMAR-side fixes/improvements
NEMAR PRs against the dataset repo
v2.0.0
Subsequent re-pull from OpenNeuro
as-imported mirror (new)
v2.0.1, v2.1.0, ...
NEMAR-side fixes/improvements on top of v2.0.0
NEMAR PRs
v3.0.0
Yet another re-pull
as-imported mirror (newer)
The set of "as-imported" NEMAR mirror versions is exactly the vN.0.0 tags. Each one has a 1:1 relationship to a specific OpenNeuro version at the time of pull.
Implications:
DOI mapping: each vN.0.0 NEMAR DOI should map (via DataCite IsDerivedFrom) to the specific OpenNeuro DOI it was pulled from. Subsequent minor/patch NEMAR versions inherit the same IsDerivedFrom relation until the next major pull.
Upstream-update detection:nemar admin sync-openneuro (or whatever the eventual command is) checks if the upstream ds* has a new version since the last vN.0.0 mirror; if so, pull and bump to v(N+1).0.0 — never touch minor/patch from this path.
Front-door discovery (website-side): the dataset detail page on nemar.org will:
Detect on* via prefix + related_identifiers DERIVED relations
Render a "NEMAR-curated copy of OpenNeuro ds00xxxx" provenance card
List every vN.0.0 as an "as-imported mirror snapshot" so users can compare any of them against the current latest
DOI parity table side-by-side (NEMAR DOI ↔ OpenNeuro DOI)
The frontend logic is being implemented now in nemarOrg/website Phase 2 (see provenance.ts's listMirrorVersions). When the CLI/backend side of this lands (this issue), the website logic stays correct — it only depends on the version-tag shape we agreed on.
Worth promoting this to docs.nemar.org once both sides ship.
Activity
neuromechanist commentedon May 13, 2026
It is a little more complicated than that:
We are allowing PRs on our website, and provide a version patch, so basically each version import from ON is a major version bump (not yet implemented), then we update with monitor and patch versions. Does this sound good?
arnodelorme commentedon May 13, 2026
Yes, as long as there is a mechanism in place and the DOIs are pointing to the right location (the updated NEMAR needs to point to the updated OpenNeuro version). Tx
fix(onboard-openneuro): skip ds IDs whose nemarDatasets repo exists (#…
neuromechanist commentedon May 15, 2026
Documenting the versioning policy here so it's a single source of truth.
OpenNeuro-pull = major bump on NEMAR side. Period.
Each pull from OpenNeuro bumps the NEMAR major version — regardless of whether the upstream OpenNeuro change was minor or major. NEMAR-side modifications between pulls take minor/patch bumps.
Concretely for an
on*dataset:v1.0.0v1.0.1,v1.1.0, ...v2.0.0v2.0.1,v2.1.0, ...v3.0.0The set of "as-imported" NEMAR mirror versions is exactly the
vN.0.0tags. Each one has a 1:1 relationship to a specific OpenNeuro version at the time of pull.Implications:
vN.0.0NEMAR DOI should map (via DataCiteIsDerivedFrom) to the specific OpenNeuro DOI it was pulled from. Subsequent minor/patch NEMAR versions inherit the sameIsDerivedFromrelation until the next major pull.nemar admin sync-openneuro(or whatever the eventual command is) checks if the upstreamds*has a new version since the lastvN.0.0mirror; if so, pull and bump tov(N+1).0.0— never touch minor/patch from this path.nemar.orgwill:on*via prefix +related_identifiersDERIVED relationsds00xxxx" provenance cardvN.0.0as an "as-imported mirror snapshot" so users can compare any of them against the current latestThe frontend logic is being implemented now in
nemarOrg/websitePhase 2 (seeprovenance.ts'slistMirrorVersions). When the CLI/backend side of this lands (this issue), the website logic stays correct — it only depends on the version-tag shape we agreed on.Worth promoting this to
docs.nemar.orgonce both sides ship.Phase 2: Dataset detail page + on* provenance + version switcher (#8)