From: He, Jianxiao (NIH/NCI) [C]
Sent: Friday, March 20, 2009 12:05 PM
To: Englisch, Volker (NIH/NCI) [C]; Rosenbaum, Olga (NIH/NCI) [C]; Pizzillo, Bryan (NIH/NCI) [C]
Cc: Grama, Lakshmi (NIH/NCI) [E]; Beckwith, Margaret (NIH/NCI) [E]
Subject: RE: tables in Drug Info Summaries

Volker,

 

I went through all the cases listed in your list.  Most of them are related to the XSLT transformation requirement. I found a document which lists all the requirement when I first created these XSLTs. L:\OCE\CTB\Software Development\CancerGovV2.0_Documentation_Legacy\Admin Web Site Documentation\CDRPreviewWebService\XSLT Functionality and CDR Preview Web Service.doc.

 

Here are the related part to the table.

 

Common

TableFormatter

Table

http://www.cancer.gov/cancerinfo/pdq/cam/vegetables-sun-soup

 

If Frame = All, set it to “border”.

If Frame = Bottom, set it to “below”.

If Frame = Sides, set it to “ vsides”.

If Frame = Top, set it to “ above”.

If Frame = TopBot, set it to “hsides”.

Otherwise, set it to “border”

If ColSep !=0, set rule to “cols”.

If RowSep !=0, set rule to “rows”.

Create an anchor for section.

If title exists, display in <caption>

In <COLGROUP>, for each TGroup/ColSpec, set each col width= @colwidth.

If less than 1*, set as 1*.

If equal to , set as 1*.

In <thead>, set span:

If NameEnd !='' and NameSt !='', set span as

"substring(@NameEnd,4) - substring(@NameSt,4) + 1".

Set head valign: default as middle.

Set head aling: Default as center.

 

In <tfoot>,

If only 1 row.

set span:

If NameEnd !='' and NameSt !='', set span as

"substring(@NameEnd,4) - substring(@NameSt,4) + 1".

Set foot valign: default as top.

Set foot aling: Default as left.

If more than 1 row,  create a separate table.  Style as the above-mentioned.

In <tbody>,

set span:

If NameEnd !='' and NameSt !='', set span as

"substring(@NameEnd,4) - substring(@NameSt,4) + 1".

Set foot valign: default as top.

Set foot aling: Default as left.

 

 

Is it possible for you to come up with more updated requirement for rendering table? If you take a look at DTD, there are tons of child elements inside Table element that are not rendered in the XSLTs. If you provide details, I might be able to implement them in the XSLTs.

 

Thanks,

 

 

From: Englisch, Volker (NIH/NCI) [C]
Sent: Wednesday, March 18, 2009 2:37 PM
To: Rosenbaum, Olga (NIH/NCI) [C]; He, Jianxiao (NIH/NCI) [C]; Pizzillo, Bryan (NIH/NCI) [C]
Cc: Grama, Lakshmi (NIH/NCI) [E]; Beckwith, Margaret (NIH/NCI) [E]
Subject: RE: tables in Drug Info Summaries

 

All,

 

I've created a few tables in a DrugInfo Summary demonstrating the problems we are seeing.

So far we had only noticed these problems in PublishPreview but - after publishing the document to GatekeeperGK - I noticed that the display on PublishPreview and on PreviewGK were different, too.

After putting on my thinking cap I realized that I'm using a different browser when I run Publish Preview and lo and behold, a few of the problems are only related to IE7 display issues.

 

Below is the link to the DIS Aprepitant listing all the tables and a comment for each set of problems.

     http://previewgk.cancer.gov/cancertopics/druginfo/aprepitant

 

Please let me know if you need anything else.

--
Volker Englisch
Contractor - Lockheed Martin
phone: (301) 496-0102  (CTB)
mailto:volker@mail.nih.gov

 

 


From: Rosenbaum, Olga (NIH/NCI) [C]
Sent: Tuesday, March 17, 2009 10:57 AM
To: Englisch, Volker (NIH/NCI) [C]; He, Jianxiao (NIH/NCI) [C]; Pizzillo, Bryan (NIH/NCI) [C]
Cc: Grama, Lakshmi (NIH/NCI) [E]
Subject: tables in Drug Info Summaries

Volker,

Do you have any examples of the drug info summaries with tables that did not render correctly?

Could you please provide all the details to Jay? He will try to look into it in the next couple of days and see how much work it is to enhance it.

 

Thank you

Olga