CDR Tickets

As far as I can tell, there is no interface for generating mailers for editorial board members. Is this right? I guess that would mean we can retire all the LaTeX software.

Collecting my questions in one place.

1. Can we retire the LaTeX software completely?

2. Should the required Mode attribute be Mail or Web-based?

3. If we don't use the publishing system, should we modify the schema to make the Job element optional, or use 0 for its value?

4. What should the value of the Deadline element be?

5. Should Sent still be the date the tracking document was generated?

6. Or should some different document type be used for this?

Over to you, Robin, for these questions.

While you're mulling over these questions, I'm going to try and get as much tentative work done on the ticket as I can, going with the assumptions that

• We'll keep the Mailer document type

• I can leave out the JobId element (I just realized it's already optional)

• The other answers can easily be plugged into whatever I've put together when I get them

Sorry for all the noise. I worked out the obvious answers for most of my questions. The enhancement has been implemented on DEV. One of the advantages of the new approach is that you can test more freely, not having to worry about adding jobs to the publishing table or LaTeX mailers added to the file system.

I used Web-based as the value for the Mode attribute, but we may want to consider the new value Tracker to reflect this new usage of the Mailer document type. And I still need confirmation that the LaTeX software can be removed from the servers.

I've added my responses to your questions below.

Collecting my questions in one place.

1. Can we retire the LaTeX software completely? RJ: Yes, we can retire it as long as this isn't used for the mailers sent to the genetics professionals. We no longer need to generate summary mailers (Ed Board mailers were removed several years ago).

2. Should the required Mode attribute be Mail or Web-based? RJ: Web-based sounds good to me.

3. If we don't use the publishing system, should we modify the schema to make the Job element optional, or use 0 for its value? RJ: I don't see any reason to keep this number. It sounds like you came to the same conclusion. 🙂

4. What should the value of the Deadline element be? RJ: I don't know what this means.

5. Should Sent still be the date the tracking document was generated? RJ: Yes.

6. Or should some different document type be used for this? RJ: The same document type is fine for now. Thanks!

Over to you, Robin, for these questions.

This is looking good on QA but could you please remove blocked summaries from the list of available summaries for which to generate mailer tracking documents? Thanks.

Could you give me an example of a blocked summary for which a tracking document is generated? I don't believe the logic for selecting the summaries has changed.

False alarm! The Peds summary Genomics of Thyroid Cancer*BLOCKED* [Module];Treatment;Health professionals has mailer tracking documents generated, but the document is not actually blocked in the system (just has that manually appended to the title).

Verified on QA.

Sorry, but it turns out I spoke too soon. Upon logging out of QA, I was presented with a very large message about checked-out documents. Apparently the mailer tracking software is checking out all of the mailer tracking docs to whomever generated them, which would mean only that person could check in the responses. The mailer tracking documents should be created but automatically checked back in.

Sorry about that. Fixed on QA, I think. I have unlocked the mailers. I will add the fix to the deployment package and apply it to DEV after you have tested on QA and confirmed that the fix is correct.

Looks good on QA. Thanks!

Verified on PROD.