Bulk Import does not support cm:name property on folder metadata

[colindstephenson]

Description of Problem:

The problem being solved is migrating content from a different platform into Alfresco. To avoid name collisions and windows path length issues, the objects are exported out with their unique identifier with the cm:name property set to rename to their correct name in Alfresco.

This works with BI 1.x and the crappy version which ships with Alfresco. BI 2.x does not cope well with the "bait & switch" name change on folders. Files are fine.

Steps to Reproduce:

Create a folder hierarchy of

folder1/folder2/folder3

on folder1 and/or folder2 create a metadata.properties.xml file and set the cm:name to something other than folder1 or folder 2, ie altfolder1 and altfolder2

Expected Result:

I would expect to see in Alfresco a hiearchy like altfolder1/altfolder2/folder3.

Actual Result:

OutOfOrderBatchException due to not being able to resolve altfolder1. Bulk Import looks for folder1 (based upon the filesystem hierarchy).

Environment:

CentOS 6.7, Alfresco One 5.1.1 (installed from one click installer)

[colindstephenson]

I implemented a crude solution to this, to allow us to proceed with using BI2 rather than the OOTB version. Attached the DirectoryAnalyser.java to give the general idea off adding an additional sourceRelativeParentDirectory.

DirectoryAnalyser.java.txt