We are syncing a large network drive with Google Apps for Business Drive. When a user removes a file or folder that they do not own on Google Drive, the file or folder is not deleted (since you can't delete a file you don't own) but it is removed from its parent folder. If it has no other parent folders then it becomes an orphan. On Google Drive it is very difficult to find orphans. There is no search term that works for all orphans so you have to search for them individually, assuming you already know they are there. This is extremely annoying, but it's a Google Drive problem.
Syncdocs seems to handle orphans by syncing them to the root of your local sync folder (in our case the network drive). This can be confusing for users of the network drive. It would be far better if these orphans could be moved to a special folder called "Orphaned" or something similar. This would avoid cluttering the folder structure at the root and allow users to see which files and folders have been orphaned. I've put together a script to do this based on some examples I found on the interwebs but it's a very cumbersome solution. Since even using the API I have found no way to search for orphans directly, the script has to chug through every file and folder to check for parents. With a large repository it is too slow to complete without timing out so the script has to remember where it left off and run multiple times. It would be awesome to have syncdocs do this as part of the normal syncing process.