Extension:TableEdit/Details

...using a template
 Template:PageName 
 * The name of the template should be put in-between the tags, including the Template: prefix. See the section below for defining a template.

...without a template
 Heading1 Heading2 Heading3 So Forth... 


 * Put the headings for the row/columns you want to create in-between the tags. You must specify a heading for a column.

Template Definitions
TableEdit is extensively template-driven. Most of the tables on EcoliWiki.net are managed by templates, meaning all the information about the table is defined in a wikipage in the Template namespace. This includes all the headings, the heading-styles, if the table is horizontal or vertically oriented, and other variables.

 
A newline (carriage-return) delimited list of the headings.


Sets the default style for the headings. This code gets inserted into the   tag in the following manner:

'heading_style. '>'

 

 * 0 indicates a vertical-type table -- with the headings going across the page left to right.
 * 1 indicates a horizontal-type table -- with the headings running down the left side of the table.

 </tt>

 * This text shows up above the box view on the general view and when you edit a row.

 </tt>

 * Above the table on the general view when you are editing a table.

 </tt>

 * Below the table on the general edit view.

 </tt>

 * On the very right hand side when you edit a row.

 </tt>

 * Text (HTML? wikitext?) goes inbetween these tags. It gets put right above the table in the wiki page.

 </tt>

 * This is the counterpart to  </tt> tag. The text in this field gets put right below the table in the wiki page.

Example
Standard name Mnemonic Synonyms </heading_style> 1
 * Here is the Template:Gene_nomenclature_table from EcoliWiki.

Qualifier||qualifier|select| |NOT|Contributes to|Colocalizes with|Obsolete GO term|Under review GO ID||go_id|text GO term name||go_term|lookupcalc|SELECT page_title FROM GO_archive.term WHERE go_id = '' ORDER BY term_update DESC LIMIT 1|page_title|split|_!_|1 Reference(s)||refs Evidence Code||evidence|select| |IC: Inferred by Curator|IDA: Inferred from Direct Assay \ with/from||with|text Aspect||aspect|lookup|SELECT namespace from GO_archive.term WHERE go_id = '' ORDER BY term_update DESC LIMIT 1|namespace Notes||Notes Status||status|calc|reqcomplete|go_id|refs|go_term|evidence </heading_style>
 * Here is a more complicated example that makes use of column-rules. This comes from Template:GO_table_product in EcoliWiki. Long lines have been broken and have a backslash to indicate an inserted line-break.
 * IEA: Inferred from Electronic Annotation|IEP: Inferred from Expression Pattern \
 * IGC: Inferred from Genomic Context|IGI: Inferred from Genetic Interaction \
 * IMP: Inferred from Mutant Phenotype|IPI: Inferred from Physical Interaction \
 * ISS: Inferred from Sequence or Structural Similarity|ISO: Inferred from Sequence Orthology \
 * ISA: Inferred from Sequence Alignment|ISM: Inferred from Sequence Model \
 * IGC: Inferred from Genomic Context|RCA: inferred from Reviewed Computational Analysis \
 * TAS: Traceable Author Statement|NAS: Non-traceable Author Statement \
 * ND: No biological Data available|NR: Not Recorded

Column Types / Column Rules
This is defined in TableEdit::apply_column_rules.

<ul> <li>

select</tt>
</li>

<li>

checkbox</tt>
</li>

<li>

text</tt>
</li>

<li>

lookup</tt>
</li>

<li>

calc</tt>
</li>

<li>

lookupcalc</tt>
</li>

<li>

timestamp</tt>
</li>

<li>

foreign</tt>
The foreign table type allows you to show data from another table/row in a table. This was originally created for the Quickview Tables on EcoliWiki. We needed a way to mirror the data from the Gene and Product pages on the Quickview page dynamically, so the user wouldn't have to edit the same information in two different places. The specification goes as follows:

Heading_to_show||column_name|foreign|foreign_page|foreign_table_template|foreign_heading

Anything in italics should be changed. For gene pages we needed a way to tell the table to look on the corresponding gene/product page, so we added the <tt></tt> magicword. For example, the following line would pull information from the nomenclature table on the corresponding Gene page. (If this was used on the lacZ:Quickview page, it would pull from the lacZ:Gene page.)

Gene Synonym(s)||syns|foreign|:Gene|Gene_nomenclature_table|Synonyms

The code executes in the following manner:
 * 1) sets a row property specifying this is a foreign row
 * 2) breaks the definition (coming from the template) into variables
 * 3) does  magic word processing
 * 4) uses variables to search the database for the corresponding foreign row/box
 * 5) creates a box object from the returned database info
 * 6) crawls through the box, and when the right row is found, it saves the foreign row_data to this row_data
 * 7) looks for any existing relations in the db
 * 8) if none are found, it creates a relation in the db
 * 9) creates display version & raw version to be shown in the view
 * 10) returns view string

</li> </ul>

Object Classes
TableEdit has undergone major changes trying to make it more like the MVC model. This cannot always be accomplished due to programmer style and historical reasons, but where possible we've tried to seperate the three.

<tt>wikiBox</tt>
A <tt>wikiBox</tt> object consists of a series of attributes that control the behavior and appearance of the table and a collection of row objects that hold the actual data. The <tt>wikiBox</tt> also has methods to manipulate rows, serialize and unserialize its contents, and for interacting with the MySQL database that controls the tables. Most of the manipulation of the tables can be done through this method. It (not so transparently) handles the wikiBoxRow objects (see below.)

<tt>wikiBoxRow</tt>
A <tt>wikiBoxRow</tt> object holds the actual data. This is also defined in <tt>class.wikiBox.php</tt>. The <tt>wikiBoxRow</tt> has methods for loading and saving etc. This class also carries methods that cannot/are not called from class wikiBox, such as the methods dealing with the relations database table (<tt>ext_TableEdit_relations</tt>.)

<tt>TableEdit</tt>
class <tt>TableEdit</tt> is defined in <tt>SpecialTableEdit.body.php</tt> and is an extension of the MediaWiki <tt>SpecialPage</tt> class. However, it can be invoked without generating a special page to handle interactions between <tt>wikiBox</tt>es and Article objects in MediaWiki.

<tt>wikiBoxMetadata</tt>, <tt>wikiBoxRowMetadata</tt>, <tt>tableEditMetadata</tt>
These classes are defined in <tt>class.wikiBox.php</tt> and handle the saving and retreiving of metadata from their respective database tables.

<tt>TableEdit_Loader</tt>
Defined in <tt>class.loader.php</tt>, this class is devoted to loading data into pre-existing tables. There is a whole page devoted to the loader, with all the options and usage explained there.

Semantics
Don't know what people are talking about? Brush up on the TableEdit lingo and impress your friends.

table

 * 1) The table as displayed when you first visit a wiki page.
 * 2) A table in the database that stores data. (Ex. ext_TableEdit_box or ext_TableEdit_relations.)

box/box object

 * 1) The complex data structure representing the table. This consists of an object with sub-objects/arrays, etc.
 * 2) Sometimes used in place of "table."