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
Currently, upload_to_zenodo will try to lob whatever the specified PDF is at Zenodo. Zenodo itself is idempotent, e.g. won't change the upload if the MD5 checksum matches, but this (a) is slow because each paper is 1-4MB, which is roughly 100MB per conference and over 1GB in aggregate, and (b) requires that the PDFs are accessible if local, or suffers both a download and upload if the electronic edition (ee) is a URL on the web.
There are few ways around this (and maybe others):
track MD5 checksums from Zenodo in the proceedings database
before uploading, ask Zenodo what the latest MD5 checksum is
toggle PDF uploading as a global arg
(3) is certainly the easiest to implement, but also the easiest to misuse / create drift. That said, perhaps we start there and revisit if it becomes problematic?
The text was updated successfully, but these errors were encountered:
realizing I left it out, the issue with (3) is if we want to only update some of the PDFs ... (3) is an all or nothing option. If we wanted a partial bypass, we'd have to do something else (side-chain bypass info?)
Currently,
upload_to_zenodo
will try to lob whatever the specified PDF is at Zenodo. Zenodo itself is idempotent, e.g. won't change the upload if the MD5 checksum matches, but this (a) is slow because each paper is 1-4MB, which is roughly 100MB per conference and over 1GB in aggregate, and (b) requires that the PDFs are accessible if local, or suffers both a download and upload if the electronic edition (ee
) is a URL on the web.There are few ways around this (and maybe others):
(3) is certainly the easiest to implement, but also the easiest to misuse / create drift. That said, perhaps we start there and revisit if it becomes problematic?
The text was updated successfully, but these errors were encountered: