Kevin: I am not sure if you're interested, but I made some code modifications at Cornell University's dspace instance that puts up an informational display when one clicks on an embargoed bitstream or one that is controlled by IP. The code that I use is based on some code that I borrowed from Terry Owen at the University of Maryland several years ago (Thanks, Terry!). It puts up displays based on the group that controls a bitstream. So, here at Cornell, we have our embargo code set up to restrict a bitstream to a specific group "embargo" which has read access to the bitstream. I have the code for JPSUI 1.8.2 and XMLUI 1.8.2. If you are interested in the details, I can send them to you.
Below are examples: For Embargo, go to http://ecommons.library.cornell.edu/handle/1813/31510 and click on the bitstream to see the display For IP restriction, go to http://ecommons.library.cornell.edu/handle/1813/29540 and clikc on the bitstream to see the display George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 -----Original Message----- From: helix84 [mailto:[email protected]] Sent: Thursday, May 23, 2013 6:51 PM To: Evans, Kev Cc: [email protected] Subject: Re: [Dspace-tech] What are the options for restricting the display of the login box for embargoed files On Thu, May 23, 2013 at 5:03 PM, Evans, Kev <[email protected]> wrote: > Dspace Version. 1.8.2 > Theme: xmlui I'll assume the default Mirage theme. The process normally looks like this: 1) click on an embargoed bitstream, get the following prompt: The file is restricted The file you are attempting to access is a restricted file and requires credentials to view. Please login below to access the file. Sign in to DSpace 2) sign in to dspace as a non-administrative user 3) get the following message: This bitstream is restricted You do not have the credentials to access the restricted bitstream This seems pretty straight-forward to me. I'm not sure how you'd like to make it clearer. Anyway, I added a new feature that appears in DSpace 3 that shows a lock icon for bitstreams that have restricted access (missing Anonymous READ). Since you're on 1.8, you have 2 options if you want this feature: 1) upgrade to DSpace 3 2) apply my patch from this Jira ticket (it's compatible with 1.8): https://jira.duraspace.org/browse/DS-1193 There's a screenshot attached to that ticket showing what it looks like. If I misunderstood and you wanted something else, please explain. 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 ------------------------------------------------------------------------------ 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
