Starting this Monday November 3rd the Rogue Scholar science blog archive stopped registering concept DOIs for new blog posts, i.e. two DOIs for each post.
The InvenioRDM repository platform that Rogue Scholar uses supports DOI versioning:
When you publish an upload for the first time, we register two DOIs:
* a DOI representing the specific version of your record.
* a DOI representing all of the versions of your record.
Afterwards, we register a DOI for every new version of your upload.
While this approach makes perfect sense for publishing content that has a lot of versions such as datasets or software on Zenodo (which initially implemented DOI versioning), it is not a good fit for blog posts which rarely have more than one version and never dozens or hundreds of versions. This feature is built-in into the InvenioRDM repository platform and the versioning happens automatically, but it has always confused authors and readers.
Already registered blog posts keep their two DOIs for the specific version and all versions (concept DOI). Blogs archived in Rogue Scholar using their own DOI registration (e.g. the DataCite or ROR blog) never used DOI versioning.
And this change is unrelated to two other aspects of DOI versioning:
- DOIs have no concept of versions in the DOI suffix such as 10.5555/12345678.v1, this is an arbitrary decision by the publisher. The version information is found in the DOI metadata (and supported for Crossref DOIs since schema 5.4 released March 2025).
- Blog posts and other scholarly content should always link to other versions via relations metadata, e.g. IsNewVersionOf, or IsPreprintOf.
Please use Slack, email, Mastodon, or Bluesky if you have any questions or comments, in particular with regards to DOI versioning.
References
- Fenner, Martin. “Rogue Scholar Starts Supporting Versioning.” Front Matter, September 29, 2025. https://doi.org/10.53731/nxp08-a9947.
