topic ACP import uuidBinding: Local versus Global UUID, MOVE nok in Alfresco Archive

ACP import uuidBinding: Local versus Global UUID, MOVE nok

sbroussi — Thu, 20 Apr 2006 15:53:47 GMT

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:subnode1

Re: ACP import uuidBinding: Local versus Global UUID, MOVE nok

davidc — Thu, 20 Apr 2006 16:09:42 GMT

Can you try the binding REMOVE_EXISTING.

Re: ACP import uuidBinding: Local versus Global UUID, MOVE nok

ero — Thu, 20 Apr 2006 21:31:50 GMT

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

Re: ACP import uuidBinding: Local versus Global UUID, MOVE nok

davidc — Fri, 21 Apr 2006 09:34:21 GMT

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.