CDR Tickets

BZDATETIME::2011-11-02 10:47:22
BZCOMMENTOR::Bob Kline
BZCOMMENT::1

In some of the discussions of the menu pages we noted that it may not be appropriate for the terminology documents to carry the menu information for the summaries, in which case we would want to consider storing the menu information in the summaries themselves.

BZDATETIME::2011-11-14 11:25:20
BZCOMMENTOR::Bob Kline
BZCOMMENT::2

Can we confirm that we're just talking about the A-Z lists? The other options in the "Types of Cancer" block appear to be so much more highly customized that it's hard to picture how just adding strings to the terminology documents assigned to the summaries could have been considered as a possible solution. Also, are we trying to preserve the nested hierarchy currently present in the A-Z lists? For example:

Brain Tumor
Astrocytomas, Childhood
Brain and Spinal Cord Tumors, Childhood
Brain Stem Glioma, Childhood
Central Nervous System Atypical Teratoid/Rhabdoid Tumor, Childhood
Central Nervous System Embryonal Tumors, Childhood
Craniopharyngioma, Childhood
Ependymoblastoma, Childhood
Ependymoma, Childhood
Medulloblastoma, Childhood
Medulloepithelioma, Childhood
Pineal Parenchymal Tumors of Intermediate Differentiation, Childhood
Supratentorial Primitive Neuroectodermal Tumors and Pineoblastoma, Childhood

If we do want to preserve the nested hierarchy, is it sufficient to support a single level of nesting, or do we need to support unlimited nesting?

Here's a rough idea of a possible structure:

<Summary>
<SummaryMetaData>
:
<SummaryMenuItems type="atoz">
<SummaryMenuItem>
<SummaryMenuItemString>Brain Tumor<SummaryMenuItemString>
<SummaryMenuItem>
<SummaryMenuItemString>Astrocytomas, Childhood</SummaryMenuItemString>
</SummaryMenuItem>
<SummaryMenuItemString>Brain ..., Childhood</SummaryMenuItemString>
</SummaryMenuItem>
:
</SummaryMenuItem>
:
</SummaryMenuItems>
</SummaryMetaData>
:
</Summary>

This allows for arbitrary nesting of the menu items. Note that some of the strings in the A-Z pages don't actually have a link, so we might need to have something along these lines to indicate such a situation:

<SummaryMenuItems type="atoz">
<SummaryMenuItem>
<SummaryMenuItemString linked="N">Carcinoid Tumor<SummaryMenuItemString>
<SummaryMenuItem>
<SummaryMenuItemString>Childhood</SummaryMenuItemString>
</SummaryMenuItem>
</SummaryMenuItem>
:
</SummaryMenuItems>

Also, it appears that some of the menu items don't actually link to the top of the summary, so we might also need something along these lines:

<SummaryMenuItems type="atoz">
<SummaryMenuItem>
<SummaryMenuItemString linked="N">Carcinoid Tumor<SummaryMenuItemString>
<SummaryMenuItem>
<SummaryMenuItemString target="_124">Childhood</SummaryMenuItemString>
</SummaryMenuItem>
</SummaryMenuItem>
:
</SummaryMenuItems>

(The actual link for that example is http://www.cancer.gov/cancertopics/pdq/treatment/unusual-cancers-childhood/Patient/page5#Section_124.)

BZDATETIME::2011-11-14 11:33:11
BZCOMMENTOR::Bob Kline
BZCOMMENT::3

We'll also need a language attribute and a separate block for the Spanish strings:

<SummaryMenuItems type="atoz" lang="en">
:
</SummaryMenuItems>
<SummaryMenuItems type="atoz" lang="es">
:
</SummaryMenuItems>

BZDATETIME::2011-11-14 11:41:22
BZCOMMENTOR::Margaret Beckwith
BZCOMMENT::4

I didn't realize that it was just the full A to Z list that we were talking about creating using the menu information. I was hoping that we would be able to use this menu information to populate the menu pages for the adult and pediatric PDQ summaries: http://www.cancer.gov/cancertopics/pdq/adulttreatment and http://www.cancer.gov/cancertopics/pdq/pediatrictreatment

These menu pages are also created manually. In these lists there isn't any hierarchy (the brain tumors are dealt with by just putting Brain Tumor,...at the beginning of each title).

In terms of linking from the menu link to the summary, you are correct that we do link into the Unusual Cancers of Childhood summary since it covers a bunch of different diseases. There are probably other cases of this as well. We would want to be able to do that.

I guess I am a little confused about how this is going to be used for the mobile Web site. Maybe understanding that better would help decide how to go.

BZDATETIME::2011-11-14 12:04:16
BZCOMMENTOR::Bob Kline
BZCOMMENT::5

(In reply to comment #4)
> I didn't realize that it was just the full A to Z list that we were talking
> about creating using the menu information. I was hoping that we would be able
> to use this menu information to populate the menu pages for the adult and
> pediatric PDQ summaries: http://www.cancer.gov/cancertopics/pdq/adulttreatment
> and http://www.cancer.gov/cancertopics/pdq/pediatrictreatment

OK, we can do those, too (I was looking at "Cancers by Body Location/System" - which we hadn't been discussing - and recognized that it was very unlike the A-Z lists, which we had been discussing). So we might want to have something like:

<SummaryMenuItems type="atoz" lang="en">...</SummaryMenuItems>
<SummaryMenuItems type="ped" lang="en">...</SummaryMenuItems>
<SummaryMenuItems type="adult" lang="en">...</SummaryMenuItems>

and so on. The fact that these other pages don't have hierarchy is supported by the structure I proposed.

> I guess I am a little confused about how this is going to be used for the
> mobile Web site. Maybe understanding that better would help decide how to go.

I can imagine that since the existing menu pages are created manually, they embed assumptions about the target device that don't work on the smaller target devices, and that they would need to create pages tailored to mobile viewers. It makes sense to me that they would need the menu information supplied from which they can rebuild the mobile pages dynamically.

BZDATETIME::2011-11-14 15:59:16
BZCOMMENTOR::Bob Kline
BZCOMMENT::6

Looks like two-level nesting will not be sufficient. For example, on the Spanish page for "C":

Cerebro
Infantil
Astrocitomas
:

Also, it appears that some of the menu items have inline markup; for example: Midline Tract Carcinoma Involving <i>NUT</i> Gene. Can you give me a list of which inline markup elements we will need to support (I assume we'll want semantic markup rather than presentation markup, so <GeneName>...<GeneName> rather than <i>...</i>)?

Finally, what's the CDR ID for this summary (I can't find any summaries on Bach with "young" in the title)?

http://cancer.gov/cancertopics/aya

BZDATETIME::2011-11-15 15:11:00
BZCOMMENTOR::Bob Kline
BZCOMMENT::7

The first two spreadsheets are for the comprehensive A-Z lists. For those pages the menus are hierarchical, but the hierarchy is "implemented" by using varying numbers of leading spaces. Even wraparound of long menu items is done by putting the first part of the item's name on one line, marked up as a hyperlink, then the rest of the name on a separate line, with its own hyperlink markup and some extra leading space characters. If have captured the amount of indenting space characters in the second column of the spreadsheets, and we should be able to use that information to reconstruct the hierarchy and splice back together the menu items whose names have been broken up.

The remaining four spreadsheets are from the adult and pediatric treatment menu pages (English and Spanish). There I was able to determine what the CDR ID was for the summary (though in at least one case there was a mismatch in the URL which caused the lookup to fail).

These sheets will needs some review before we actually load the data into the summaries, and we probably still have some more discussions ahead with the cancer.gov team to make sure we know what they really need. A comment Bryan threw out in this morning's standup meeting made me suspect that when they said "A-Z lists" they weren't really referring to the comprehensive A-Z menus.

Attachment summary-menus.xls has been added with description: menu information extracted from cancer.gov a-z pages

BZDATETIME::2011-12-08 07:27:16
BZCOMMENTOR::Bob Kline
BZCOMMENT::8

At last Thursday's status meeting Bryan told us that the data I have extracted won't be used (at least for now). We'll await clarification of requirements before we proceed with any further work on this task.

BZDATETIME::2011-12-08 16:55:34
BZCOMMENTOR::Bob Kline
BZCOMMENT::9

Dropped priority at Margaret's suggestion.

BZDATETIME::2012-03-01 11:45:36
BZCOMMENTOR::Margaret Beckwith
BZCOMMENT::10

I am getting the impression that this isn't the approach that the cancer.gov team wants to take for this, so I am lowering the priority so that this issue will fall off the list. If it comes up again, we can up the priority.

The mobile team decided to take another approach so we can close this.