On Fri, Jan 18, 2013 at 12:47 PM, Bram Luyten <[email protected]> wrote: > When you say "define your setter/lifter" how much of this happens in > configuration and how much is customization. > Or to ask the question differently: which kind of settings are provided "out > of the box" and which ones are achieved with customization? > How did you change the setter/lifter so that it only applies to the primary > bitstream?
That's right, the setter/lifter is custom code. I always assumed the DefaultEmbargoSetter/DefaultEmbargoLifter classes are something like a placeholder, meant to be customized, because they are very limiting. So to rephrase: > 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. Yes, that is correct with the default setter/lifter, which is written in a way that encourages customizing it. Admittedly, that may not be easy for anyone. 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
