AnsweredAssumed Answered

ACP import uuidBinding: Local versus Global UUID, MOVE nok

Question asked by sbroussi on Apr 20, 2006
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,

St?phane

Outcomes