search

plazi / Biodiversity-Literature-Repository

covers the creating, maintenance and upload to the BLR
3 stars 0 forks source link

duplicate minting of image doi #9

Open myrmoteras opened 6 years ago

myrmoteras commented 6 years ago

@gsautter an you check, why I do get a duplicate deposit in BLR when I save the document, that I reopened using its UUID.

https://zenodo.org/record/998589

this concerns the images.

The UUID is FFE8EA274F658B706275C03FFF83FFE2

It is a medical journal (my borthers headache journals) and he is interested in our process - so we choose a random article he published, throw it into GGI and watched. It has a problem because of the captioons being superimposed of the images, that I had to fix manually.

gsautter commented 6 years ago

The "caption inside image" issue surely is a GGI thing, but it should be possible to resolve via a respective style template property.

gsautter commented 6 years ago

Regarding duplicate images: did the IMF already have a Zenodo-Dep ID when you reopened it? If not, it might be that the synchronizer uploaded the figures to Zenodo, but the whole process failed further downstream, e.g. when publishing the PDF deposition. In that case, the deposition numbers are not stored back, and a new update of the document will trigger a new upload.

Not ideal, I know, but fortunately a pretty rare issue, and one that would take quite a bit of effort to prevent altogether.

myrmoteras commented 6 years ago

from a handler point of view, just make sure that the upload of the images to BLR is finished, and then edit the article deposit metadata on Zenodo. Just to remember, especially in demos where editing is something that is good to show....

gsautter commented 6 years ago

You're aware that Zenodo side metadata edits thus far do not go back to our server, right? It's quite possible, but a good bit of effort to make happen.

On top of that, how would our server even know when to check for updates? Checking once a day won't help in a demo, and checking more frequently would generate a lot of traffic, as well as load for the Zenodo servers.