Hi. I’m not sure if this is something that falls under Binderhub’s control, or if this is something that I should talk to the Zenodo devs about, so I thought I’d ask here first:
Is it possible to have Binder detect if the Zenodo
.zip archive it has access to has been properly unpacked?
Binder has the fantastic feature of being able to create Binder images from a Zenodo DOI. Example: Binder
However, this nice functionality will only unpack the Zenodo archive if the Zenodo archive was made from the Zenodo GitHub importer. If instead, the archive was manually uploaded to Zenodo (like mplhep: bridging Matplotlib and HEP from PyHEP 2020 ) then the resulting valid Zenodo DOI can not be used to create a useful Binder image.
Instead, the built Binder image will launch the Jupyter server with the archive zip file being the only file in the server top level directory, as opposed to being unpacked like the importer method.
Is this the intended behavior? If so, can someone point me in an area where I can better understand why? If not, can this get fixed so that all valid Zenodo DOIs get treated the same (happy to help if possible/useful)? If this behavior could be changed that would be pretty huge, as that would also ensure that past physics workshops like PyHEP 2020 could have most of the projects in its Zenodo community collection be runnable on Binder far into the future given Zenodo’s archive stability.
For clarity, example links are repeated here: