Hello Mark,
wouldn't the bitstream based embargo with advanced settings kind of do
the trick. This step is available in the workflow.
You can restrict individual bitstream to a group and set the date to the
actual date, thus the policy would take effekt immediately.
The drawback is, that the step
We have a collection (currently in DSpace 5.2) in which we need to
restrict access to some but not all ORIGINAL bitstreams, based on
human judgments. Unless I've missed something, there is no way for a
collection editor to apply these judgments during workflow. So I've
recommended that the collec
