On Fri, Dec 7, 2012 at 9:31 PM, Tim Au Yeung <[email protected]> wrote: > I have a bit of an odd scenario going on here and could use some > suggestions. We have a 1.7.2 instance running using the default embargo > settings. It sets the embargo lift date and removes the policies for the > item but the embargoed bitstream is viewable despite the fact that there are > no read policies on the bitstream in the item's authorizations. Anyone > encounter a similar situation/have suggestions as to what's going on here?
Hi Tim, sorry I can't be of any immediate help, but I wanted to check the resource policies in your repositories and it's down for me (no ping). Curiously, it seems to be up from elsewhere: http://www.isup.me/dspace.ucalgary.ca These are the last three hops that are responding: 6 canarie-gw.rt1.ams.nl.geant.net (62.40.124.222) 120.830 ms 120.767 ms 120.708 ms 7 clgr2rtr1.canarie.ca (205.189.32.162) 156.312 ms 155.855 ms 155.790 ms 8 c4-orano-tor.canet4.net (205.189.32.213) 159.576 ms 156.452 ms 156.391 ms 9 * * * When you figure out this (IMHO much more important) issue, please, send me a link to an example item in your repository so I that I can do a quick check. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ 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
