| Issue Number | 386 |
|---|---|
| Summary | Modify import from NLM to comply with NCBI changes |
| Created | 2016-06-22 09:44:29 |
| Issue Type | Improvement |
| Submitted By | Kline, Bob (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2016-08-12 16:26:03 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.186638 |
NLM has announced that they will be switching to HTTPS on September 1, and that when they do that POST requests will be broken. From their announcement:
Starting on September 1st, when you visit NCBI pages, you’ll see a green lock and https:// in the address bar instead of http://. This lets you know that you are really on an NCBI page – that our server identity is confirmed – and that your communication with our server is encrypted and private.
Here’s what to expect if you’re a general user or a scripter:
For general users
You will see the changes mentioned above – https:// and a green lock in the address bar – but you don’t have to update or change anything.You don’t need to clear your cache or update any links to NCBI pages that you’ve put on your own webpages or shared with people. We will redirect all our pages to https://.
For scripters
To keep calls from failing, use https:, not http:.Scripts that use HTTP POST to send data will not work once we transition from HTTP to HTTPS on September 1st.
If you'd like to know more about this change to HTTPS, please read The HTTPS-Only Standard https://https.cio.gov/ from the Federal Chief Information Officers website.
We currently use POST requests to retrieve articles from PubMed. According to the announcement, if we don't change the requests to use the GET verb our software will no longer work.
~henryec: Should we squeeze this into the 3.3 release or try to get another mini-release done with CBIIT to take care of this? It would have to be done no later than 1 September in order to avoid disrupting the PDQ board work.
I have this implemented on DEV and I believe I have tested all the paths (imports, links to abstracts, journal info updates, check for missing PMIDs, etc.). I had to suppress certificate checking, as our PHP/curl are too old to work properly. It would be good if you could do a little poking around, ~JutheR (and perhaps have the librarians do an import or two).
(Note: not everything we did on QA yesterday as we were refining the editor has been backported to DEV, because I want to do that as part of another test of the deployment script, but not until after we've decided whether to fold this ticket into the current release. So don't be alarmed if some of the recent tweaks for other release tickets aren't on DEV right now.)
I'm testing what I hope is the final version of the 3.3 deployment script on DEV. Expect a little down time.
Deployment script appears to have worked correctly on DEV. Running it on QA now (that will bring the changes for this last ticket — which has been added to the release — to that tier).
I've imported a few citations on DEV and it seems to be working fine. Since it sounds like we're close to getting this fix onto QA, I'll ask Minaxi and Cynthia to take a look there when we're ready. Thanks.
Ready on QA. As soon as you let me know they're finished I'll submit the ticket for CBIIT to deploy 3.3 to STAGE.
Will do. I tried a few imports on QA, too, and so far, so good.
From Minaxi:
"I have tested importing two batch files and 3 individual citations. All
citations imported correctly."
I think we can proceed.
This is working well so far on PROD, but I'd like to keep this open until Sept 1 (when the NLM change goes into effect) just to be sure.
Elapsed: 0:00:00.000648