Unlike documents, folders are not checked out, so they are available at all times to all authors. Consequently, your local folder structure may differ from the structure on the server due to delays in synchronization while you are working online or because you are working offline. For instance, while working offline, you create a folder under a parent that another author has deleted. The server resolves these conflicts by following prescribed conflict resolution rules. The following describes the server side conflicts that can occur for folder operations performed on the client side and the rules the server uses to resolve them.

Add Folder

Conflict: Parent folder is renamed or moved.
Resolution: The new folder is added to renamed/moved folder.

Conflict: Parent folder is deleted (not yet purged).
Resolution: Undelete parent and add new folder to it.

Conflict: New folder has same name, but different document ID, folder already on server under the parent.
Resolution: The client folder is updated to the same document ID as the folder on the server. No new folder is created.

Conflict: Folder on server already exists and was deleted.
Resolution: Undelete the folder and parent(s) if needed, and update client folder to server folder document ID.

Conflict: Parent does not exist; was purged.
Resolution: Client folder is placed in root directory of Library.

Conflict: No conflicts.
Resolution: Add folder to server.

Move Folder

Conflict: Old parent folder is renamed or moved.

Resolution: No problem. Folder moves to new location.

Conflict: New parent folder is renamed or moved.

Resolution: No problem. Folder moves to new location.

Conflict: New parent is deleted (not yet purged).

Resolution: Undelete new parent and move folder.

Conflict: Folder already moved on server (parent folder on server already contains folder with same document ID).

Resolution: No action necessary.

Conflict: Another folder with the same name is found in the new parent.

Resolution: Contents of move folder are moved into server side folder with same name. Purge (not mark as deleted) both server and client side old move folder.

Conflict: A deleted folder with the same name is found in new parent.

Resolution: Undelete the server side folder and parent(s) if needed and move the contents of the folder into the server side folder with the same name. Purge both the server and client side move folder.

Conflict: New parent does not exist (was purged).

Resolution: Abort the move. Restore the folder to old location.

Conflict: No conflicts.

Resolution: Move the folder.

Rename Folder

Conflict: Folder name already changed.

Resolution: Override name with client name. Basically last one to change the name wins.

Conflict: Folder marked as deleted.

Resolution: Undelete folder, parents if needed and rename it.

Conflict: Parent renamed or folder has moved.

Resolution: No problem since parent identified by document ID. Renamed folder moves to updated parent.

Conflict: Folder does not exist (was purged).

Resolution: Abort operation. Folder will be totally removed when done.

Conflict: No conflicts.

Resolution: Rename folder.

Delete Folder

Conflict: Folder not empty (contains undeleted documents or folders).

Resolution: If all of the documents are checked in, delete the contents of the folder and then the folder. If server side folder contains checked out documents, folder is not deleted.

Conflict: Parent folder is renamed or moved.

Resolution: No problem since parent identified by document ID. Delete the folder.

Conflict: Deleted folder was renamed.

Resolution: No problem finding folder since identified by document ID. Delete the renamed folder.

Conflict: Folder already deleted.

Resolution: Do nothing - work already done.

Conflict: Folder does not exist (was purged).

Resolution: Do nothing - work already done.

Conflict: No conflicts.

Resolution: Mark the folder as deleted.

Table of Contents