A an author, I want to be able to see the title and legend for a table so that I can check the content is correct.
As an author, I want to be able to edit the title and legend for a table so that I can correct any errors.
As an author, I want to be able to add a reference or asset citation to a table title or legend so that I can cite other articles or items in this context.
As an author, I want to be able to add, edit or remove equations in a table title or legend so that I can include mathematical content.
As an author, I want to be able to add new rows and columns to a table so that I can add new content.
As an author, I want to be able to remove rows and columns from a table so that I can remove content.
As an author I want to be able to add text to new cells so that I can add new content.
As an author, I want to be able to edit or remove the existing content in a cell so that I can correct any errors.
As an author, I want to be able to paste multiple cells copied from a spreadsheet into a table so that I can add new content in bulk.
As an author, I want to be able to add, edit or delete a reference or asset citation in the content of a cell so that I can cite other articles or items in this context.
As an author, I want to be able to add, edit or delete an equation in the content of a cell so that I can include mathematical content in a table.
As an author, I want to be able to apply style formatting (bold, italic etc) to the content in a cell so that I can add emphasis.
As an author, I want to be able to remove style formatting from the content in a cell so that I can remove emphasis.
As an author, I want to be able to add and remove style formatting across multiple cells at once so that I can make mass formatting changes in a table.
As an author, I want to be able to set the vertical and horizontal alignment of content in one or more cells so that I can improve the readability of the table.
As an author, I want to be able to designate one or more rows as header rows so that I can indicate the headings for my table.
As an author, I want to be able to remove header row status from one or more rows so that I can correct errors.
As an author, I want to be able to merge two or more cells into cells that cross rows and/or columns so that I can improve the readability of the table.
As an author, I want to be able to unmerge cells that cross rows and/or columns so that I can improve the readability of the table.
Production staff
As production staff, I want to be able to add a new table so that I can capture missing content.
As production staff, I want to be able to chose whether a new table should be a main table (label, title and legend) or an inline table (just the cells and footnotes) so that I can pick the most appropriate option for the content.
As production staff, I want to be able to add a title to a new table so that I can describe the content.
As production staff, I want to be able to add a legend to a new table so that I can describe the content.
As production staff, I want to be able to remove a table so that I can correct errors.
Érudit
As production staff, I want to be able to add an image to represent a table so that I can capture table content supplied in this manner.
As production staff, I want to be able to repalce the image representing a table so that I can correct any errors.
As production staff, I want to be able to add an attribution to a table so that I can acknowledge the source of the content.
As production staff, I want to be able to edit the attribution for a table so that I can correct any errors.
As production staff, I want to be able to remove the attribution for a table so that I can correct any errors.
But what if . . . ?
Considerations
Labelling. eLife currently allows unlabelled tables, labelled tables (Table 1, Table 2 etc) and a special case labelled table (Key resources table). Unlabelled tables won't have titles or legends and are generally used by authors to give shorter sets of data.
We need to support header rows at any point in the table, not just the first row(s).
eLife currently uses the @position attribute for tables, with two different values - either 'float' (for main tables) or 'anchor' (for inline/unlabelled tables). The idea was to fix inline tables at certain points in the text and to allow main tables to move about. This, however, is mostly a PDF issue the attributes may not be needed for this.
PKP use both @postion and @orientation attributes, wtih @orientation being required in PDF generation.
XML requirements
Tables are captured using table-wrap. table-wrap may or may not have a child label element. Similarly they may or may not have a caption or title.
A table-wrap may have the attributes @position and @orientation, which are generally used for the purposes of PDF generation. Typical values are position="float", position="anchor", orientation="portrait", orientation="landscape".
Every table-wrap should contain one and only one table element. This table element may have a thead or a tfoot, and must have a tbody. Rows are determined by the element tr which can contain th and td elements. th must be allowed as a descendant of both thead and tbody, whereas td should be allowed as a descendant of tbody and tfoot.
The @colspan attribute can be used in order to specify if a th/td spans more than one column. The @rowspan attribute can be used in order to specify if a th/td spans more than one row. The @align attribute can be used in order to specify th/td data horizontal alignment. The @valign attribute can be used in order to specify th/td data vertical alignment.
The break element should be used in order to add line breaks within th/td elements.
Tables within an article.
User Stories
Author
Production staff
Érudit
But what if . . . ?
Considerations
@positionattribute for tables, with two different values - either 'float' (for main tables) or 'anchor' (for inline/unlabelled tables). The idea was to fix inline tables at certain points in the text and to allow main tables to move about. This, however, is mostly a PDF issue the attributes may not be needed for this.@postionand@orientationattributes, wtih@orientationbeing required in PDF generation.XML requirements
Tables are captured using
table-wrap.table-wrapmay or may not have a childlabelelement. Similarly they may or may not have a caption or title.A
table-wrapmay have the attributes@positionand@orientation, which are generally used for the purposes of PDF generation. Typical values areposition="float",position="anchor",orientation="portrait",orientation="landscape".Every
table-wrapshould contain one and only onetableelement. Thistableelement may have atheador atfoot, and must have atbody. Rows are determined by the elementtrwhich can containthandtdelements.thmust be allowed as a descendant of boththeadandtbody, whereastdshould be allowed as a descendant oftbodyandtfoot.The
@colspanattribute can be used in order to specify if ath/tdspans more than one column. The@rowspanattribute can be used in order to specify if ath/tdspans more than one row. The@alignattribute can be used in order to specifyth/tddata horizontal alignment. The@valignattribute can be used in order to specifyth/tddata vertical alignment.The
breakelement should be used in order to add line breaks withinth/tdelements.Example of PKP content:
The following elements should be allowed as children of
th/td:bolditalicsupsubscunderlineext-linkxrefbreaknamed-contentpreformatcodeinline-graphicinline-formulalistpÉrudit example
Érudit capture tables as images:
Published HTML
Mock ups
This is not required, but if you have mock ups of what you would like to see please provide them here.
Proposal
This will be added by the Texture team after the feature request is discussed and agreed.