Note that text shown in this style documents a feature which isn't in the current release but will be in the next release and
text shown thus indicates a feature which is
being removed in the next release.
If you find anything in this documentation which is wrong or unclear then please use the link at the bottom on the page to comment and we will update the page to correct it or make it clearer.
How you display your datacards is up to you. At one level they're just another Opus article so having published the datacard you can note the article number and then link to it using the normal {NNN>link text} syntax however you sometimes want to treat the datacards as a set and display them together and that's where the Opus {deck} tag comes in.
The basic syntax is {deck:cardname} - that will give you a table containing one row per datacard and one column per fields. Twenty five rows are displayed per page so if you've got more than twenty five datacards in your "deck" of cards it will paginate it for the reader.
However this is all fairly primitive and you can tweak it in various ways.
First you can restrict which fields are shown in the table. You do this by adding an extra parameter opusorder to the datacard field definition. So long as at least one field has such a parameter the table will only show those fields with an opusorder parameter and in the order in which they are shown will be determined by the value of opusorder. So set opusorder to 1 for the field you want displayed in column 1 and so on.
Secondly there are some additional optional parameters to the {deck} tag which you add separated by colons thus:
{deck:cardname:page_size:class_prefix}
page_size lets you override the number of rows per page in the table.
class_prefix lets you override the prefixes for the classes used in the style sheet to display the table (the default is "opusdeck", see ./php/def/paperstyle.css for details).
tag
Opus 2.30 Publisher's Manual
Product Overview
Customising a Paper 
