I have a similar desire, but I'm a code guy, not really an interface guy. I was wondering if the ImporterComponent implementation of the ImporterService could just be made a little smarter until I or someone else can find the time to properly expose the UUID Binding options in the web client UI.
I have an as yet untested change that might help make the import process just a little smarter in regard to UUIDs. Specifically, the part where I change the AND to OR is what's untested, simply importing the UUIDs works fine in my custom-generated ACPs.
Here's a diff of what I'm talking about:
Standard disclaimer here…there's a lot of code involved in making Alfresco go, and I freely admit that I am unaware of any effects of my alterations that are farther reaching than those I intend. The intended changes are these:
By default, when importing content, Alfresco appears to use the CREATE_NEW binding. I have changed the default to be CREATE_NEW_WITH_UUID. When importing, Alfresco checks to see if assignNewUUID is false AND if the node being imported has a UUID that is not null. My understanding of this is that you need to have a UUID assigned AND you have to specifically not want to create new ones on import, and my understanding of my change is that it will instruct Alfresco to look for and import UUIDs by default, and generate them as when they are not present in the imported package.
A possible "gotcha" here is that this seems to put the onus of ensuring that the UUIDs are actually unique to the Alfresco repository squarely on the shoulders of the importer, and so more may need to be done there. In my case, as I alluded to before, I am generating ACPs on the fly. The content I'm generating isn't participating in Alfresco's more advanced features, like workflow or versioning, it's largely using Alfresco's content storage, delivery, and transcription features. That all said, I recognize that my patch works for my use case, but a cleaner solution is likely necessary.
Hope this helps someone.
I have an as yet untested change that might help make the import process just a little smarter in regard to UUIDs. Specifically, the part where I change the AND to OR is what's untested, simply importing the UUIDs works fine in my custom-generated ACPs.
Here's a diff of what I'm talking about:
Index: /Alfresco/projects/repository/source/java/org/alfresco/repo/importer/ImporterComponent.java
===================================================================
— /Alfresco/projects/repository/source/java/org/alfresco/repo/importer/ImporterComponent.java (revision 1242)
+++ /Alfresco/projects/repository/source/java/org/alfresco/repo/importer/ImporterComponent.java (working copy)
@@ -460,7 +460,7 @@
{
if (uuidBinding == null)
{
- return new CreateNewNodeImporterStrategy(true);
+ return new CreateNewNodeImporterStrategy(false);
}
else if (uuidBinding.equals(UUID_BINDING.CREATE_NEW))
{
@@ -488,7 +488,7 @@
}
else
{
- return new CreateNewNodeImporterStrategy(true);
+ return new CreateNewNodeImporterStrategy(false);
}
}
@@ -1256,7 +1256,7 @@
Map<QName, Serializable> initialProperties = bindProperties(node);
// Assign UUID if already specified on imported node
- if (!assignNewUUID && node.getUUID() != null)
+ if (!assignNewUUID || node.getUUID() != null)
{
initialProperties.put(ContentModel.PROP_NODE_UUID, node.getUUID());
}
Standard disclaimer here…there's a lot of code involved in making Alfresco go, and I freely admit that I am unaware of any effects of my alterations that are farther reaching than those I intend. The intended changes are these:
By default, when importing content, Alfresco appears to use the CREATE_NEW binding. I have changed the default to be CREATE_NEW_WITH_UUID. When importing, Alfresco checks to see if assignNewUUID is false AND if the node being imported has a UUID that is not null. My understanding of this is that you need to have a UUID assigned AND you have to specifically not want to create new ones on import, and my understanding of my change is that it will instruct Alfresco to look for and import UUIDs by default, and generate them as when they are not present in the imported package.
A possible "gotcha" here is that this seems to put the onus of ensuring that the UUIDs are actually unique to the Alfresco repository squarely on the shoulders of the importer, and so more may need to be done there. In my case, as I alluded to before, I am generating ACPs on the fly. The content I'm generating isn't participating in Alfresco's more advanced features, like workflow or versioning, it's largely using Alfresco's content storage, delivery, and transcription features. That all said, I recognize that my patch works for my use case, but a cleaner solution is likely necessary.
Hope this helps someone.
