Hello,
I’m new to DataCite DOIs, but exploring how we can apply them to institutional blog posts. Is anyone else doing this? I’d be particularly interested to know if you are applying the DOI directly to the blog post, or to a metadata record, and whether you’ve had any internal discussions about blog URL stability before beginning.
Finally, is anyone aware of a plugin that would work with the WordPress platform to automate DOI minting?
Many thanks for any comments or help
Best wishes
Helen
1 Like
Hi and welcome, @HelenW!
DataCite DOIs can definitely be applied to blog posts.
In fact, we use DOIs ourselves on the DataCite blog! We have been using the resourceTypeGeneral “Text” with the resourceType “blog post”.
The DataCite blog uses WordPress, and we register these DOIs individually through the DataCite Fabrica web interface. I’m not aware of any WordPress plugin for automated DataCite DOI registration, though if you find one, please let us know!
Here is another example from the blog for The Commonwealth Fund: https://doi.org/10.26099/7pht-w940.
And one more from the DINI (Deutsche Initiative für Netzwerkinformation) blog: https://doi.org/10.57689/dini-blog.20230515
2 Likes
So, Martin Fenner, who’s been up to some pretty cool stuff with scholarly blog posts. AFAIK He’s been working with InvenioRDM to build an archive just for these kinds of posts. He’s also been talking about how useful it could be to have DOIs attached to each blog post. Martin’s also been looking at different ways to make this whole thing work, like how some other big-name academic resources do it. But, he’s also pointed out that there are a few hurdles to get over, like figuring out the business side of things and deciding on a standard format for archiving these blog posts.
Here’s the really exciting part: Martin has started a project called “Rogue Scholar” to make this idea a reality. It’s an archive just for science blogs that kicked off in April 2023. At the start, it was pretty basic – science blogs could sign up and get added to the archive in just a couple of days. And it’s already getting some traction!. So, it’s clear that there’s some real momentum behind the idea of creating a system for attaching DOIs to blog posts and archiving scholarly blogs in one place. Isn’t that awesome?
2 Likes
Thanks @KellyStathis, that’s really helpful to see the DOIs in place on the blog posts, and to know what resource types you’re using.
Thanks @SofiSmith, I wasn’t aware of Martin Fenner’s work so that’s been a really interesting read - particularly to see Rogue Scholar.
Hi @KellyStathis I’m just having a read through the DataCite Metadata Schema https://schema.datacite.org/meta/kernel-4.4/doc/DataCite-MetadataKernel_v4.4.pdf and can’t see ‘blog post’ listed in the resourceType controlled vocab. Am I missing it, or is it that you can use free text as part of the ‘other’ option? Thanks!
You can use “Text” for resourceTypeGeneral and “Blog post” for resourceType. For example:
<resourceType resourceTypeGeneral="Text">Blog post</resourceType>
1 Like
I’m rather late to this discussion - but v interested, especially in Rogue Scholar, not least in my new role as cochair of The Scholarly Kitchen committee. At ORCID, we used to add all our blog posts to our figshare repo where they were automatically assigned a DataCite DOI and then (oh joy!) automatically added to our ORCID record. That doesn’t seem to be happening any more - and the blog posts that were on figshare have been removed. However, thanks having a DOI they now resolve instead to the ORCID website. PIDs are so good at being … persistent 
Hi @AliceM, thanks for joining the discussion. I still feel at rather early days with this. There have been a number of things to work through locally, and still some more things to consider before we get up and running. One of the things yet to look at is whether we could use ORCIDs as a way of manging names within the metadata for blog DOIs. I’m also leading an ORCID integration project for our CRIS, so these would then automatically push through to individual ORCID records as well…
Congrats on the new role as co-chair with The Scholarly Kitchen committee
1 Like