ACP import uuidBinding: Local versus Global UUID, MOVE nok

[sbroussi]

Hi,

I'm testing the Import feature (command line to specify the -uuidBinding UPDATE_EXISTING).

My problem is that the node UUID specified in the ACP file is checked only in the local folder where the import is running on.

1) Tree Example *BEFORE IMPORT* :

- node1 (uuid:node1)
  - subnode1a (uuid:subnode1a)
- node2 (uuid:node2)‍‍‍

2) I import an ACP file containing the structure
    where I want to MOVE the "subnode1a"
    to another folder (here: node2)

ACP structure:

- node1 (uuid:node1)
- node2 (uuid:node2)
  - subnode1a (uuid:subnode1a)‍‍‍

3) Tree Example *AFTER IMPORT* :

- node1 (uuid:node1)
  - subnode1a (uuid:subnode1a)
- node2 (uuid:node2)
  - subnode1a (uuid:subnode1a)‍‍‍‍

4) *EXPECTED RESULT* :

- node1 (uuid:node1)
- node2 (uuid:node2)
  - subnode1a (uuid:subnode1a)
‍‍‍‍

Problem: The UUID is checked if it exists in the local
folder where the import is running on.
This prohibit to MOVE contents from the command
line.
The need is to manage the node structure from a
legacy system (db extract, ACP generation, import
ACP from the command line)

—

My guess: Using a new uuidBinding
(let say: UPDATE_AND_MOVE_EXISTING),
the "ImporterComponent" should check if the
same UUID is existing in the WHOLE content store.
If yes, this node should be updated and moved
according to its new location.

Guess 2: Is it planned to have the uuidBinding
selection accessible from the Web UI ?

Thanks in advance,

Stephane

[davidc]

Can you try the binding REMOVE_EXISTING.

[ero]

Can you try the binding REMOVE_EXISTING.

Hi David,

Stephane forgot to say that needing to keep any existing content or subspace of subnode1a space as is (unchanged), we can't use REMOVE_EXISTING command line option as suggested.
Our requirement is to switch parent node relationship (from node1 -current parent space- to node2 -any other new space in the tree hierarchy-).
It's only possible if UUID is really considered as being unique across all content store. It seems it's not actually the case.

Eric

[davidc]

The importer's primary job is to import new items or update existing items.  It's not particularly suited to deleting or moving existing items - and that's what you want to do - move a child from one parent to another without re-creating the child.

For the fine control you described, you'll need to use one the repository api's.  

One idea is that we add a "control" language to the ACP introducing verbs such as create, delete, move etc.  This would give the ability to write synchronisation tools and perhaps generate deltas.