This document is intended for technical staff creating imports to Signifikant Platform and describes the Signifikant Simplified XML import format.
...
| Code Block | ||
|---|---|---|
| ||
<ImportSetting>
<LanguageSettings>
<!-- If no language specified, use this -->
<DefaultTextLanguage>en-US</DefaultTextLanguage>
<!-- Do not allow to create new languages at import -->
<AutoAddNewLanguage>false</AutoAddNewLanguage>
<!-- Only this list of languages will be allowed at import -->
<AllowOnlyValidLanguages>true</AllowOnlyValidLanguages>
<!-- If language code french is used, map it to fr-FR. -->
<LanguageCodeMapping>
<Language alias="french" culture="fr-FR" />
</LanguageCodeMapping>
<!-- Only listed languages are accepted. -->
<ValidLanguages>
<Languages>en-US,fr-FR</Languages>
</ValidLanguages>
</LanguageSettings>
</ImportSettings> |
...
* 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.
...