search

epiverse-trace / epiverse-trace.github.io

Technical blog of the Epiverse-TRACE project, where we share opinions and investigations in R package development, or scientific software development more generally
https://epiverse-trace.github.io/
3 stars 3 forks source link

Add DOI category #288

Closed chartgerink closed 1 week ago

chartgerink commented 2 weeks ago

This PR adds the new DOI category and adds one post by @Bisaloo to it.

After merging, I can go ahead and send the feed https://epiverse-trace.github.io/blog-doi.xml to Rogue Scholar for indexing 👍

This is step 1 for closing #113 - automatically adding the DOIs to the posts will come in a future PR.

netlify[bot] commented 2 weeks ago

Deploy Preview for tourmaline-marshmallow-241b40 ready!

Name Link
Latest commit 1822e0d3d2fd72e83dba23ca75930872bbf7f446
Latest deploy log https://app.netlify.com/sites/tourmaline-marshmallow-241b40/deploys/6679643f4feae80008e7d4c6
Deploy Preview https://deploy-preview-288--tourmaline-marshmallow-241b40.netlify.app
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Bisaloo commented 2 weeks ago

Potential concern of doing this as a two-steps workflow:

How to make sure it's not accidentally identified as a new post since the hash fingerprint will have changed?

IDK it's that's a valid concern. I'm not completely sure how RSS & Rogue Scholar work. I remember receiving duplicated RSS notifications in the past because of minor updates of content.

chartgerink commented 1 week ago

Thanks for sharing your concern @Bisaloo 🙏

I have not experienced duplicates in Quarto RSS personally, and I looked into how the feed is constructed to see whether this issue will pop up.

As it looks, the individual posts in the feed do not contain a hash ID of any kind. This would mean, I suspect, that the feed construction stays the same. The only difference might be the lastBuildDate for the feed itself, but that gets updated at every feed regeneration.

Rogue Scholar did not mention any quirks regarding Quarto and RSS feeds in my emails with them, and they have some experience running this for Quarto blogs (12 at this time).

We can probably rely on their expertise to smooth this out further if issues arise. In any case, I'll keep an eye on issues that may arise and document + resolve them as is appropriate.

noamross commented 1 week ago

Came here because I saw the DOI on your latest post! We build our site nightly, so when we first post there's no DOI but the on the next nightly build we fetch the DOI and include it in the page. Alternatively you could use JS to fetch the DOI client-side and it would be available quicker.

It's @maelle's work of course: https://github.com/ropensci/roweb3/pull/632

maelle commented 1 week ago

Maybe something to be done in a post-render script? https://quarto.org/docs/projects/scripts.html#pre-and-post-render