[Archivesspace_Users_Group] A user who is set as manager of a collection can not create containers...

[Gadsby, Eric T.]

Payten,

Our users report that worked. Yvonne thanks for your input as well.  Thanks everybody! 

Sincerely,

Eric T Gadsby
IT Operations Specialist, Cook Library
Towson University
egadsby at towson.edu
410-704-3340

> On Nov 16, 2016, at 2:20 AM, Payten Giles <payten at paytengiles.com> wrote:
> 
> Hi there Eric,
> 
> Access to the “Create” for containers is provided by the update_container_record role.  It looks like this isn’t granted to managers (repository-managers) by default.  This has a bug vibe and I’ll ensure a JIRA issue is recorded.
> 
> In the meantime, you can expand the roles available to your repository managers by following these steps:
> 
> 1. Login as an administrator
> 2. Ensure the repository you’d like to update is selected
> 3. Under the ‘cog’ icon next to the repository name, select "Manage Groups”
> 4. Select ‘Edit’ next to the repository-managers group
> 5. Under “Members can”, ensure the checkbox for "create/update top container records” is selected
> 6. Save Group
> 
> Hopefully the “Create” action will now be available!
> 
> Thanks,
> Payten
> 
> 
> On 16 November 2016 at 11:47:21 AM, Gadsby, Eric T. (egadsby at towson.edu) wrote:
> 
>> I posted this to the list earlier but the list seems more active this week so I thought I’d try again. One of ouse users is manger of a collection but can’t create containers in it here is what they report: 
>> 
>> “While attempting to create top containers for instances, I only had access to “browse” but not create. I had management level access at the time. I had to be given admin level access to be able to gain the create button for top containers. The create option disappeared when placed on just admin level access. I had to be placed in both levels of access to be able to create top containers.” 
>> 
>> Our server has only been in production for a few weeks and is set-up per the http://www.archivesspace.org recommendations. Our server does authenticate via LDAP (Active Directory) but our users experience is the same using an AD or ArchivesSpace local users. Do you know how we might resolve this or what might be the next steps in troubleshooting? Thanks! 
>> 
>> Sincerely,
>> 
>> Eric T Gadsby
>> IT Operations Specialist, Cook Library
>> Towson University
>> egadsby at towson.edu
>> 410-704-3340 _______________________________________________ 
>> Archivesspace_Users_Group mailing list 
>> Archivesspace_Users_Group at lyralists.lyrasis.org 
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group