Handling of access levels in File Cloud
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	grote
	Apr 28 2015, 5:01 AM

Description

Currently, the Kolab files module allows moving files from Seafile backend from one folder into a read-only folder. Apparently, the UI suggests that it is still possible to move a file into the read-only folder and shows it there, but then does not allow to move it out again:

Read-only libraries/folders in Seafile should be shown as such, maybe using a lock icon and then not allowing files to be moved/copied inside the folder in the first place.

Currently the UI is not aware of the access rights of folders. The same is for mail folders in Roundcube. While we do this for addressbook/calendar/tasks Alec is not sure it's good for Files and Mail. There might be possible problem with performance, as we expect more folders here, but maybe if we'd check rights only on shared folders it wouldn't be so bad. There's no performance problem for SeaFile as its API already returns access rights of a folder/library.

This request is specifically for Seafile, so it would be sufficient to check for read-only state for shared file folders via the Seafile API.

Details

Ticket Type: Epic

Related Objects
Search...

Status	Assigned	Task
Resolved	machniak	T106 Handling of access levels in File Cloud
Resolved	machniak	T112 Cache the read-only / read-write / access control parameters to folders from backends
Resolved	machniak	T114 Design of the UI elements to indicate read-only or read-write state of a folder
Resolved	machniak	T116 Omit read-only folders in "Save to cloud..." type of dialogs
Resolved	None	T115 Prevent dropping files to read-only folders

Event Timeline

grote created this task.Apr 28 2015, 5:01 AM

grote raised the priority of this task from to 60.

grote updated the task description. (Show Details)

grote added projects: Architecture & Design, Quality Assurance, Product Owners.

grote changed Ticket Type from Task to Task.

grote edited a custom field.

grote subscribed.

Seafile returns directory metadata containing the read-only / read-write state of a folder, so no separate round-trip would be needed.

IMAP would require more roundtrip interactions, but is assisted by local caches.

The Chwala API and API client however only communicate about the folders, not the associated access level.

@machniak and I agree that this can be a (client) post-operation, such that the list of folders is communicated first, followed by a chunked series of requests about the user's access to them.

vanmeeuwen moved this task from Backlog to Elaboration on the Architecture & Design board.Apr 28 2015, 9:54 AM

vanmeeuwen added a subtask: T114: Design of the UI elements to indicate read-only or read-write state of a folder.Apr 28 2015, 11:39 AM

vanmeeuwen added subtasks: T116: Omit read-only folders in "Save to cloud..." type of dialogs, T115: Prevent dropping files to read-only folders.Apr 28 2015, 11:41 AM

vanmeeuwen renamed this task from Seafile: Handle ReadOnly Folders to Handling of access levels in File Cloud.Apr 28 2015, 11:52 AM

vanmeeuwen edited a custom field.