This document is intended for technical staff creating imports to Signifikant Platform and describes the Signifikant Simplified XML import format.
...
Info |
---|
The import.config is automatically generated when Manager is started the first time. The location is C:\ProgramData\Signifikant\Assert\ |
Sample import.config
Transformation
Transformation configuration is holding list of transformation styles which may transform files from one format to an other format.
Transformation configurations
Code Block |
---|
<TransformationConfigs>
<TransformationConfig src="C:\ProgramData\Signifikant\Assert\htmlDocumentStyle.xsl" name="htmlDocumentStyle" transformTo=".html" />
</TransformationConfigs> |
In TransformationConfigs section we can specify multiple transformation styles sheets which may transform document from one type to an other. For example, from xml format to html format.
The src attribute represents the path where the transformation style sheet is located. We can assign identification name to style sheet by giving a name in name attribute. The transformTo attribute represents to which format this transformation will transform.
Sample import.config
Code Block | ||
---|---|---|
| ||
<Configurations> <TransformationConfigs> <TransformationConfig src="C:\ProgramData\Signifikant\Assert\WindchillXml.xsl" name="WindchillXml" transformTo=".xml" /> <TransformationConfig src="C:\ProgramData\Signifikant\Assert\signifikant_signifikantToXliff.xsl" name="SignifikantToXliff" transformTo=".xml" /> <TransformationConfig src="C:\ProgramData\Signifikant\Assert\signifikant_signifikant_to_signifikantSimplified.xsl" name="SignifikantToSignifikantSimplified" transformTo=".xml" /> <TransformationConfig src="C:\ProgramData\Signifikant\Assert\signifikant_xliffToSignifikant.xsl" name="XliffToSignifikant" transformTo=".xml" /> <TransformationConfig src="C:\ProgramData\Signifikant\Assert\signifikant_signifikantsimplifiedToSignifikant.xsl" name="SignifikantSimplifiedToSignifikant" transformTo=".xml" /> <TransformationConfig src="C:\ProgramData\Signifikant\Assert\SSXExport_parts.xsl" name="SSXExport_parts" transformTo=".xml" /> <TransformationConfig src="C:\ProgramData\Signifikant\Assert\SSXExport_assemblies.xsl" name="SSXExport_assemblies" transformTo=".xml" /> <TransformationConfig src="C:\ProgramData\Signifikant\Assert\SSXExport_hotspots.xsl" name="SSXExport_hotspots" transformTo=".xml" /> </TransformationConfigs> <XmlConfig> <ExportBasePath>D:\Assert\Export</ExportBasePath> <ImportBasePath>D:\Assert\Import</ImportBasePath> <StyleSheetsBasePath>C:\ProgramData\Signifikant\Assert</StyleSheetsBasePath> <!-- When new presentations are imported they will get this item status. The item status has to be defined in itemstatus.config. --> <InitialItemStatusList> <InitialItemStatus base-type="Part" initial-value="NEW" /> <InitialItemStatus base-type="Catalogue" initial-value="NEW" /> <InitialItemStatus type-code="Kit" initial-value="NEW" /> </InitialItemStatusList> <ImportSetting> <UseCache>false</UseCache> <LoadCache>false</LoadCache> <StopOnError>false</StopOnError> <MailEnabled>true</MailEnabled> <MailFromManager>true</MailFromManager> <MailFromAPI>true</MailFromAPI> <MailAtSuccess>true</MailAtSuccess> <MailAtFailure>true</MailAtFailure> <MailSender>noreply@domain.com</MailSender> <MailRecipient>admin@domain.com</MailRecipient> <!-- If no language specified, use this --> <DefaultTextLanguage>en-US</DefaultTextLanguage> <!-- Do not allow to create new languages at import --> <AutoAddNewLanguage>false</AutoAddNewLanguage> <!-- New specification types cannot be created at import --> <AllowNewSpecificationTypes>false</AllowNewSpecificationTypes> <!-- Only this list of languages will be allowed at import --> <AllowOnlyValidLanguages>true</AllowOnlyValidLanguages> <ValidLanguages> <Language>en-US</Language> <Language>da-DK</Language> </ValidLanguages> </ImportSetting> <TransformerSettingList> <TransformerSetting Name="Illustrations" TransformType="SignifikantSimplifiedXml"> <StylesheetPath>C:\ProgramData\Signifikant\Assert</StylesheetPath> <FolderRegex>Illustrations</FolderRegex> <!-- Alternative path for this type of information --> <ExportBasePath>C:\Export</ExportBasePath> <SequenceNumber>1</SequenceNumber> <BatchSizeMB>20</BatchSizeMB> <BatchCounter>0</BatchCounter> <!-- By default specification types that come in XML cannot change the type already in the database. By setting this tag to true specification types in import will update the type in the database. This setting is available from version 4.5.3 and later. --> <EnableEditExistingSpecificationTypes>false</EnableEditExistingSpecificationTypes> </TransformerSetting> <TransformerSetting Name="Parts" TransformType="SignifikantSimplifiedXml"> <StylesheetPath>C:\ProgramData\Signifikant\Assert</StylesheetPath> <FolderRegex>Parts</FolderRegex> <SequenceNumber>3</SequenceNumber> <BatchSizeMB>20</BatchSizeMB> <BatchCounter>0</BatchCounter> </TransformerSetting> <TransformerSetting Name="Assemblies" TransformType="SignifikantSimplifiedXml"> <StylesheetPath>C:\ProgramData\Signifikant\Assert</StylesheetPath> <FolderRegex>Assemblies</FolderRegex> <SequenceNumber>4</SequenceNumber> <BatchSizeMB>20</BatchSizeMB> <BatchCounter>0</BatchCounter> </TransformerSetting> <TransformerSetting Name="Catalogues" TransformType="SignifikantSimplifiedXml"> <StylesheetPath>C:\ProgramData\Signifikant\Assert</StylesheetPath> <FolderRegex>Catalogues</FolderRegex> <SequenceNumber>5</SequenceNumber> <BatchSizeMB>20</BatchSizeMB> <BatchCounter>0</BatchCounter> </TransformerSetting> </TransformerSettingList> </XmlConfig> </Configurations> |
...
* The persistent-identity is the only attribute that is required in the import file. Often the identity, persistent-identity and number are the same, but there are use cases where these have different values.
Info |
---|
PersistentIDThe persistentID has to be unique per type of information and no duplicates may exist. E.g. there may only be one part with the same persistentID. If persistentID is not unique the import engine will get confused and unexpected results may occur. |
Specifications
You can add an arbitrary number of additional attributes to most data types in the Signifikant information model. During import, you provide their values by using the Specifications tag which takes key/value pairs (called type and value).
...
Each text may be defined by a persistent id which can be referred from all other exports. Each text contains all translations for that text with language defined using ISO 639-1 alternatively ISO 639-1 and ISO 3166.
A text with language "" is considered being invariant, the same for all languages.
...