Zenodo metadata for the template itself + production API defaults - #38
Merged
Merged
Conversation
The template's CITATION.cff is full of {{placeholders}}, including
date-released and the ORCID, so it is not valid citation metadata (cffconvert
rejects it) and cannot describe the template's own Zenodo record. Add a
.zenodo.json for the template itself; Zenodo's GitHub integration prefers it
over CITATION.cff.
.zenodo.json must not survive into a study created from the template, or every
replication would be archived under the template's title and creators.
init_template.py now deletes it (reported on a dry run too), with two tests.
/np/constellation is on production since 2026-09-20 and forrt-research-mcp 0.1.1 defaults to it. import-from-nanopub's curl now defaults to production too; verify-chain says so, keeps dev as an explicit opt-in, and tells existing users to upgrade (pre-0.1.1 servers still default to dev).
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
1 participant
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.
The template is now switched on in Zenodo, but its next release would not have archived cleanly. This PR fixes that and updates the skills to use the production API.
1. The template's own Zenodo metadata
CITATION.cffin this repo is a template:{{AUTHOR_FAMILY}},{{AUTHOR_ORCID}},date-released: "{{RELEASE_DATE}}"…cffconvert --validaterejects it, so Zenodo cannot build a record from it..zenodo.jsondescribing the template itself (title, description, Anne Fouilloux + ORCID + LifeWatch ERIC, keywords, MIT). Zenodo's GitHub integration prefers.zenodo.jsonoverCITATION.cff, so the template's release gets clean metadata whileCITATION.cffkeeps its placeholders for studies.scripts/init_template.pydeletes.zenodo.jsonwhen a study is initialised, and a dry run reports that it would. Otherwise every replication created from the template would be archived under the template's title and creators. Two new tests cover this; the init-template skill documents it.release-identifiers.ymlis unaffected on this repo: its ready-guard already skips while the.template-uninitialisedsentinel is present, so it won't write DOIs into the template's placeholder files.2. Skills default to the production API
import-from-nanopub: the sibling-repocurldefaults tohttps://api.sciencelive4all.org(wasapi-dev).verify-chain: says the server defaults to production, keeps dev as a commented opt-in so a copy-paste doesn't switch to dev, and addspipx upgrade forrt-research-mcp, because servers before 0.1.1 still default to dev./np/constellationhas been on production since 2026-09-20, and forrt-research-mcp 0.1.1 (on PyPI) defaults to it.Checks
pixi run -e tests pytest: 164 passed (2 new)..zenodo.jsonis valid JSON.After merge
Cut v2.1.1 as a GitHub Release. That is the template's first version archived on Zenodo.