EBMS Tickets

I may need to retract this ticket.

When I tested this after hearing from Jeff that it did not work, I accidentally used the full text drag and drop 🙂 not the pubmed file drag and drop which explains the invalid file error.

I just tested the file again and it appears in the drag and drop box and gets successfully imported. So I cannot recreate what Jeff is experiencing when he reports that this is "still not working".

I am unable to reproduce this problem as well. I used the attached file to run successful import jobs on

• my private Docker container development site

• https://ebms.rksystems.com

• https://ebms4-dev.nci.nih.gov

I was able to get the form into a confused state by attempting to drag the file to the wrong field (as you did), at which point neither field would accept the file, but refreshing the form and starting over worked fine.

I have informed Jeff that neither of us can recreate any problem with the drag and drop feature. I asked him for more details.

My guess is that it is timing out and not finding the file which I have been able to recreate a couple times in the past on ebms4 and erc (more frequently) but it is sporadic as it works fine some days/times and fine for some files (usually smaller ones). And he has reported import times of over 4 minutes for larger files (400+) using the browse file feature.

I'll attached the breast cancer file of 473 citations if you want to give it a try. breast_REGULAR_473.txt

From Jeff:

OK, so I first tested it by importing a very small file from my PC (One Drive) and it didn’t work.

I then re-tested it, using the same file from the shared drive (T-Drive), and then it worked ok.

HOWEVER, when I tried it with a larger file (473 citations) it just kept giving me a spinning circle. I tried it on all 3 browsers (Chrome, Edge, Firefox) and it did the same thing. It also did this on the shared drive and my PC (Onedrive).

edge_recording.mp4

I created a video (edge_recording.mp4) of what happens when I try to import. While this was for a smaller file, I get the same thing for larger files. You don’t need to watch it until the end. It just does the same thing and it went on for 10 minutes and still didn’t upload it.

Well, I can see three paths available to us:

• users for whom D+D doesn't work use the Choose from folder method

• open a ticket with CBIIT to see what's different about the PC where it doesn't work

• replace the file posting interface with a simpler widget without the D+D option

I have added watchers (~vshields, ~juther, ~duganal) to widen the conversation. I don't hold a lot of hope for the CBIIT ticket option. They're likely to say (possibly correctly) that this is a browser JavaScript problem, and therefore out of their jurisdiction (it's also possible that there really are some security settings or other conflicts which are unique to this PC). On the other hand, if Jeff sees any interesting errors in the console log (Ctrl+Shift+J in Edge on Windows) when this is happening, that might open a fourth path.

I tested this again this morning and was able to recreate the issue Jeff had with the breast cancer file. I first used the Choose from Folder option and selected the breast cancer file from its location on the NCI shared drive. Upon clicking submit I got the follow message in the console:

It then spined for well over 10 minutes before I stopped it.

I then used the D+D with the same file also from the NCI shared drive and got the following message in the console:

This also spined for well over 10 minutes before I stopped it.

When I used the D+D with a copy of the breast cancer file stored on my desktop, the import was successful but I did get the following message in the console:

So this does not seem to be limited to just Jeff's PC and it is not limited to just the D+D feature.  But it seems to have something to do with where the file is stored.

In today's weekly status meeting I learned that this problem has a history which goes back for years, so it's unrelated to the rewrite of the EBMS (and likely related to the CBIIT configuration of the network shares). Victoria and Robin decided that we'll leave the interface as it is.

Closing this ticket. Will open a new ticket in the future if needed. Thanks!