You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
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.
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.
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.
The text was updated successfully, but these errors were encountered: