[ 
https://jira.duraspace.org/browse/DS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27578#comment-27578
 ] 

Mark H. Wood commented on DS-1465:
----------------------------------

Instead of hoping that the link isn't divulged accidentally or discovered by a 
patient spider, wouldn't it be much better to just exercise precise control by 
explicitly granting a user access?

If becoming a user is burdensome, wouldn't it be better to lift the burden a 
bit by accepting credentials that the viewer may already have?  Think 
Shibboleth (e.g. InCommon), or perhaps we need an OpenID AuthenticationMethod?

I feel that we need to be removing exceptions to access controls, not making 
more of them.  We should be making access control more simple and regular, not 
more ornate.
                
> Enable private sharing of bitstreams through direct links that bypass imposed 
> access restrictions
> -------------------------------------------------------------------------------------------------
>
>                 Key: DS-1465
>                 URL: https://jira.duraspace.org/browse/DS-1465
>             Project: DSpace
>          Issue Type: New Feature
>          Components: DSpace API
>            Reporter: Bram Luyten (@mire)
>         Attachments: Screen Shot 2013-01-24 at 18.20.14.png
>
>
> Here is the usecase:
> Someone who has the ownership/control/authority over a particular item or one 
> of its associated bitstreams, could want to allow specific people to bypass 
> the default embargo's or access restrictions. Instead of forcing this person 
> to take the file and attach it to an email, I think he or she should have a 
> way to generate a link that would allow a non-logged in person to download 
> the file directly.
> As a concrete example of other systems with similar functionality, think 
> about Google Docs access rights, where you can define that "anyone with the 
> link" can view. (see screenshot). 
> In a certain sense this usecase is related to "Request a Copy"
> https://wiki.duraspace.org/display/DSPACE/RequestCopy
> The big difference is that request a copy is only a part of this usecase. The 
> need to share here is generated by a particular person requesting a copy.
> While a professor might want to share one particular paper with his students, 
> by sending them a direct link.
> In certain usecases, there may be a need to put certain limitations on the 
> link:
> - automatic expiry of the direct link after a number of days
> - automatic expiry of the link after a certain number of downloads

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to