mahara-contributors team mailing list archive

[Gordon McLeod <1212644@xxxxxxxxxxxxxxxxxx>]

The aspect that prompted the current thread was about easy access to the
resources on the pages without making them 'open', as Aaron commented. I
guess it would start to look like a cohort enrolment system - but that's
one of the ways I've been using Mahara groups in a teaching context -
for disseminating information resources meant to be shared with student
year cohorts. Admin users are assigned who can upload content, create
pages, etc and if users wanted to participate using forums the group
could have request membership if it was necessary to restrict access.

Something I did notice while manually assigning shared group access to
the multiple pages/collections of a resource group was that the users
then get an e-mail notification for every page/collection that is
shared, so end up with 6-8 messages (per group shared) rather than a
single notice for each group.

I'm just wondering - if a group A page is shared with group B, do the
users in group B have rights to post to forums in group A? If not then
this would just be an extension of the same rights but set higher up the
chain so that viewing access is granted to all pages in one go. I
appreciate that's a simplification of the actual work involved! ;)

I guess the question of hierarchical groups ties in with this wishlist
feature for sub groups  https://bugs.launchpad.net/mahara/+bug/1169962

Regards, Gordon.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contrib members
https://bugs.launchpad.net/bugs/1212644

Title:
  Share group with other groups - not just pages

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Enhancement request.
  I've recently developed a number of resource groups with multiple pages/collections to be shared with staff and students across several years and programmes. Auto enrol all users isn't an option as we need to restrict access to the content and our Mahara is accessed university wide. Adding staff and students to year cohorts and sharing the resource groups with those would allow the necessary level of access filtering, but in order to share the content of the resource groups with the 'cohort group' you need to share access at the page or collection level rather than at group level. If it was possible to 'share with group' at the group (rather than page) level and effectively give any member of group A the right to access the content in group B that would make the process much easier - making sharing 1 click instead of 6 to 10 page/collection shares per group.
  Regards, Gordon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1212644/+subscriptions