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

empty sandbox deposition lists - Can not set embargo date for Zenodo Sandbox deposit #93

Open
rkrug opened this issue Dec 5, 2023 · 4 comments

Comments

@rkrug
Copy link

rkrug commented Dec 5, 2023

I have a dataset I want to publish as embargoed - so far so good. But I can not set the time until when it is embargoed.

r$> cli
<deposits client>
 deposits service : zenodo
           sandbox: TRUE
         url_base : https://sandbox.zenodo.org/api/
 Current deposits : 1 (see 'deposits' element for details)

   hostdata : <none>
   metadata : 8 terms (see 'metadata' element for details)

r$> cli$metadata$accessRights
[1] "embargoed"

r$> cli$deposit_embargo("2024-01-01")
Error: Client not associated with any deposit which can be embargoed. Please first use `deposit_new()` or `deposit_retrieve()` methods.
@rkrug
Copy link
Author

rkrug commented Dec 5, 2023

Happy to provide more details if needed.

@mpadge
Copy link
Member

mpadge commented Dec 5, 2023

Likely because of #92 (comment):

The deposit_id value should be populated from the Zenodo sandbox data, but if that's all empty, there's no value to use.

This issue can serve as a placeholder to address all issues related to empty sandbox deposition lists.

@rkrug rkrug changed the title Can. not set embargo date for Zenodo Sandbox deposit empty sandbox deposition lists - Can not set embargo date for Zenodo Sandbox deposit Dec 6, 2023
@rkrug
Copy link
Author

rkrug commented Dec 6, 2023

Have you tried if it works on Zenodo non-sandbox?

I am asking because I have to make some deposits in December and would like to use deposits but have to do it manually if it does not work on Zenodo non-sandbox.

@mpadge
Copy link
Member

mpadge commented Dec 6, 2023

Yep, on non-sandbox everything seems to work as expected. The sandbox is, however, a complete mess. The web interface dumps the explicit validation errors at the top, which is useful, but also shows a bunch of errors some of which are simply impossible to resolve. I have no idea what is going on there, and will have to allocate some time next week to check it all out. Sorry for the inconvenience, but at least the non-sandbox seems to be functioning same as ever.

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

2 participants