Both serverimport and serverexport have a special handling built in for the
master and masterVersion properties.
The export will store the translation state of a derived document and on import efforts are taken
to reestablish a comparable translation state.
For the concrete names of the master and masterVersion properties,
the SiteModel has to be provided to the tools, which is done via
Spring in the file COREM_HOME/properties/corem/serverimportexport-context.xml
(In CoreMedia Blueprint this file is added in the cms-tools-application module).
Examples:
The examples assume that you export a document and its master and import it afterwards into a
clean system. The table uses # (hash mark) to denote contents having the given latest version number.
- Master (before)
The master version before export. none means that no master link is set.
- Version (before)
Value of the master version property of the derived document before export. none means that no version is specified yet which actually marks derived documents as not being up to date with its master document.
- State (before)
The translation state of the derived document before export.
- Master (after)
The master version after import (actually always
#1).- Version (after)
- Value of the master version property of the derived document after import.
- State (after)
The translation state of the derived document after import.
| Master (before) | Version (before) | State (before) | Master (after) | Version (after) | State (after) | Comment |
|---|---|---|---|---|---|---|
#5
|
5
| up-to-date |
#1
|
1
| up to date | The master and derived document were up to date before export (derived document is most recent localization of its master). Thus, after import the same state is set. |
#5
|
4
| not up-to-date |
#1
|
| master version destroyed | The master and derived document were not up to date before export. Thus, after import the value of the master version property is set to a special version number denoting that the derived content is not up-to-date. On API level this is regarded as if the referred master version got destroyed meanwhile. For the editor the document will appear as being not up-to-date. |
#5
|
none | not translated yet |
#1
|
none | not translated yet | Derived document was never localized from its master. Thus, the same state applies after import. |
|
none |
5
| no master |
none |
| no master | Corrupted content: No special logic is applied. The overall approach for import and export is defensive thus if the state was invalid before, the fallback is to use the default behavior from import and export keeping the values as is. |
Table 6.21. Example for server export and import for multi-site
 |  |  |
 |