Data can currently be exported to a comma separated values (csv) file which can be opened or imported by Excel, Access and most other systems for handling structured data. Data can be exported for all 'Action Editions' within a 'Campaigning Action' or individuall for each 'Action Edition'.
The exact fields that are included in the export file are specified in the 'datafile' script. This can be set site-wide (tested) or at the action or action edition level (untested). If you have multiple languages, you need to ensure that language is set for each 'Action Edition' so it appears in the data export file.
To specify what data the download should contain, simply customise the 'fields' list in the 'datafile' file with the field ids that match what is in the action schema. This can be done on the file system (ecampaigning_scripts/datafile.py) or customised via the ZMI (portal_skins/ecampaigning_scripts/datafile). To specify a export for a particular Action or ActionEdition?, simply put the datafile specification in the appropriate folder (untested).
To specify the column header labels, add the appropriate msgids to the 'ecampaigning' .po files in the /eCampaigning/i18n/ folder on the Zope instance (filesystem access required). For each language, simply add the msgids to the appropriate .po file as usual. Data header msgids are auto-generated based on the pattern 'header_dataexport_record_XXXX' where XXXX is the field id from the schema.
[OnlineHelp]?
