missing related item from treatment to article

[myrmoteras]

see also https://github.com/plazi/Biodiversity-Literature-Repository/issues/91

in this case, there is the link from the treatment to the article deposit missing. https://zenodo.org/record/4470008

Also there are only few of the 366 treatments included in BLR so far, and neither the article per se. https://zenodo.org/communities/biosyslit/search?page=1&size=20&q=%2210.11646%2Fzootaxa.4919.1.1%22 see also http://tb.plazi.org/GgServer/dioStats/stats?outputFields=doc.articleUuid+doc.gbifId+doc.zenodoDepId+cont.treatCount&groupingFields=doc.gbifId+doc.zenodoDepId&FP-doc.articleUuid=D94BFFF8813AFFDE7016D56B781FFFE2&format=HTML

Besides this, @gsautter mentions that it will take a time to create these networks of links.

• Do you have an idea how long this takes? The article went through QC yesterday night (11 hours ago) and is not here.
• Is there a way to see what is being or how far such processing has been progressed? This would help to avoid unnessary questions and understand when the process is finished so the article can be used and announced in public eg Twitter.

[gsautter]

Nothing pending ... just a few transit problems: https://tb.plazi.org/GgServer/dtpStats/stats?outputFields=doc.docUuid+doc.updateDate+problems.detailId+problems.detailLabel+problems.transSource+problems.transDest+problems.probSource+problems.probType+problems.probDescription&groupingFields=doc.docUuid+doc.updateDate+problems.detailId+problems.detailLabel+problems.transSource+problems.transDest+problems.probSource+problems.probType+problems.probDescription&orderingFields=problems.detailLabel&FP-doc.docUuid=D94BFFF8813AFFDE7016D56B781FFFE2%20&format=HTML

Apparently, DOI 10.11646/zootaxa.4919.1.1 already is in Zenodo, which blocks upload of the article proper (as well as the figures if there were any) ... even though I cannot seem to find anything under this DOI other than our 16 treatments ... that said, hard to tell who this deposition belongs to, but the API definitely complains the DOI is already there.

[flsimoes]

Nothing pending ... just a few transit problems: https://tb.plazi.org/GgServer/dtpStats/stats?outputFields=doc.docUuid+doc.updateDate+problems.detailId+problems.detailLabel+problems.transSource+problems.transDest+problems.probSource+problems.probType+problems.probDescription&groupingFields=doc.docUuid+doc.updateDate+problems.detailId+problems.detailLabel+problems.transSource+problems.transDest+problems.probSource+problems.probType+problems.probDescription&orderingFields=problems.detailLabel&FP-doc.docUuid=D94BFFF8813AFFDE7016D56B781FFFE2%20&format=HTML

Apparently, DOI 10.11646/zootaxa.4919.1.1 already is in Zenodo, which blocks upload of the article proper (as well as the figures if there were any) ... even though I cannot seem to find anything under this DOI other than our 16 treatments ... that said, hard to tell who this deposition belongs to, but the API definitely complains the DOI is already there.

This is actually related to https://github.com/plazi/Biodiversity-Literature-Repository/issues/96

[gsautter]

Regarding the waiting time, what you are basically asking is an external means of monitoring the work queues ... this is a pretty hard thing to implement, considering we number of queues we have for data exports alone. Plus, given that the only really slow export is the one to going Zenodo (pretty much everything else is pretty much instantaneous, unless there is really heavy traffic as in half a dozen monographs coming in at the same time), this would only ever be relevant to Zenodo.

And there is an easier way of checking the Zenodo export status readily available:

• check the transit stats at https://tb.plazi.org/GgServer/dtpStats to see if any exports bound for Zenodo have problems listed
• check the article stats at https://tb.plazi.org/GgServer/dioStats to see if there already is a Zenodo deposition number

If the former comes up empty (or empty regarding Zenodo), the export is still in progress or waiting in the queue. If the latter comes up without a deposition number, write-back is still pending, or the export is still in progress or waiting in the queue, or there was an error. This is pretty much what I actually check for questions like this one ... and this data is open to all of you ... so, please, at least check the error statistics before you start opening a ticket ... odds are there will be a problem listed in the very most cases at least an hour or so after upload (rule of thumb being an expected delay of about 10-15 seconds per treatment, as that is how long the upload of one takes).

[myrmoteras]

Nothing pending ... just a few transit problems: https://tb.plazi.org/GgServer/dtpStats/stats?outputFields=doc.docUuid+doc.updateDate+problems.detailId+problems.detailLabel+problems.transSource+problems.transDest+problems.probSource+problems.probType+problems.probDescription&groupingFields=doc.docUuid+doc.updateDate+problems.detailId+problems.detailLabel+problems.transSource+problems.transDest+problems.probSource+problems.probType+problems.probDescription&orderingFields=problems.detailLabel&FP-doc.docUuid=D94BFFF8813AFFDE7016D56B781FFFE2%20&format=HTML

Apparently, DOI 10.11646/zootaxa.4919.1.1 already is in Zenodo, which blocks upload of the article proper (as well as the figures if there were any) ... even though I cannot seem to find anything under this DOI other than our 16 treatments ... that said, hard to tell who this deposition belongs to, but the API definitely complains the DOI is already there.

@gsautter can you fix this, or do we need to talk to @slint ?

[gsautter]

@gsautter can you fix this, or do we need to talk to @slint ?

I'm afraid this is for @slint to fix, as I cannot remove the DOI from a deposition via the API or web UI ... would be enough to remove the DOI proper from the deposition, but deleting the deposition altogether would also do. Either way, we need to clean this up on our end es well (including the deposition number if the deposition is deleted altogether).