| Issue Number | 318 |
|---|---|
| Summary | [Printing] Display All Print Jobs on View Packing Printing Jobs Page |
| Created | 2015-08-27 11:02:24 |
| Issue Type | Improvement |
| Submitted By | Juthe, Robin (NIH/NCI) [E] |
| Assigned To | alan |
| Status | Closed |
| Resolved | 2016-01-22 00:24:08 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.168657 |
The list is currently cut off and appears to only be displaying the 50 most recent jobs. It's fine to show 50 at a time, but we should have the option to scroll to view other pages or view all.
A somewhat related question:
How many print jobs OR for how long are the print jobs stored on the
server?
I've added Bob as a watcher on this issue since it touches a bit on the setup of our new DEV system.
I once commented that printable jobs stay on the server until the server is rebooted.
That turns out to be wrong. It's true for some Linux systems, but not ours. In ours a program named "tmpwatch" is invoked periodically to look for files in the /tmp directory (where our print job output files are stored) that have not been accessed in a while.
If I'm reading the configuration file correctly (/etc/cron.daily/tmpwatch) tmpwatch deletes all files that have not been accessed in more than 10 days. So the time is variable. If someone creates a print job and then, 9 days later, views the existing print jobs, they'll see the job and the data will continue to be around for a total of at least 19 days since it was created. However if they go to look at the job 11 days after it was created they're too late. It's gone.
I've started experimenting with paginating the display of the print jobs, but I'm right at the beginning of the task. It will be a bit easier when the configuration of the new server is complete with full accessibility of the fpdf package that is used in printing and is not yet installed.
I expect be in again next Monday and will work on it. If fpdf is not yet installed, I may be able to fiddle with things to work around that for my testing, or I may switch to testing on QA. I presume that, as with everyone else, a lot of CBIIT folks will be out for the holidays and that may slow things down in configuring the server.
I'm afraid that I haven't finished this and it's time for me to leave. I won't be back until after Jan. 15.
In addition to paginating the display, I'm also planning to hyperlink the job numbers if, and only if, the tar file is still on the server. So instead of entering a job number in a field at the bottom of the form, the user will be able to see that the job data does or does not have data before doing anything, and then pick the job data to recall.
It will still be the case that the current server settings normally only save jobs for 10 days after they are used.
I've left the user interfaces the same as they were on DEV and QA and plan to install the new user interface with the paging and hyperlinking when I get back.
I've completed the changes. The new version of the View Packet Printing Jobs function allows a user to view all print job information on a single page, or to see the information in pages, currently set at 25 jobs per page. It also dispenses with the text entry field at the bottom of the form and instead hyperlinks any job IDs for which data still resides on the server (typically only for 10 days after the data was generated.) Clicking the job ID retrieves the job output.
The revised functionality is currently only available on DEV.
The revised functionality is currently only available on DEV.
The new functionality is now also on both old and new QA servers.
Verified on QA SG.
Verified on PROD.
Elapsed: 0:00:00.000789