Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Return version_id in outputs #28

Open
huard opened this issue Nov 4, 2024 · 1 comment
Open

Return version_id in outputs #28

huard opened this issue Nov 4, 2024 · 1 comment

Comments

@huard
Copy link

huard commented Nov 4, 2024

First off, thanks for this action, really appreciate it. I've been experimenting with it to create two depositions from the same repo, in order to split data and code into two different digital objects.

Here are the things I had to learn the hard way or add to my composite action to get things working. Disclaimer, I'm an action newbie and had very little experience with the Zenodo API.

The action will fail if some of the files are inside a subdirectory. I understand this is not supported by Zenodo, but the error message is not very informative (Something went wrong on PUT ... File not found.) Maybe this could be catched earlier.

I won't know in advance the name of the files to be added to the deposition, so I added a glob action to match glob patterns and convert them to actual file names.

The CITATION.cff file is not always in the top parent directory (since I have two depositions), so I included cffconvert-github-action to convert the CITATION.cff file to a .zenodo.json file.

One thing that I can't easily add in my composite action is the version_id of the deposition created. What I would like is ultimately to create some kind of workflow message or notification saying something like "Deposition created at https://doi.org/...)." This would be useful to review the deposition, especially if publish is false.

Many thanks again,

David

@huard
Copy link
Author

huard commented Nov 4, 2024

To give some additional context, I'd like to create a workflow for scientists with little CI/CD experience to publish figure data to Zenodo.

The idea would be to

  1. Commit a figure and the code generating the figure to the repo;
  2. Make a release:
    2.1 Publish on Zenodo;
    2.2 Store the concept DOI in some .env file;
  3. Make sure subsequent releases use the stored concept DOI;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant