thanks for this additional clarification.
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?
again, I got my info from the current docs:
*.. The default behavior here is simply to remove the read policies on all
the bundles and bitstreams except for the "LICENSE" or "METADATA" bundles
...*
https://wiki.duraspace.org/display/DSDOC3x/Embargo#Embargo-Termsinterpretation/imposition
On Fri, Jan 18, 2013 at 12:42 PM, helix84 <[email protected]> wrote:
> 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
