[Sakai Jira] Commented: (SAKIII-2267) Content Profile > Visibility and Permissions > problems with "Message Link" behavior for "private" cotnet

[Bert Pareyn (JIRA)]

    [ https://jira.sakaiproject.org/browse/SAKIII-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=119563#comment-119563 ] 

Bert Pareyn commented on SAKIII-2267:
-------------------------------------

1) The link not being displayed was part of SAKIII-2024 and has now been fixed.

2) IMO we shouldn't remove buttons due to a privacy setting (well, for managers). Frequent users might not immediately see that their content has private permission settings and wonder why the messaging button isn't there, just because they've always seen it in there and expect it to be available. Instead of undermining the expected workflow I suggest we give a more subtle notification to the user upon sharing.

I've attached two possible scenario's:

A) Simple message stating that the content is private and giving the user a choice to go and change the permissions or send the message anyway.

B) The message in this screen indicates that the users who receive the message will also be added to the list of viewers. This option does not need any further action from the sharer before or after sharing. I would go for this solution as it anticipates expected behaviour and doesn't trouble the user with extra actions.

WDYT?

> Content Profile > Visibility and Permissions > problems with "Message Link" behavior for "private" cotnet
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SAKIII-2267
>                 URL: https://jira.sakaiproject.org/browse/SAKIII-2267
>             Project: Sakai 3 UI Dev
>          Issue Type: Bug
>          Components: Content & Media
>    Affects Versions: Sprint 103: Stabilization and QA
>         Environment: ttp://sakai3-demo.uits.indiana.edu:8080
> DEBUG: Nakamura Version: 0.9-257-g6eb2f93 | UX Version: v_0.5.0_rc3-911-g0b7bc65
> DOC mod date: | PLACE: 7HY5igo3QaX7IudwCOUuaAD
>            Reporter: Lynn E. Ward
>            Assignee: Bert Pareyn
>             Fix For: Sprint 104: Stabilization and QA
>
>         Attachments: A.jpg, B.jpg
>
>
> When a private content item has been shared with another user, that user can see and use the "message link" button to attempt to send the link to a user with whom the item has not been shared.  There are two problems under this scenario:
> 1.  The message that is sent to the other user doesn't contain the URL to the content item.  The sender sees this message:
> "Hi,
> I would like to share "Lynn.jpg" with you.
> You can find it on http://sakai3-demo.uits.indiana.edu:8080/dev/content_profile.html#content_path=/p/7HY5igo3QaX7IudwCOUuaAD
> Regards,
> Lynn"
> But the received message is the following:
> Lynn Too wants to share a file with you
> Lynn
> Accept | Deny | You have replied to this site join request | Accept Invitation | Ignore Invitation | You have accepted this person as a contact or ignored their request | Reply
> 2.  More importantly, the recipient doesn't have permission to view the document.  So, I think we need to rethink the behavior here.  Perhaps the "Message Link" and "Email the link" buttons should not display if the item is private, and only the "Message the Link" should show if the item is only available to logged in users.  Sending a user a link does no good if they cannot access the document.  Alternatively, we could notify the sender if they attempt to message someone who does not have permission to view the document.
> To replicate:
> 1.  Create three accounts (called user1, user2, and user3)
> 2.  As user1, upload a file, make it private, and share it with user2 as a viewer.  Then logout.
> 3.  Login as user2, access the file from step 1 and message the link to user 3.  Note the default message text includes the URL.  Copy the URL to the clipboard.  The logout.
> 4.  Login as user 3 and access your messages.  You should have a message from user2 that tells you the file has been shared, but no details are provided.  Now, paste the URL into the location field of user3's browser.  You'll get an error that the page is unavailable.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira