We have implemented a CMIS repository for our database and have noticed a couple of issues with the Drive CMIS connector.
In our repository the paths are not made up of the names. For example if a consider a top level folder with the name Top Level Folder and sub-folder called Sub Folder, i.e
Top Level Folder
+-- Sub Folder
The CMIS connector assumes that the path to the folder is /Top Level Folder/Sub Folder whereas, in our repository, then path has the format /FOLDER00002/FOLDER00010. For folders the GetObject call returns the cmis:path property that should be used instead of assumnig that the path is made up of the names. For documents the GetObjectParents and GetChildren calls allow the path segment to be returned.
2. Multiple Parents
Our repository supports multi-filing and therefore documents can have multiple parents. We have found that thsi causes a problem when saving new assets. In our repository assets can be automatically added to a second folder when created. The connector requires the first parent returned by the GetObjectParents call to be the folder that the asset has just been created in. We have worked around this by ordering the parents returned but it would be better if the connector checked all the parents returned.