-
Type: Task
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: ADDONS_5.6
-
Component/s: Nuxeo Drive
We need to implement the following file system tree client-side:
Nuxeo Drive |_ My Documents |_ Other Documents
where:
- My Documents contains either:
- the children of the user personal workspace if it is registered as a synchronization root
- the folders registered as synchronization roots and created by the user if the user workspace is not registered as a synchronization root
- Other Documents contains the folders synchronized by the user, created by another user and on which the user has the ReadWrite permission
So in the case where the user workspace is registered as a synchronization root, the hierarchy sould be:
Nuxeo Drive |_ My Documents | |_ Child folder 1 of user workspace | |_ Child folder 2 of user workspace | |_ Child file 1 of user workspace | |_ ... |_ Other Documents | |_ Shared synchronized folder 1 | |_ Shared synchronized folder 2 | |_ ...
else:
Nuxeo Drive |_ My Documents | |_ Synchronized folder 1 | |_ Synchronized folder 1 | |_ ... |_ Other Documents | |_ Shared synchronized folder 1 | |_ Shared synchronized folder 2 | |_ ...
The names of the Nuxeo Drive, My Documents and Other Documents folders must be configurable through an extension point.
- depends on
-
NXP-11110 Existing local folder bound to a newly synchronized root does not get its children synchronized
- Resolved
- is required by
-
NXP-11515 fileSystemItem attribute should not be None in the change summary entry for an unregistered sync root that can be adapted
- Resolved
-
NXP-11517 Make sure that a document remotely deleted and created with the same name in the same sync batch is deleted first client side to avoid deduplication suffix
- Resolved
-
NXP-11587 Add integration tests for the custom hierarchy configurations
- Resolved
-
NXP-10122 Options for Nuxeo Drive hierarchy
- Resolved