Issue Number | 4298 |
---|---|
Summary | Adjusting Summary Error Threshold |
Created | 2017-08-07 16:44:53 |
Issue Type | Improvement |
Submitted By | Englisch, Volker (NIH/NCI) [C] |
Assigned To | Englisch, Volker (NIH/NCI) [C] |
Status | Closed |
Resolved | 2018-04-27 15:26:29 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.212525 |
As discussed with Margaret and Amy we want to revisit the currently enforced "Document Failure Threshold" when we're removing the CTGovProtocols from our PDQ publishing set.
Currently, we're stopping publishing if a single error for either the summaries or the CTGovProtocols has been encountered. The idea is to allow a few (maybe 2-5) errors and rather address the errors for those documents via a hot-fix, if necessary, instead of having to hot-fix all of the documents listed on the GovDelivery report.
The change would require to adjust the publishing control document (CDR178).
We wanted to adjust the number of allowable documents with
errors once we removed the CTGovProtocol documents from our publishing
job to prevent our job from failing due to a very small number of
failures.
What would you all think would be this very small number? I
suggest the number 3.
To be honest, the problem isn't as significant as it used to be due to Bob's Gauss changes which increased the speed to publish our documents dramatically. This speed increase gives us time to possibly re-run a publishing job Monday morning but it would still involve more work than just correcting and hot-fixing the small number of documents.
I've updated the error threshold from 0 to 3 in the following file:
Primary.xml
[cdr4298-maxerr ac4a1fd]
This has been copied to DEV and QA.
The changes have been copied to STAGE and PROD.
We've set the max number of summary errors to 3.
The following file has been updated:
I confirmed that the changes are on PROD. I will close the ticket after Friday's successful publishing job.
The changes have been merged into master.
Elapsed: 0:00:00.000835