CDR Tickets

BZDATETIME::2012-07-13 01:00:20
BZCOMMENTOR::Alan Meyer
BZCOMMENT::1

Here is revised draft of the user perspective of how printing will work.

I'll email a copy to Bonnie, who is not currently in Bugzilla.

Attachment Printing.html has been added with description: Packet printing user perspective - Draft 2.0

BZDATETIME::2012-08-03 01:25:36
BZCOMMENTOR::Alan Meyer
BZCOMMENT::2

Here is a new draft of the user overview for printing, based on today's meeting and cogitations.

Attachment Printing.html has been added with description: Packet printing user perspective - Draft 3.0

BZDATETIME::2012-09-18 23:55:33
BZCOMMENTOR::Alan Meyer
BZCOMMENT::3

I'm writing code for the printing in EBMS and am ready to create the response sheet for a board member. Would it be possible to have the specs for that by sometime on Tuesday (Sept. 25)?

Whatever is easiest to produce is okay, either naming fields or just producing an example, e.g., in Word, together with any explanatory notes. For example, if I need to print the first, second, and last author of an article, make a note of that. If I don't understand what you've done, I'll ask questions. If its easier to print an example and pencil in the notes, that's fine too.

I suggest that we confine the response to one sheet of paper, so nobody at either the board member end or our end can miss the second page. I expect we'll be printing on both sides of the paper but it might still be safest if we can fit everything on one side of one sheet. That way a board member is less likely to miss something he should have filled out that happened to be on the back side of the page.

If there's any doubt at all about whether every article's data will fit, I suggest that we agree on a maximum length of the article title, max number of authors, and possibly use the brief journal citation instead of the full journal title.

If that doesn't work then we'll just have to print two pages.

BZDATETIME::2012-09-21 16:14:21
BZCOMMENTOR::Robin Juthe
BZCOMMENT::4

I'm attaching a document in which we have summarized our wishes with regard to printing agenda packets. We also had a few questions. I'm happy to meet and discuss. Thanks!

Attachment Printing Meeting Agenda Packets in the EBMS.doc has been added with description: Requirements for Printing Agenda Packets

BZDATETIME::2012-12-06 15:20:10
BZCOMMENTOR::Alan Meyer
BZCOMMENT::5

I finished a draft of the code for printing and have started testing (hooray!)

At some point we'll need to have a list of board members who will want printing. I'm not sure when the right time to get that is, but I just wanted to give a heads up on this since it might take some time to produce the list.

I'll arbitrarily choose some for test purposes.

BZDATETIME::2012-12-21 02:18:57
BZCOMMENTOR::Alan Meyer
BZCOMMENT::6

I've committed a working version of the program to version control.

Testing is very incomplete. There are a great many program options that have not yet been tested, but I've got basic functionality working to print individual packets, "packages" (all the packets for one board member), and full board printouts (all the packages for all of the board members who want printouts.)

The program also produces a comprehensive report of what will print (which a user can get without producing any actual printouts if desired), and a command script to be run on Bonnie's workstation to send all of the documents, in the proper order, to a network printer of her choice.

BZDATETIME::2012-12-31 23:39:17
BZCOMMENTOR::Alan Meyer
BZCOMMENT::7

I wrote the attached document because our QA testers, mainly Sridhar, need an explanation of what printing is and how it works. I tried to write it in a fairly general way so that it would also be useful to Bonnie, to board managers, and other users of the EBMS.

Attachment EBMS Packet Printing.doc has been added with description: Description of packet printing, as implemented so far.

BZDATETIME::2013-01-03 21:23:50
BZCOMMENTOR::Alan Meyer
BZCOMMENT::8

One of the objects that a user might want to print is a single packet. But there is currently no good way to identify it. The packet title doesn't work because there is no requirement that they be unique and, in fact, the 12337 packets converted from legacy data share only 127 packet titles.

For my testing I've been using the internal packet_id, which is perfect for the purpose, but, as far as I know, the EBMS user never sees the internal packet_id.

What would be a good solution to this problem?

1. Display the packet ID somewhere in the user interface so users can find it?

2. Automatically append the packet ID to the packet title, e.g.,

"Packet converted from legacy CiteMS database history (September 2012) [12336]"

3. Use the topic string and perhaps the "created at" date, e.g.,

"Toenail Cancer 2012-09-21"

Number 3 is informative, but it would not be unique if user created two packets with the same topic on the same date - which might happen, for example, if there were 20 articles on Toenail Cancer this month and it was too much for each reviewer to read all 20, so the board manager created two packets. Then we'd have to hassle with dates - or maybe just do something like what Windows does :

"Toenail Cancer 2012-09-21"
"Toenail Cancer 2012-09-21(2)"

But what if a packet contains two topics? Even if we don't do that now, we might want to later.

I'll need to make some user interface changes for printing whatever we do. I'll wait until I hear from someone who has the answer.

BZDATETIME::2013-01-04 08:46:34
BZCOMMENTOR::Robin Juthe
BZCOMMENT::9

(In reply to comment #8)
> One of the objects that a user might want to print is a single packet. But
> there is currently no good way to identify it.

Since the printing process will be automated for the most part (i.e., running as a batch job based on printing preferences), there shouldn't be a frequent need to generate a printout of a single packet. Therefore, I vote for option #1 as the least obtrusive solution. I think an ideal place to show the packet ID would be on the page listing all of the packets that have been created (in a separate column, if possible) and also on the "edit packet" page for a single packet. I would prefer not to see the packet ID in every occurrence of the packet title (e.g., in our Board members' lists) and I think relying on dates could be problematic.

BZDATETIME::2013-01-07 22:11:33
BZCOMMENTOR::Alan Meyer
BZCOMMENT::10

"PDQ" appears three times in the response sheets. It seemed a little more emphatic than we might want to put a copyright symbol after each of them, so I just did it after the first one. It's on page 2.

Please have a look. If it needs to be up a squinch or down a scrunch, or we need it after all three, please let me know.

Attachment ResponseSheetArticle268790_Mbr47.pdf has been added with description: A response sheet with a PDQ (c) symbol

BZDATETIME::2013-01-08 06:37:39
BZCOMMENTOR::Bob Kline
BZCOMMENT::11

(In reply to comment #10)
> Created attachment 2296 [details]
> A response sheet with a PDQ (c) symbol
>
> "PDQ" appears three times in the response sheets. It seemed a little more
> emphatic than we might want to put a copyright symbol after each of them, so I
> just did it after the first one. It's on page 2.
>
> Please have a look. If it needs to be up a squinch or down a scrunch, or we
> need it after all three, please let me know.

It's supposed to be the registered trademark symbol (U+00AE), not the copyright symbol.

BZDATETIME::2013-01-08 09:39:13
BZCOMMENTOR::Alan Meyer
BZCOMMENT::12

(C), (R), sometimes us bears of little brain confuse the two.

Here it is again with the registered trademark symbol.

Attachment ResponseSheetArticle268790_Mbr47.pdf has been added with description: Response sheet with a registered trademark symbol (R)

BZDATETIME::2013-01-08 11:59:37
BZCOMMENTOR::Robin Juthe
BZCOMMENT::13

(In reply to comment #12)
> Created attachment 2297 [details]
> Response sheet with a registered trademark symbol (R)
> (C), (R), sometimes us bears of little brain confuse the two.
> Here it is again with the registered trademark symbol.

The registered trademark symbol looks good. I agree with only adding it at first mention on that page.

I noticed a couple of other things on the coversheet. Maybe I should keep quiet until we have this functionality released to us for QA, but I thought I'd mention these things now in case it saves any time to resolve them beforehand (otherwise, feel free to ignore my comments until then!):

1. Display of citation. The citation should be displayed as requested in TIR #2261 (which requests changes to the online review sheet).

• Please show all authors on this page.

• Please add line breaks in between authors, title, journal, PMID.

• Please add "PMID: " before the ID#.

2. Only the summary topics that are associated with the reviewers' Board(s) should appear next to "Summary topics:". In this example, Amanda Toland should only see "Genetics of Skin Cancer".

3. The note after the third disposition ("merits revision...") is missing a closed parenthetical mark.

4. The text in the second-to-last exclusion reason contains some italicized text that shouldn't be italicized (for consistency with the rest of the page.) (I'm specifically talking about the "s" in measures and the word "used".) Picky, I know!

Thank you!

BZDATETIME::2013-01-09 00:08:46
BZCOMMENTOR::Alan Meyer
BZCOMMENT::14

(In reply to comment #13)
...
> Picky, I know!

Only perfectionists can create perfect systems.

I had hoped to look at these before I left on vacation but I've finished up some more critical stuff instead. I'll get to it when I get back.

See you all on Jan 24.

BZDATETIME::2013-01-09 00:28:06
BZCOMMENTOR::Alan Meyer
BZCOMMENT::15

The attached document gives more information about what was implemented in the packet printing software. It may be helpful as a limited substitute for a proper user manual until we can get one.

Attachment EBMS Packet Printing.doc has been added with description: High level information about packet printing for users and developers

BZDATETIME::2013-01-09 08:42:56
BZCOMMENTOR::Bob Kline
BZCOMMENT::16

(In reply to comment #15)

> High level information about packet printing for users and developers

Excellent job, thanks!

BZDATETIME::2013-01-29 12:11:53
BZCOMMENTOR::Alan Meyer
BZCOMMENT::17

I've made some minor revisions to the packet printing documentation. It now reflects where the user interface functions can be found in the EBMS and includes brief info about managing members who need printing.

Attachment EBMS Packet Printing-2.doc has been added with description: High level information about packet printing for users and developers

Future work will be done using the OCEEBMS section of JIRA.