Bundle is the red-haired stepchild of the data model, or maybe
it's more like the crazy aunt we keep in the basement.  I *suspect* it is
irrelevant when deciding on read permisison for a Bitstream, but want to check.

Some background:  Bundle *has* ResourcePolicy objects associated with
it, and those are consulted before adding/removign Bitstreams, but none
of the existing code appears to pay any attention to its READ policy
(except the METS package writer, which nobody uses anyway).  One could
make a case that Bundles are really descriptive and/or structural
metadata and shouldn't exert any control over whether their contained
Bitstreams are readable or not; those Bitstreams have policies which can
speak for themselves, and do.  The system doc pages only mention
policies for ADD and REMOVE actions on Bundles.

I'm working with an custom ingest application that uses a restrictive
DEFAULT_BITSTREAM_READ policy on the Collection, and noticed this READ
policy also gets copied to Bundle objects in a new Item, yet it does not
have any effect.  For example, if the ORIGINAL Bundle is only readable to
private group, while its enclosed Bitstream is readable to "Anonymous",
the web UI still lets an anonymous user download it.

Has anyone had an experience of being denied READ access to a Bitstream
because of its enclosing Bundle's policy?  I'm inclined ignore Bundle
policies but want to be sure I'm not missing anything.

thanks,

    -- Larry



------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to