Hi Yanan,
For our repository,  we add all files only accessible by admie as "Evidence
file (non-public)".
[image: image.png]
Kind regards,
Rui


*Rui Guo**Assistant Librarian **/*  *Library Systems  *

*The Library  **/**  University of Waikato*

*Private Bag 3105*  */*  *Hamilton 3240*  */*
*New Zealand**www.waikato.ac.nz* <http://www.waikato.ac.nz/>   */** +64 ** 7
837 9138 *


On Fri, May 7, 2021 at 10:52 AM Zhao, Yanan <[email protected]>
wrote:

> Hello all,
>
>
>
> I hope this email finds you well.
>
>
>
> A couple of questions about default READ authorisation policies for full
> text file.
>
>
>
> One of our DSpace collections (
> https://researcharchive.lincoln.ac.nz/handle/10182/13711) has the
> following authorisation policies:
>
>
>
> READ     Anonymous [Group Settings]
>
> DEFAULT_ITEM_READ   Anonymous [Group Settings]
>
> DEFAULT_BITSTREAM_READ      Administrator [Group Settings]
>
>
>
> We want this collection to only have metadata publically available while
> all full text files are only accessible by admin. When we upload a new file
> under ‘Bundle: ORIGINAL’ or make a change to the full text file name and/or
> description e.g., https://researcharchive.lincoln.ac.nz/handle/10182/13750,
> the full text file seems to pick up the DEFAULT_ITEM_READ policy instead of
> the DEFAULT_BITSTREAM_READ policy which making it publically accessible.
>
>
>
> Have anyone experienced this? Have we done anything wrong in term of
> setting up the authorisation policies?
>
>
>
> We are on DSpace v5.8 XMLUI.
>
>
>
> Many thanks in advance,
>
> Yanan
>
>
>
> ––––––––––––––––––––––––––––––––––
>
> *Yanan Zhao RLIANZA (she/her/hers)*
>
> Digital Services Analyst
>
> ––––––––––––––––––––––––––––––––––
>
> *Learning, Teaching and Library – Te Whare Pūrākau*
>
> Ivey Hall
>
> PO Box 85064, Lincoln University
>
> Lincoln 7647, Christchurch, New Zealand
>
> +64 3 423 0340
>
> [email protected]
>
> ltl.lincoln.ac.nz
>
> ––––––––––––––––––––––––––––––––––
>
> *Lincoln University*
>
> Te Whare Wānaka o Aoraki
>
> ––––––––––––––––––––––––––––––––––
>
>
>
>
>
> ------------------------------
>
> "The contents of this e-mail (including any attachments) may be
> confidential and/or subject to copyright. Any unauthorised use,
> distribution, or copying of the contents is expressly prohibited. If you
> have received this e-mail in error, please advise the sender by return
> e-mail or telephone and then delete this e-mail together with all
> attachments from your system."
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-community/SYBPR01MB5471C1BD18E5130C0AA5201EC2589%40SYBPR01MB5471.ausprd01.prod.outlook.com
> <https://groups.google.com/d/msgid/dspace-community/SYBPR01MB5471C1BD18E5130C0AA5201EC2589%40SYBPR01MB5471.ausprd01.prod.outlook.com?utm_medium=email&utm_source=footer>
> .
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/CAOmr_ZuBMLna70jU1yP336WXB7ztuy8vXw451rS_eaLmsXqmZg%40mail.gmail.com.

Reply via email to