EBMS Tickets

Issue Number 76
Summary Print different response sheets for the same board member, same pdf, when more than one topic
Created 2013-09-17 16:52:13
Issue Type Bug
Submitted By alan
Assigned To alan
Status Closed
Resolved 2013-09-17 16:55:40
Resolution Fixed
Path /home/bkline/backups/jira/oceebms/issue.113400
Description

OCEDRUEBMS entered 2013-07-16 by Alan Meyer (completed but could not change status)

The EBMS server packet printing software creates a response sheet for each PDF file to be sent to a board member. The filename created for the response is created by combining the document ID and the board member ID.

This works in most cases, but sometimes the board member has a packet with two or more different topics in it, and one single article happens to require review for more than one of those topics. In that case, the software creates a response sheet for the first topic and stores it with a filename composed of the document and member IDs. Then later it creates a response sheet for the second topic, but it gives it the same filename. As a result, it overwrites the first file. At printing time, the same response sheet with the same topic winds up being printed twice.

To fix this, I need to combine three IDs to make a filename, the document ID, the member ID, and the topic ID.

Until that is done, Bonnie or other staff printing packets will have to be alert to the problem and pencil in a topic ID on one of the printouts, or let the board member figure it out and do the same.

Comment entered 2013-09-17 16:55:40 by alan

This was fixed on DEV, QA and in subversion, Y branch, on Friday 2013-08-09. I think it may be in production.

Comment entered 2014-01-03 17:23:45 by Juthe, Robin (NIH/NCI) [E]

Bonnie, can you confirm that separate cover sheets are now printing for articles that are included more than once in a single packet (for different topics)? I believe this issue was fixed. Thanks.

Comment entered 2014-01-13 11:20:13 by Juthe, Robin (NIH/NCI) [E]

Bonnie and I just verified this on both QA and on production. Given that this is on production, I am closing this issue.

Elapsed: 0:00:00.000575