Export and Import Nodes
Since DMS 2.3.2
1 Export a node
You easily export a node to a
.xml or a
.zip file by following the simple guides below:
1. Select a node that you want to export.
2. Select the
Admin tab.
3. Click the
icon on the action bar to show the
Export Node form:
Details:
| Field | Description |
|---|
| Path to Export | The path of the node that will be exported |
| Format | Document View: Each node is a tag and the properties of that node are considered to be the elements of the tag. System view: Each node and each property of the node is included in a different tag. |
| Zip | The node will be exported in the zip type. |
4. Click the
Export button and select the location to save the file.
If the current node or one of its child nodes has versions, when this node is exported, you can also export a version history of this node.
5. Check in the
Zip check box to export the content to a .zip file.
6. Click on the
Export version history button.
2 Import a node
You can import nodes in
.xml format into JCR Explorer system by following the guides below:
1. Select the location that users want to import a node.
2. Select the
Admin tab.
3. Click the
icon to show the
Import Node form:
4. Click on
Browse to select a file that you want to import.
The file is in .xml format for the Upload file field, and in .zip format for the Version History field.
5. Click the
icon to upload the selected file.
6. Select a behavior:
UUID stands for Universal Unique Identifier that is a used to uniquely identify objects or entities on the Internet. UUID must be unique in the workspace. If you export nodes from the workspace and import them to the same workspace, there will be a conflict between existing nodes in the workspace and those nodes you wish to import. They cannot - under no circumstances - share the same UUIDs. Therefore, you can choose among several strategies (behaviors) that solve or avoid these conflicts.
Details:
| Name | Description |
|---|
| Create new | If you select this behavior, the imported nodes receive new UUIDs which are completely independent of any existing nodes. As the imported nodes get new UUIDs, there are no UUID conflicts with the existing nodes in the workspace. The existing nodes in the workspace are not moved, modified or deleted. The imported nodes are considered as new nodes and do therefore not have a version history. You cannot import a version history for these nodes. |
| Remove existing | If you select this behavior, the imported nodes in a seletecd path receive the same UUIDs of the exported nodes. As the result, there is UUID conflicts with the existing nodes. Therefore, the existing nodes are removed from the workspaces and the new nodes have the same version history as the existing nodes. |
| Replace existing | If you select this behavior, you only can import the exported nodes into their original workspaces where they are exported. When the new nodes are created with the same UUIDs of the existing nodes, causing UUID conflicts with the existing nodes in the workspaces. Therefore, the existing nodes are replaced by the new ones in the same location and the new nodes have the same version history as the existing nodes. |
| Throw Exception | If you select this behavior, there is a message which will alert that you can not import this node in case this node has been existing in the workspace. If this node hasn't existed, a new node will be created. |
Notice: The existing node will be taken an effect when users are working in the same drive or the same user workspace
- In case you import a node which contains its version history, then you should specify the UUID behaviour is 'Remove existing' or 'Replace existing'.
- The node-importing rules for document nodes ( article, file, kofax...) or folder nodes ( content folder, document folder) into document or folder node also follow the rules of adding files and folder types in a folder and creating a new document. For example, you can not import an Article document that is exported from a Content Folder into a Document folder.
7. Click on
Browse to import a version history of a node, then click the
icon to upload the selected file.
This field is not mandatory
8. Select the format in the
Format field.
9. Click the
Import button to complete importing a file.
Notice: When exporting a node to an .xml file and its version history to a .zip file, then importing it into another node with version history, and using the "Create New" UUID behavior, the version history will be lost.
For example: Export the version history of the node "Test 1" with version 1 and then import it:
After importing the node to another node using the UUID behavior "Create New" the node's version history is lost. Because the UUID is the link between a node and its version history, so creating a new UUID for the node will break the link to its version history. You can observe the result in the illustration 82:
