CDR Tickets

BZDATETIME::2012-09-06 14:22:08
BZCOMMENTOR::Robin Juthe
BZCOMMENT::1

Here are the requirements we agreed upon in today's meeting. I've added a few additional comments about the user interface and design of the output below.

REPORT LOGIC

1. Look at the last publishable version of each summary in the selected set. (See comments re: user interface/report options below.)

2. Apply permatarg resolution and validation software such that only publishable sections are "seen". In other words, if a proposed or approved new section has a permatarg ID associated with it, it will NOT be included in the results of this report. It will only be included if it is in publish-level markup, or not in markup at all. This is the same as for publishing filters.

3. The report should identify the name of the summary that includes a permatarg ID and the CDR ID of that summary.

4. The report should identify the name of the section title that has the permatarg ID. This section title will come from the last publishable version of the document, so it may or may not be the same title as existed in the document when the permatarg ID was originally added to the section.

5. Look at the date/time the permatarg was added. With this information, the report should identify the number of the subsequent version. The date/time the permatarg was added, the version number, and the version comment should all be provided in the report output. Moving forward, we plan to add a comment to say where the request originated in the next version made after adding the permatarg IDs. This could be a publishable or non-publishable version.

USER INTERFACE/REPORT OPTIONS

Users should have some options when running this report, although the default (for right now) could be to run the report for all summaries since there aren’t many summaries with permatargs in them. I propose that the landing page for the report contain the following options (similar to the options in the last box on the Summaries TOC lists report):

X All Summaries

Select Summary Audience
__ Health Professional
__ Patient

Select Summary Language and Summary Type

English
Select PDQ Summaries: (one or more)
__ All English
__ Adult Treatment
__ Cancer Genetics
__ Complementary and Alternative Medicine
__ Pediatric Treatment
__ Screening and Prevention
__ Supportive and Palliative Care

Spanish
Select PDQ Summaries: (one or more)
__ All Spanish
__ Adult Treatment
__ Pediatric Treatment
__ Supportive and Palliative Care
__ Screening and Prevention

REPORT OUTPUT

The report should be provided in an HTML table with the following column headings:

CDR ID
Summary Title
Section Title
Date/Time Added
Version Number
Version Comment

The results should be sorted alphabetically by summary title and then by section title.

Did I miss anything?

BZDATETIME::2012-10-23 17:38:45
BZCOMMENTOR::Alan Meyer
BZCOMMENT::2

I started making notes on this in a free moment but I'm returning to EBMS, which is higher priority. It will take several solid days of work and so will probably not be done until EBMS winds down or the priority of this is raised.

Sorry.