| Issue Number | 3516 |
|---|---|
| Summary | Problem Publishing Media Document |
| Created | 2012-05-31 17:03:24 |
| Issue Type | Improvement |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Englisch, Volker (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2012-06-12 15:40:47 |
| Resolution | Won't Fix |
| Path | /home/bkline/backups/jira/ocecdr/issue.107844 |
BZISSUE::5211
BZDATETIME::2012-05-31 17:03:24
BZCREATOR::Volker Englisch
BZASSIGNEE::Volker Englisch
BZQACONTACT::Alan Meyer
I'm adding this issue to discuss on Thursday. An problem came up that could (should?) be fixed but is so rare that we may decide not to do anything about it (after all, it only happened once :-) ).
This is the situation:
On Apr-13 a new Spanish summary (CDR728604) got published but failed to
be processed on Gatekeeper. As it turned out, that summary shouldn't
have been published and the failure to successfully processing the
summary was ignored. The summary had been blocked in the CDR.
Along with the summary a new image was included in the publishing job.
This image then failed to get processed on Gatekeeper because it
belonged in the same group as the summary that failed.
Now the summary has finally been published but the image did not display because it had never been successfully published on Gatekeeper and the CDR did not submit the image again to reprocess because it was listed in the CDR as a document already published without a change.
I was able to fix the problem by re-publishing the image but I'm not exactly sure why the image wasn't pushed again to the Gatekeeper despite the fact that the load on Gatekeeper had failed.
I will try to find out more before next week.
BZDATETIME::2012-06-12 15:39:52
BZCOMMENTOR::Volker Englisch
BZCOMMENT::1
We discussed this at our last status meeting and decided not to do anything at this point. The situation that caused this problem is so rare that the effort to detect and/or correct this would far outweigh the benefits.
One thing to keep in mind when a document failed is that Gatekeeper does only display the count of "Document Status errors" on the main page which does not include dependency processing errors like the one for the Media document. This means that a Gatekeeper load with a failed document needs to be checked for possible dependency errors and these will have to be dealt with in addition to the "parent" document. In the case of the Media document we could have published the Media document independently of the summary.
If this problem comes up again in the future we can re-open the issue
and decide if it's worth it to add additional safe guards.
Closing issue for now.
BZDATETIME::2012-06-12 15:40:47
BZCOMMENTOR::Volker Englisch
BZCOMMENT::2
Setting status to closed.
Elapsed: 0:00:00.001111