The configuration of a custom XSL transformer is described here.
The TableStar XML schema describes the XML structure of the TableStar XML for matches and data tables.
The following table leads to the documentation of the different schema versions.
|Table Schema Version||Documentation||Changes|
|1.1||https://www.subshell.com/tablestar-import/1.1/index.html||Allows the import of data tables.|
Via the import of matches you can add matches to an existing match round in an automated manner. Please see the following examples with explanations for further information.
tablestar.import.matchrounds.blacklistconfiguration key. Further explanation on how to configure this list is described here.
Via the import of data tables you can replace content rows of an existing data table in an automated manner. Please see the following example with explanations for further information.
The usual work flow would be to prepare a data table document with a data table containing just the header row, e.g.:
|Tore||Name||Name [KURZ]||Verein||Verein [KURZ]|
You also have to specify an import ID in the appropriate property on the 'Import' tab of the data table document. The ID must match the ID in the incoming XML in order for the import process to decide which data table contents will be replaced by the incoming content rows.
For the installation of the Sophora Importer, please visit its appropriate documentation.
In order to use the TableStar schema and transformations you will have to do the following steps:
- Include the
tablestar-import-shaded.jarinto your Sophora Importer installation (see
sophora.importer.additionalClasspathin the Sophora Importer documentation). The JAR already contains the schema files.
- Copy the TableStar Import transformation files (xsl folder) to a place of your choice and declare its path in your Sophora Importer instance configuration (see
sophora.importer.directory.xslin the Sophora Importer documentation). The folder structure within the xsl folder must be retained!