On Fri, Jan 18, 2013 at 11:55 AM, Bram Luyten <[email protected]> wrote: > the pre-DSpace 3.0 embargo's applied on a whole item by removing read > restrictions on all bitstreams at a certain date specified in the item > metadata.
Bram probably has better overall information on embargo, but I can say that this is certainly not true. It all depends on how you define your embargo setter/lifter, e.g. I have one that sets/lifts embargo only on the bitstream marked as primary, the rest remains publically accessible for the whole item's lifetime. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
