On Fri, May 24, 2013 at 12:19 PM, Evans, Kev <[email protected]> wrote: > We want to display the message when users click on the bitstream but NOT the > login box. And despite the message (we have edited telling them they do not > have access to the file - due to embargo) they still attempt to login. Hence > creating frustrated users! > > Hope this makes sense.
Yes, now it does. The question here is how can you tell apart: a) when the user is denied access due to not being logged in (in which case the login box should be displayed); and b) when the user is denied access due to embargo (in which case you don't want to display the login box) Do you still use the original 1.6 embargo as opposed to simplified embargo introduced in DSpace 3? In that case which metadata field stores the information that there is/isn't an embargo? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ 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
