Hi Tim and Adan, Thanks for your input. We have considered using an Embargo, but it would not meet our requirements.
We would probably need to handle the mail server error message and add another button that will notify the requester that the file is too large to be sent by mail (and offer them other methods to get the document). We would probably need to implement something similar to Adan. Regards, Enes On Monday, September 24, 2018 at 5:21:54 PM UTC+2, Adan Roman Ruiz wrote: > > We solved using other method. Although it needs changes in the source > code. > First we alter the request-copy to send links with a generated > token (very long), instead of the file. We store into the database the > token, related file, date and uses. > Then we added a point of access to dspace similar to /bitstream called > /itemRequestFileDownload. This access point checks that the token exists, > and returns the related file ignoring permissions. > In addition you can record the number of uses, or use the time passed from > its generated, to make expire the link. > > Best luck > Adán Roman > > El lun., 24 sept. 2018 a las 16:35, Tim Donohue (<tdon...@duraspace.org > <javascript:>>) escribió: > >> Hi Enes, >> >> If you are willing to create a DSpace *group* to provide access to the >> document, then you could manage this access similar to a DSpace Embargo: >> >> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-DSpaceEmbargoFunctionality >> >> In DSpace, an Embargo is simply provides temporary access and/or >> restrictions on an entire Item or a specific file (Bitstream). However, >> those temporary access rights are only available to be set at the Group >> level (not at an individual EPerson). But, if you are willing to create a >> Group for this scenario, then you could Edit the Item, and add a new >> "authorization policy (also known as a "Resource Policy") (on either the >> entire Item, or a single Bitstream). You'd want to define a new policy that >> provides READ access to a specific Group, and add an "End Date" of one >> day/week/month from now. Once the "End Date" passes, the policy will >> expire, and the access rights provided by the policy will no longer be >> valid. >> >> I hope that gives you an idea of another way to provide temporary access >> rights. Let us know on this list if you have other questions. >> >> Tim >> >> >> >> On Mon, Sep 24, 2018 at 6:17 AM eneshukic via DSpace Technical Support < >> dspac...@googlegroups.com <javascript:>> wrote: >> >>> If a registered user is requesting a copy of large bitstream document, >>> mail server will return an error message. >>> >>> >>> What are the other way of distributing large documents? We can export >>> the item (zip file) and place it into shared folder, but that is not the >>> most efficient and secure way to do it. Can we grant a temporary user >>> access to the bitstream? >>> >>> >>> Regards, >>> >>> Enes >>> >>> -- >>> All messages to this mailing list should adhere to the DuraSpace Code of >>> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "DSpace Technical Support" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to dspace-tech...@googlegroups.com <javascript:>. >>> To post to this group, send email to dspac...@googlegroups.com >>> <javascript:>. >>> Visit this group at https://groups.google.com/group/dspace-tech. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> Tim Donohue >> Technical Lead for DSpace & DSpaceDirect >> DuraSpace.org | DSpace.org | DSpaceDirect.org >> >> -- >> All messages to this mailing list should adhere to the DuraSpace Code of >> Conduct: https://duraspace.org/about/policies/code-of-conduct/ >> --- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to dspace-tech...@googlegroups.com <javascript:>. >> To post to this group, send email to dspac...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Adán Román Ruiz > adan....@gmail.com <javascript:> > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
