| Issue Number | 3205 |
|---|---|
| Summary | White Paper on Tables |
| Created | 2010-08-12 18:13:52 |
| Issue Type | Improvement |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Osei-Poku, William (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2015-12-17 15:02:30 |
| Resolution | Won't Fix |
| Path | /home/bkline/backups/jira/ocecdr/issue.107533 |
BZISSUE::4893
BZDATETIME::2010-08-12 18:13:52
BZCREATOR::Volker Englisch
BZASSIGNEE::Volker Englisch
BZQACONTACT::William Osei-Poku
Per discussion at the status meeting and based on input from board managers it might be useful to create a white paper on how to create, edit, and update tables in XMetaL and how to fix problems. One aspect of this document should specifically focus on the output created by Cancer.gov's conversion into HTML tables and the differences when viewing the tables in different browsers.
The idea is to create this document as the ultimate "Table Bible".
BZDATETIME::2011-12-30 16:13:52
BZCOMMENTOR::Volker Englisch
BZCOMMENT::1
Changing priority to P8 per status meeting.
Are we still planning to do this? Would William be the best person to create this document, or Volker? Would it be appropriate to assign this ticket the status of "On Hold"?
The users had requested something like this when there were staff changes and they had a phase of many table problems. 90% of the problems can be tracked down to adding a table column and spanning across table rows. The system inserts a table between col1 and col2 with the id col02. The fix is usually to rename col2 -> col3 and col02 -> col2.
I'm not sure this information is worth a "paper". :-)
Again, I don't know which documentation CIAT is using when working with
tables. We may want to have William (or me) include this info or create
a wiki page but we shouldn't keep the issue around.
Our estimate of this assumes that William will be able to furnish a lot of the material and that he and Volker will collaborate on a final document.
I passed this ticket on to William as he is in the process of creating the user documentation to attach to this issue.
Decided in status meeting that we won't do this.
Elapsed: 0:00:00.001692