Issues connecting to some of the online content providers.
Opened this issue · 10 comments
I did not include any providers that require accounts to be setup.
But, I am not sure whether any of the following errors might be due to missing accounts, or licensing requirements:
Krames Staywell: Server IP address could not be found.
Clinical Key: www.elsevier.com refused to connect.
PubMed: pubmed.ncbi.nlm.nih.gov refused to connect.
Sanford Guide: webedition.sanfordguide.com refused to connect.
MicroMedex: Unable to authenticate the user with the provided credentials.
Mayo Clinic: www.mayoclinic.org refused to connect.
NOTE: We are using the Docker container image for all of our deployments and environments.
These resources require a subscription:
Krames Staywell: Server IP address could not be found.
MicroMedex: Unable to authenticate the user with the provided credentials.
Clinical Key: www.elsevier.com refused to connect.
The others are failing to load in an iFrame due how the XSLT is configured. We can change this by updating your XSLT or having you switch to a different one.
Which would be easier to perform? Updating or changing the XSLT?
Can you provide instructions on how to update / change the XSLT?
I made the following changes, but I do not see any difference:
../oib-site-lite-ui/app/tools/toolsController.js
From: xslt = '&xsltTransform='
To: xslt = '&xsltTransform=Infobutton_UI'
../oib-site-lite-ui/app/tools/OpenInfobuttonDemo.html
From: var xslt = '&xsltTransform=' + getXslt(organizationOID);
To: var xslt = '&xsltTransform=Infobutton_UI' + getXslt(organizationOID);
Please let me know if these were the correct files to change, and whether the entry I changed, was the correct entry.
Thank you.
Which copy, or copies, of the Infobutton_UI.xslt should we replace?
There are currently 6 different instances of this xslt file:
/opt/data/InfoButtons
--> find . -name Infobutton_UI.xslt
./oib-request/oib-request-service/src/test/resources/xslts/Infobutton_UI.xslt
./oib-request/oib-request-service/src/main/webapp/Infobutton_UI.xslt
./oib-request/oib-request-service/src/main/resources/xslts/Infobutton_UI.xslt
./oib-request/oib-request-service/target/infobutton-service/Infobutton_UI.xslt
./oib-request/oib-request-service/target/infobutton-service/WEB-INF/classes/xslts/Infobutton_UI.xslt
./oib-request/oib-request-service/target/classes/xslts/Infobutton_UI.xslt
And, should I revert the changes that I made previously, back to what they were initially?
Well if you're rebuilding the app, you want to replace the ones under src/main.
However, you probably just want to replace the one in the running instance in Docker.
Let's pretend that we're using the Docker container image, and let's pretend that we're using the SITE LITE GUI for demonstration and configuration purposes, and let's pretend that our backend applications are sending get requests to the URL.
Let's also pretend that we are not the developers of this application, and because of the many different directory structure branches, don't really know which branch supports the running instance that we are using.
The ../src/main/webapp and ../src/main/resources/xslts files are currently very different.
...... Which one should I replace, or should I replace both with this newly supplied variant? ......
Or, do both of the above methods described use the same directory structure variant?
Also, since you need to push the UMLS UTS login and password change to the Docker image, will this new XSLT file be included in the new Docker image?
I do have access, and I can login to the Docker image. Therefore, I can modify whichever XSLT file I need to. But, if the XSLT file is not included in the next version of the Docker image, I will need to push the XSLT file to all future Docker images.
Is there any update to this XSLT file placement?
Will this XSLT file be included in a new Docker image?