Hi Mark,
On 03/03/16 16:46, Mark Ludwig wrote:
Thanks for your help, you are brilliant!
You hit it right away. The collection owner was authorized to
edit items and inadvertently set some as 'private'.
Glad I could help :)
Anyway, I'll have to do some work to find any other items that may
have been set to
private.
You can easily identify them in the database since it's a column on the
item table. If you're using XMLUI, you can also see all private items at
eg http://demo.dspace.org/xmlui/admin/private -- I'm not sure whether
similar page exists in JSPUI.
I'll look to see if there is an option to turn off setting items private,
which just seems like a bad idea.
I don't think it can be turned off. You could change the wording around
the "make private" button to strongly discourage your users? Really I
guess it should be called "discoverable" in the user interface (like it
is called in the code/database), and perhaps there is some overlap with
the (relatively new) access rights awareness in Discovery that doesn't
make for the best user experience. Feel free to report this as a bug :)
https://jira.duraspace.org/browse/DS
cheers,
Andrea
--
Dr Andrea Schweer
Lead Software Developer, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
+64-7-837 9120
--
You received this message because you are subscribed to the Google Groups "DSpace
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
