Re: [Dspace-tech] Problem with authorization created during Submission process in DSpace 1.5.1

2010-03-11 Thread Thornton, Susan M. (LARC-B702)[RAYTHEON TECHNICAL SERVICES COMPANY]
Great!  Thanks Graham!
Sue


From: Graham Triggs [mailto:grahamtri...@gmail.com]
Sent: Thursday, March 11, 2010 2:57 PM
To: Thornton, Susan M. (LARC-B702)[RAYTHEON TECHNICAL SERVICES COMPANY]
Cc: DSpace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Problem with authorization created during Submission 
process in DSpace 1.5.1

Hi Sue,

Don't worry, the READ policy on the COLLECTION has no effect on the access of 
the items.

In fact, it doesn't really have any effect on the access of the Collection home 
page/browse itself, either :(

For accessing items, what you need to be concerned with is the 
DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ - those are the policies that 
Items and Bitstreams inherit when they are installed (accepted) into the 
repository - and it is only the policies defined on each Item or Bitstream 
individually (which are created from the default) that determine access when 
someone tries to view or download the item / bitstream.

Regards,
G
On 11 March 2010 18:48, Thornton, Susan M. (LARC-B702)[RAYTHEON TECHNICAL 
SERVICES COMPANY] mailto:susan.m.thorn...@nasa.gov>> 
wrote:
Hi,
 We are in the process of implementing a new secure DSpace instance where 
the default access has to be "no-access" for anonymous users. During the 
"Define Collection" process, despite the fact that I am NOT checking the box 
that says "New items should be publicly readable", the following authorization 
is being added at the Collection level for a new Collection:

[cid:image001.jpg@01CAC138.58D2A690]

Maybe this is ok and maybe I'm unclear on the difference between READ access to 
a Collection and DEFAULT-ITEM-READ access to a Collection.

If the only access I have to a Collection is READ access, exactly what can I do 
and see in that Collection?

Thanks and Best regards,
Sue


Sue Walker-Thornton
ConITS Contract
NASA Langley Research Center
Integrated Library Systems ~ Developer/DBA
130 Research Drive
Hampton, VA  23666
Office: (757) 224-4074
Fax:(757) 224-4001
Mobile:  (757) 506-9903
Email:  susan.m.thorn...@nasa.gov<mailto:susan.m.thorn...@nasa.gov>


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net<mailto:DSpace-tech@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/dspace-tech

<>--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] Problem with authorization created during Submission process in DSpace 1.5.1

2010-03-11 Thread Graham Triggs
Hi Sue,

Don't worry, the READ policy on the COLLECTION has no effect on the access
of the items.

In fact, it doesn't really have any effect on the access of the Collection
home page/browse itself, either :(

For accessing items, what you need to be concerned with is the
DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ - those are the policies that
Items and Bitstreams inherit when they are installed (accepted) into the
repository - and it is only the policies defined on each Item or Bitstream
individually (which are created from the default) that determine access when
someone tries to view or download the item / bitstream.

Regards,
G

On 11 March 2010 18:48, Thornton, Susan M. (LARC-B702)[RAYTHEON TECHNICAL
SERVICES COMPANY]  wrote:

>  Hi,
>
>  We are in the process of implementing a new secure DSpace instance
> where the default access has to be *“no-access”* for anonymous users.
> During the “Define Collection” process, despite the fact that I am NOT
> checking the box that says *“New items should be publicly readable”*, the
> following authorization is being added at the Collection level for a new
> Collection:
>
>
>
>
>
> Maybe this is ok and maybe I’m unclear on the difference between READ
> access to a Collection and DEFAULT-ITEM-READ access to a Collection.
>
>
>
> If the only access I have to a Collection is READ access, exactly what can
> I do and see in that Collection?
>
>
>
> Thanks and Best regards,
>
> Sue
>
>
>
>
>
> *Sue Walker-Thornton*
>
> *ConITS Contract**
> NASA Langley Research Center
> Integrated Library Systems ~ Developer/DBA*
>
> *130 Research Drive*
>
> *Hampton, VA  23666*
>
> *Office: (757) 224-4074**
> Fax:(757) 224-4001
> Mobile:  (757) 506-9903*
>
> *Email:** ** **susan.m.thorn...@nasa.gov* 
>
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>
<>--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech