-
Notifications
You must be signed in to change notification settings - Fork 0
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
no DOI in TB :F34FFF95FE36FFCF8E76FF9AFFD3FFEB #900
Comments
Looking at the timetamps, odds are you still have this one open ... before you close the IMF, the server has no chance to acquire the lock and write the external identifiers back into the IMF, from where they propagate and also get to TB. And even after you close the IMF, there might be a little delay ... |
I closed this a while ago. but lets see tomorrow morning |
By the way, they are there now ... please wait a bit after closing an IMF before open any such tickets about externally minted identifiers ... |
patience..... at some point I will be able to sit on top of a phone pole |
Before the introduction of the coordinated external link write-back, a document wouldn't even show on Zenodo before you close it, as the uploader did the upload and DOI write-back in one go, so the current approach is by no means slower, but quite the opposite, as the export to Zenodo happens a lot earlier. |
why is there not DOI here?
https://doi.org/10.5281/zenodo.3653112
https://zenodo.org/record/3653112#.XjyEqmhKjAQ
which has this image https://zenodo.org/record/3653121#.XjyEwGhKjAQ
This is one of Piotr^s article in polish - this seems to work
The text was updated successfully, but these errors were encountered: