This document is intended for technical staff creating imports to Signifikant Platform and describes the Signifikant Simplified XML import format.
...
* 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 | ||
|---|---|---|
| ||
The 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).
...
Most data types in the Signifikant information model can be linked to an image. The image is identified by its file name in the image directory. Images are imported into the Signifikant Manager from a directory or zip-file.
Removing presentations
All presentations can be removed at import by usign a remove command in the xml.
| Code Block | ||||
|---|---|---|---|---|
| ||||
<!-- Sample ContentSet removal -->
<ContentSets>
<ContentSet remove="true">
<persistent-identity>8433121394</persistent-identity>
</ContentSet>
<ContentSets>
<!-- Sample Document removal -->
<Documents>
<Document remove="true">
<persistent-identity>12345678_A123456_external</persistent-identity>
</Document>
</Documents>
|
Specific components per data type of the xml import files
...
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.
...