Open Source Document Management System | OpenKM

I am testing out the export/import of a repository. I exported my current repository on 5.1.10 and tried to import it to a blank 5.1.10 with metadata and restoring uuid's enabled. I get an error "Error: Target node 6728c115-92e1-4bd4-8346-c70131a21813 of REFERENCE property does not exist" on the import. It looks like this occurred because the category existed on the old system but not on the new system. Are categories referenced in the metadata validated by an import but not handled entirely on an export and import (meaning exported and then imported)? Is this correct? How am I to get the categories into the new system (if this is indeed the issue)?

is not needed to force create with same UUID ( here could get some problem), simply import with order, first import categories and then taxonomy files, with this ordering ( without force UUID ) should get it.

Interesting... I would have expected that it would be preferable to avoid restoring UUId's on a repository with existing data but not on an empty repository. If I were to rebuild a repository from scratch from an export it is preferable for me to keep the same uuid's because of custom applications that we have that work with openkm via web services rely on linking to the uuid's in order to abstract away relying on the location of the document in the repository. Is there a reason you have the checkbox to restore uuid's??? Will it be better supported in the future to restore a repository from scratch with the previous uuid's intact? This would obviously be desirable to me for a complete restore from backup or a migration that depended on an export/import of the repository.

Thanks for your help and a great product!

Yes, as you said is good option to continue having same UUID. But is this case is not a UUID problem is an order of operatons problem, first should be imported categories and then documents. I made some imports without repecting UUID ( Because in my case was not necessary ) I do not know if could be some problem repecting UUID with same operation ( I think not ), if you found something wrong tell us and we will take a look on it.