It saves time to list the exact wording ("This export archive is restricted.").Here's what the comment at that place in code says: // The user does not have read access to this bitstream. Interrupt this current request // and then forward them to the login page so that they can be authenticated. Once that is // successful they will request will be resumed. I don't use that functionality, so I don't know what's wrong. One guess I would take is - if you made the export and he's trying to download it, he probably can't (although I'm not sure your export would show up in his "My Exports"). Is the message the same when he tried to do the export as opposed to downloading the export? BTW you may test the functionality on demo.dspace.org. From my test, it works (both exporting and downloading the export). Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
