In order to offer the most opportunities for sharing, but still maintain our contract of privacy with the end users, we propose the following strategy:
- Thumbnails are no longer public. They will be visible or not dependent on the users rights over that item. This is only relevant in albums and slideshows.
- Users can create albums or slideshows of any content they have read access over without restriction.
- When the user goes to share the album/ss, the IME sets access on items that user has admin rights on; IME reports on any it could not set access on - reports that user will not be able to see it, OR that user will be able to see it because already has access to that item. In second case, we should note that we cannot guarantee it will stay accessible.
- IME will also create record in the item representing any item-level access right and the context in which it is relevant. It will use this record to manage these rights when adding/removing them. IME workflow:
1. For each item in the album/ss, check if admin over. If YES, set item-level right, and record album-right in item record.
2. If NO, query to see if the user being given privileges already has access to that item. Report on the failure, whether it will be visible or not. - Any items later added to the album should be also given all relevant item-level privileges where they can be, and the user should be notified if the item(s) cannot be shared.
- Any items that are removed, item-level access record should be removed, and item-level access should be removed if it is not present in some other context.
Use cases:
SAP & HST:
- Judy uploads files to a library. She creates an album, which she shares with Jamie. Jamie makes changes, and then is ready to let the publisher know that they are ready. When Jamie tries to share with the publisher she is warned that she cannot share the items in the album. Judy must give Jamie admin rights over the content in her library, or over the album itself (is this true?) so Jamie can share it.
- This seems acceptable: everyone on the team needs to be an admin of the content. Once we have groups, this will be very easy to make work.
Stellar:
- Professor A gathers content from Rotch, and from Vue, and creates a slideshow. She then shares it with her students. Students WILL be able to see all the content, because Rotch and Vue content is public, even though she does not have admin rights over that content. QUESTION: how should we handle the messaging? don't want to alarm people unnecessarily.
- Professor B has a library, and shares it with Professor A. Professor A takes some content from Prof B's library, and adds it to her slideshow. She is notified that this content will NOT be visible to her students, and she must ask Professor B to make the content public if it is to be shareable.