Minting of DOIs (and archival?) for blog posts #7174
Replies: 5 comments 8 replies
-
The hypothetical new This sounds like it would be super fun to explore in depth, but with my current arrangement I'd need to write a grant proposal for a chance of funded time to work on it. I just got done writing another proposal and jeez I didn't know how exhausting it could be! |
Beta Was this translation helpful? Give feedback.
-
This feels like something that a couple of Quarto project scripts could handle! Maybe:
|
Beta Was this translation helpful? Give feedback.
-
I've learned a few new things after getting introduced to some folks with Crossref and The Rogue Scholar.
|
Beta Was this translation helpful? Give feedback.
-
I am the Rogue Scholar developer, and the service is indeed providing option 2, The problem with Zenodo/InvenioRDM is that the DOIs you register there will point to Zenodo and not your blog. But it is a good platform to upload blog content that already has a DOI in one of the many Quarto output formats (e.g. PDF or ePub). I am involved in InvenioRDM development and happy to help with writing a Quarto integration, as that is on my roadmap for the next three months. |
Beta Was this translation helpful? Give feedback.
-
I hope @mfenner is not going to hate me for teaching people how to potentially hug his site to death, but here's how I solved this problem: a project script. @mfisher87, this may meet your needs. This is a pre-render script that looks at the first ten posts in the Rogue Scholar feed, obtains the DOI via |
Beta Was this translation helpful? Give feedback.
-
Description
I'm currently a user of Zenodo to automatically generate DOIs for each release of my software projects on GitHub, and I love that my source is automatically archived and citable. All I have to do is flip a switch and Zenodo starts watching my repo for Releases. When one happens, it reads state from my Git repository and, if I have one, a
CITATION.cff
file, to find the metadata it needs.I've been thinking that this experience would be amazing to have for each post I make on my Quarto blog. Of course, since my blog is already a repo on GitHub, I can easily get a DOI for the whole thing, but that's not what I'm looking for.
I don't know what this workflow might look like, there are definitely complexities I haven't considered. Perhaps:
quarto add-doi posts/my-post/index.md
which would reach out to a DOI authority/archival service like Zenodo, authenticate with the author's credentials, send a copy of the live post (by scraping fromsite-url
? maybe modifying to embed image data?) for archival, and request a DOI. Once it gets a DOI, it updates the source file with the DOI in the front-matter.This feels like a big ask, but also possibly a huge win for adoption by technical publishing communities. As far as I can tell, there is a Wordpress plugin that can do this, some commercial live services that can do this, but nothing else.
Note
I'm already using the
citation: true
feature to generate citations at the bottom of each post, and I can manually generate DOIs for each post and then add the DOI to the front-matter. This gets the end result I'm looking for, but the process is too manual.Beta Was this translation helpful? Give feedback.
All reactions