Target group

Content administrators

Partners

Background / user story

The import/export of values is useful to execute translations processes.

The import/export is useful when moving CMS data between installations.

The import/export is useful to manage batch updating.

Same as pim

The code base of the Excel import export features in Litium should share as much of the code base as possible.

For example, all field data should have the same format as in the PIM.

Accessible api

We should explore the possibility of building the code base as an api, that partners can use to build their own solutions.

Page ID

The page ID should be the key of a page, and this should be the first column in the exported Excel file.

Sub page of

The second column of the Excel should keep the value of the parent page ID, if one exists.

Block ID

A block, both global and non global, is represented by a row in the Excel.

The third column of the Excel should be reserved for Block IDs.

For a global block that is not used in any page, the first two columns are empty.

For a block, both global and non global, that is used in a page both page IDs and block ID values are presented in the Excel.

Note that the same global block might occur several times in the Excel file. This means that on import, the values of the last read block row will be preserved.