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

Update Zenodo archive #3399

Open
Aariq opened this issue Dec 13, 2024 · 6 comments
Open

Update Zenodo archive #3399

Aariq opened this issue Dec 13, 2024 · 6 comments
Assignees

Comments

@Aariq
Copy link
Collaborator

Aariq commented Dec 13, 2024

The Zenodo archive of this repo is at version 1.7.2 and does not include all recent contributors. Not sure if maybe Zenodo—GitHub integration was broken or never set up, but it would be good to get those in sync.

@harshagr70
Copy link
Contributor

harshagr70 commented Dec 16, 2024

Hi @Aariq , I checked the Zenodo archive for the v1.8.0 release, and it seems the archive hasn't been created yet. This suggests that the Zenodo-GitHub integration might be broken and could require a manual trigger to sync the latest release with Zenodo.

@Aariq
Copy link
Collaborator Author

Aariq commented Dec 16, 2024

If this is set up with the Zenodo github integration, you might also try emailing their support—I've had good experiences in the past with them fixing the integration for me (e.g. when I moved a repo to a different organization and the integration stopped working correctly)

@harshagr70
Copy link
Contributor

Thank you for sharing your suggestion regarding Zenodo support! @Aariq 😊
I would like to explore alternate options to resolve the issue before reaching out to the Zenodo support team. If those don’t work, I’ll proceed with contacting their support as you suggested. I’ll keep you updated on the progress.

@dlebauer
Copy link
Member

I've made some progress; most recent upload is 1.7.1 at https://zenodo.org/records/5557914. There is some problem with 1.8.0 and I've reached out to support.

@dlebauer dlebauer self-assigned this Dec 16, 2024
@dlebauer
Copy link
Member

It looks like the Zenodo CFF parser is the issue. Our CITATION.CFF passes the official validator, but Zenodo's parser only allows one value for license. At least it should be easy to fix.

I have tested your file and the issue seems to be with the field "license", the backend expects it to be one value only of type "string". E.g:

license: "BSD-3-Clause"

Note that not all the fields will be ingested by Zenodo since our current implementation of the CITATION.cff standard for the github integration is still a subset of the full schema. We are working to expand it in the future, but right now not all the fields will be considered.

dlebauer added a commit that referenced this issue Dec 17, 2024
Change to address Zenodo requirements. #3399
@dlebauer
Copy link
Member

dlebauer commented Dec 17, 2024

I have opened a pull request. I think the only way to test that it will work is to merge the PR and submit again to Zenodo. I think we should just update the 1.8.0 release since this is a minor change just related to the meta data. I can do this when somebody approves this PR.

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

3 participants