Idea #2044
Updated by Tom Clegg about 10 years ago
Acceptance criteria:
* Share button opens a dialog box with a list of users and groups who can already read this collection.
* Visual indication of which users/groups *you* have given permission to read.
* Click to un-share with a user whose permission was granted by you. This change does not get committed immediately.
* Start typing name or email address to bring up an auto-complete list (e.g., "PGP" or "Tom"). _(This requires changes to @users.list@ api permissions.)_
* Choose a user from the list.
* The chosen user is added to the list, but permission is not assigned yet.
* Click "Done" to commit.
* Click "Cancel" to abandon all modifications since opening dialog.
* Click Share button again to refresh current permissions and adjust from there.
Not necessary [yet]:
* Don't auto-refresh while the dialog is open, or worry about race conditions with other users/windows.
This is a special case of a generic "Share" mechanism needed in Workbench.
* Collections do not have "write" permission.
* Collections are always owned by system_user.
* When you create a collection, you get a free permission/can_read link which is owned by system_user.
Other notes:
* You can't necessarily tell whether another user can already read your collection (e.g., that user saved a copy independently).
* You can't necessarily tell whether another user is a member of a group.