Jose -

Thanks for your input.  He is a submitter but not an admin in any community
or collection.

We have discovered that this issue is happening in any collection with
anonymous read access that was created since we upgraded to dSpace 6.3
about a year ago.  It is not user-specific as we first thought.  So it's a
big concern except that we have not created many new collections.

We're wondering if there are configuration changes related to creating
collections or new defaults that came about in 6.3 that could cause this.
Anyone else experience this or know of a bug fix for this?  I'm searching
documentation but have not found anything that seems to be relevant yet.

Kelley Canon
Language & Culture Archives
REAP Administrator
SIL International


On Tue, Nov 3, 2020 at 9:15 AM Jose Blanco <[email protected]> wrote:

> I see.  This is strange.  I wonder if the user belongs to a group that is
> an admin or even submitter to the collection?
>
> When creating admins and submitters to a collection, you can choose
> individuals or groups.  Perhaps this user belongs to a group that is part
> of Admins or Submitters to that collection?
>
> -Jose
>
> On Mon, Nov 2, 2020 at 9:50 PM Kelley Canon <[email protected]> wrote:
>
>> Jose -
>>
>> This user is not an admin at all - he is not a member of the Admin group
>> for the collection or the community it is in.
>>
>> I should not have said "partial".  My mistake.  I was comparing what he
>> sees to what I see as a dSpace system administrator.
>>
>> He should not have any admin access at all.  No editing of items or the
>> collection.
>>
>> Thank you,
>> Kelley Canon
>> Language & Culture Archives
>> REAP Administrator
>> SIL International
>>
>>
>> On Mon, Nov 2, 2020 at 7:56 PM Jose Blanco <[email protected]> wrote:
>>
>>> Kelley,  I don't see the problem.  If you are an admin and you have
>>> selected a collection, you should only see:
>>>
>>> "Edit Collection" and "Item Mapper"
>>>
>>> and if you are viewing and item, you should only see:
>>>
>>> "Edit this item"
>>>
>>> Not sure what the problem is.  What were you expecting?
>>>
>>> -Jose
>>>
>>>
>>> On Mon, Nov 2, 2020 at 6:22 PM [email protected] <[email protected]>
>>> wrote:
>>>
>>>> Hi all -
>>>>
>>>> We're running dSpace 6.3 using XMLUI and have run into a situation we
>>>> have not seen before.  A user with no Admin permissions at the collection
>>>> or community level has a *PARTIAL set of Admin tasks on his Context
>>>> menus*.  This only happens in ONE particular collection.
>>>>
>>>> At the collection level he has "Edit Collection" and "Item Mapper"
>>>> available.
>>>>
>>>> At the item level he has "Edit this item".
>>>>
>>>> Has anyone encountered this or know what else besides the community and
>>>> collection authorizations I need to check?
>>>>
>>>> Thank you,
>>>> Kelley Canon
>>>> SIL International
>>>>
>>>> --
>>>> All messages to this mailing list should adhere to the DuraSpace Code
>>>> of Conduct: https://duraspace.org/about/policies/code-of-conduct/
>>>> ---
>>>> 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 view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/dspace-tech/c11d4b58-de3c-45b0-91bb-ed436715cea2n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/dspace-tech/c11d4b58-de3c-45b0-91bb-ed436715cea2n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CACXx6FtKkhbQ4p8oarP4%2BfAzed0wq%2BM6k3mWE8Czx%2BjsPq48uQ%40mail.gmail.com.

Reply via email to