EBMS Tickets
| Issue Number | 580 |
|---|---|
| Summary | [Import] Problem importing internal articles on PROD (and QA) |
| Created | 2020-10-15 21:49:14 |
| Issue Type | Bug |
| Submitted By | Juthe, Robin (NIH/NCI) [E] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2020-10-19 15:44:41 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.276664 |
Minaxi reported that she was unable to import an internal article (PMID: 32646415). Here is a document with the error message she received:
EBMS internal article import error.docx
From the looks of it, I thought it might be an issue on NLM's side. However, when I tried to import the same article to replicate the problem, I received an entirely different EBMS-related error message. That's in the screenshot below.
EBMS internal error v2 - RJ.docx
It appears there may be a problem with the import of all internal articles, possibly related to the date the tag was added. I replicated this finding (received the same EBMS error message) on QA with the same article and another article (PMID: 33043810). I haven't been able to replicate Minaxi's error message which makes me think it was likely a temporary NLM issue.
I see what the problem is. You should hold off on importing internal articles until I come up with a fix. When I do we'll get CBIIT to apply it as a hotfix patch.
I have a fix on DEV, ready for you to test.
Verified on DEV. Thank you!
Installed on QA.
~juther, if you can confirm that this is working on QA, I'll put in a ticket to have it deployed to production.
This looks good on QA. Thanks!
~juther It's on STAGE (https://ebms-test.nci.nih.gov). I'm doing a little test, but do you want to test there as well before I have them do PROD? Also, tell me if Jira notifies you of this comment, please.
I did get the notification! However, I just tried importing an internal article and received notification that it was imported with errors (see below) and it is not in the internal article queue. I will try another article to see if there was some problem with the example I selected (PMID 33111460).
I just imported another one with the same result - "article with errors" (PMID 33111348).
Yeah, I hit the same problem when I first tested, because I had gone into PubMed, searched for "liver cancer," switched the display to order them most recent first, and grabbed the top one. A brief moment of panic until I remembered that one of the facts of life we now deal with is that NLM now returns records in the search results which aren't yet ready for retrieval (we've documented this problem in other tickets). So I grabbed one which wasn't so hot off the presses and it worked fine.
Can you try one that's not so recently added? 33111348 has an
EDAT of tomorrow. 🙂
EDAT- 2020/10/29 06:00
It worked with an older citation (PMID 31654418).
~juther this has been deployed to production. I'll tell Tracy to go ahead and close the ServiceNow ticket, but let me know if you run into any problems with internal imports and we'll regroup.
This is working well on PROD. Thank you!
| File Name | Posted | User |
|---|---|---|
| EBMS internal article import error.docx | 2020-10-15 21:42:26 | Juthe, Robin (NIH/NCI) [E] |
| EBMS internal error v2 - RJ.docx | 2020-10-15 21:44:00 | Juthe, Robin (NIH/NCI) [E] |
| image-2020-10-28-10-23-37-633.png | 2020-10-28 10:23:38 | Juthe, Robin (NIH/NCI) [E] |
Elapsed: 0:00:00.000633