Zenodo entries

[egpbos]

Between 2020 and now, the coupling to Zenodo broke. We restored it for the v1.0.1 release, but now Zenodo treats it as a new entry.

We now have the old record: https://zenodo.org/records/4020622

... and the new record: https://zenodo.org/records/14965745

Todo:

• Ideally, we would somehow get these merged.
• Possibly we need to change the DOI link on the README.

[egpbos]

More detailed analysis from @bouweandela:

I now understand what went wrong with Zenodo: the original record (https://zenodo.org/records/4020622) is only the PDF, which failed to build, so that is why there was no update. I enabled the integration, but that is for source code, so a new record was created here: https://zenodo.org/records/14965745

[bouweandela]

Maybe we should just get rid of the new DOI (is that even possible?) and fix the PDF build so that uploads to the PDF DOI.

[egpbos]

I have ownership now of the old Zenodo record, so that may help. Haven't looked deeply yet, maybe we can have a look together soon.

[egpbos]

Merged #270 to see if it works now. Manually triggered the sandbox workflow... https://github.com/NLeSC/guide/actions/workflows/upload-pdf.yml

[egpbos]

Alright, it worked!

I now also understand what the "Press the Publish button" thing means. Zenodraft actually (and in hindsight not unsurprisingly) makes a draft on Zenodo, so you have to go into your record on Zenodo and press Publish there:

This is perfect for the manual draft action. Maybe it's also fine for the definitive release one, but maybe not (I think people will probably forget to do that step manually), lemme know what you think @bouweandela @c-martinez.

After pressing publish, this is what we get: https://sandbox.zenodo.org/records/277445

Now, the question remains: what happens when we now try to update the original record? I will do a test release to see.

[egpbos]

Oh, some weird stuff has also happened, it seems: the main repo now has a tag with the date. The date itself is also obviously wrong, we already discussed before that we should remove the explicit date from the metadata (CFF, zenodo.json), so let's try fixing that as well...

[c-martinez]

I think the people have to click Publish in Zenodo is not a bug, it is a feature. It means that whoever is making the release needs to take responsibility of checking all the data & metadata are correct before publishing. Maybe we just need to have two lines of documentation of what is the release process: "Click release on Github, click publish on Zenodo".

[egpbos]

Made a new release with the fixes (hopefully) from #443: https://github.com/NLeSC/guide/releases/tag/v1.1.1

This correctly triggered this action: https://github.com/NLeSC/guide/actions/runs/16572319535

That created a draft deposition, but without a version in the metadata. I added that manually ("v1.1.1") and published it.

Here is the resulting entry, now back in the correct record! 🎉 https://zenodo.org/records/16538332

[egpbos]

Two additional metadata details that got lost: type ("Book") and language ("English"). I think we can live without these tbh.

[egpbos]

Ideally, we should still make sure the version is correctly uploaded (uses tag created in GitHub release)...

[egpbos]

... but that's for another issue and another day (if I can drag myself away from this rabbit hole)!