|
||||||||
|
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 |
||||||||
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
org.dspace.content.Collection[] cols = org.dspace.content.Collection.findAuthorized(authContext, community, Constants.ADD);
I can't find a call to Collection.findAll.
In the case of mediated deposit, each collection returned by findAuthorized is subsequently checked for permissions for that additional user, which will take extra time.
Workaround - if that is the problem - is to turn off mediated deposit, and insist that users log in using their own usernames.
Other solutions might be to call findAuthorized on both the authenticating user and the obo user and extract the union of these two sets. Not sure where the performance hit lies, though, so deeper analysis is required before we can be sure that would make things quicker.