Vandelay Queue: Export Queue As CSV in Web Client Does Not Bring Up Save File Dialog

[John Yorio]

Evergreen 3.0.11
Evergreen 3.1.5

This happens in both Chrome and Firefox.

In the web client, when you try to export a Vandelay queue to CSV (Cataloging | MARC Batch Import/Export | Insect Queue | Export Queue as CSV), the progress bar appears for a bit, like it's doing something, but then returns to the queue. You are not prompted to give the file a name or choose a location to save it.

In the XUL client, with the same queue, a confirmation dialog appears asking 'Export as "csv'?' and on clicking OK, a Save File dialog appears where you can set the file location and name.

The expectation is that the web staff client would bring up a Save File dialog, like the XUL client (I'm not sure the confirmation dialog is necessary).

[Meg Stroup (mstroup)]

We are on 3.1.5 and are affected by this bug. What follows is a cataloger's description of encountering the bug:

“When importing 135 MARC records [.mrc file] from an ebook vendor, it appeared for ~10 minutes that nothing was importing. (the bar was at 0%). I walked away from my computer and they did eventually import (~30 minutes in total).“

I just attempted to download a CSV file of the same 135 item batch that had been imported and got the following error message. Sometimes this CSV file export did not work in the client version (just timed out), but never with this error.”

[Andrea Neiman (aneiman)]

In 3.4 the option is to "Export non-imported records" and it does download an *.mrc file.

So, a couple things here:
1) is the original issue in this ticket still valid? (I say no)
2) Should there be a new ticket to allow download of the full queue as a CSV? (I say yes)

I'll bring this ticket up at Cataloging Working Group.

[Andrea Neiman (aneiman)]

Noting, because I didn't make this totally clear, that 3.4 uses the new Angular Import/Export interface.

[Ruth Frasur Davis (redavis)]

Has a new ticket been created for the export as full csv? I have not found one. It is possible that this bug has also been addressed in the Angular version of the Acquisitions Import/Export implementation of Vandelay. ???