From: Jason Simms <jsimms@ut...> - 2004-09-24 15:02:49
Why is it that when I create a new collection and specifically UNCHECK
"New items should be publicly readable" the collection still is created
with a READ policy for Anonymous? Is this a bug, or just yet another
"feature" of the overly-complex authentication scheme about which I am
still unclear? Incidentally, the parent community does not have a
default READ policy for Anonymous.
Frankly, I still can't figure out the differences (or, more to the
point, why there even is a difference) amongst READ, DEFAULT_ITEM_READ,
and DEFAULT_BITSTREAM_READ. Is READ for the general collection,
DEFAULT_ITEM_READ for the item page, and DEFAULT_BITSTREAM_READ for the
actual file? According to the docs, the READ policy does not even have
an entry under either Community or Collection; do they therefore have no
use in those contexts? Why would READ not trump the other two within a
collection, or does it?
This all seems too complex. Other posts in the past have also
complained about certain policies having no effect depending on their
context. Obviously, this is still a problem.