Heidi Seibold

2 minute read

I am in the process of making my newsletter FAIR (Findable, Accessible, Interoperable, and Reusable). Here's how.

I am an advocate for Open Science. The FAIR priciples are very near and dear to my heart.

I was excited when the Open Science folks at Jülich archived a bunch of my posts and gave them a persistent identifier (DOI, see archived posts here). This was exactly what I was still missing to make my posts more FAIR. However, I cannot expect them to take care of archiving all my posts and I would love to have all of them available with not only a DOI, but also in a more machine-readable way. That is why now I am finally getting to it and am making all future posts available, searchable, machine-readable, reusable with an open license (CC-BY 4.0) and with a persistent identifier (DOI).

I spent the whole day on this and here’s the plan that I came up with:

Infrastructure

This section is for the tech nerds here who want to know all the details. If you’re not one of them, that’s ok. You don’t need to know what Jekyll is :wink:.

I am planning on using the following infrastructure setup:

  • Jekyll website (hosted via GitLab pages), that allows me to write Markdown posts and creates an Atom feed.
  • Kit newsletter service that can turn an Atom feed into newsletter posts automatically.
  • Add my blog to Rogue Scholar, an archive for scholarly blogs, which provides long-term archiving, DOIs and metadata.

I really like using Kit for my newsletter and love creating email courses and automations with it. To make my newsletter FAIR, however, it’s not quite suitable, because the only way I could archive it and generate a DOI would be manually. Knowing myself, I’d probably forget doing that.

So, I am switching to using two tools instead of one and I am getting even more exposure by publishing on Rogue Scholar. Isn’t that something? :smiley:

My website is already set up. I am using Jekyll (Minimal Mistakes theme) and have a GitLab repository from where my website is automatically built (see pipelines). Adding a blog is incredibly easy, as Jekyll is meant for writing blogs and with the jekyll-feed plug-in an Atom feed is generated without me having to understand how it works (which is good, because I don’t).

Workflow

From now on I will do the following when I want to write a newsletter post:

  1. Write post in Markdown.
  2. Push post to GitLab repositor to build my website, which automatically generates the Atom feed.
  3. Adapt the automatically generated newsletter and send it to my subscribers.
  4. Check if the post shows up on Rogue Scholar (which it automatically should).

Does this make my newsletter FAIR?

Well, FAIR is not binary, but a spectrum…

I think having a unique and persistent identifier in the form of a DOI and improving long-term availability makes the newsletter more FAIR.

I am open for your suggestions on how I could make it even more FAIR in the future.

I am also open to hearing what your thoughts are about my new setup, even if I am a little scared :grimacing:

I am ending the day quite pleased with myself and hope you enjoy reading my self-centered post of the day :tada:

All the best,
Heidi

Updated:

You may also enjoy

Markdown-based course websites

2 minute read

New frameworks for course websites are popping up all the time. In this post, I’ll review some of them.

Sketchnoting

1 minute read

Taking notes and drawing little images helps me think, but they are also helpful to others. Would sketchnoting also be for you?

Collaborative Coding

4 minute read

Too many code projects in research are done by a single person. Keep reading on why that’s bad and how to do better.

Incorporation of the Digital Research Academy

2 minute read

I am excited to share that the Digital Research Academy incorporation is almost done. We had our notary appointment last week, set up the bank account and ar...