search

rseng / zenodo-release

Automated releases to zenodo without granting admin access to webhooks
MIT License
10 stars 4 forks source link

Uploads don't associate with existing DOIs. #1

Closed johrstrom closed 2 years ago

johrstrom commented 2 years ago

I'm trying this in a very simple project. But it seems when I upload the next version - the new DOI isn't associated with my existing DOI.

I'm trying to get the terminology right - but let's call it a base DOI.

image

https://zenodo.org/record/6325946 - is the link for version 2.0.23-1-1, but somehow Zenodo was able to figure out it was associated with the base DOI https://doi.org/10.5281/zenodo.6323791

This is the base DOI i wanted to use (generated manually) https://zenodo.org/record/6323748#.YiJLl9tOnzw

and this is the new DOI that isn't associated with the former (generated from https://github.com/johrstrom/test-actions). https://zenodo.org/record/6328317#.YiJLsdtOnzw

vsoch commented 2 years ago

@johrstrom when I was testing I tried adding the .zenodo.json from a DOI that I created manually in the interface, and it gave me an error that I could not because it was "managed locally." So I think you'd have to create the record fully with the tool, but then update your .zendoo.json metadata record to use it. Do you want to try that?

vsoch commented 2 years ago

The deposition API has a doi field: image so let's try adding it to that. If that works, we can update the action to have it and write instructions to the user to use it!

johrstrom commented 2 years ago

The deposition API has a doi field

I think that's our ticket. I've got time today, so I was trying to work through it. Happy to do it and submit a pull request.

vsoch commented 2 years ago

Sounds good! And I can help after the work day - we will get it working! Likely we need to give instruction to the user to have the field in the action blank, and then to add a doi field after the first push.

vsoch commented 2 years ago

okay this is fixed!