I'm looking for a way to add users to groups at login based on their attributes, e.g. email domain - has anyone seen a plugin to do this or are we going to have to code it ourselves?
I don't think I've seen a plugin for it.
The one solution I've seen is what we have for one customer; they send us CSV files of users / groups / users-in-groups and we run a job to read those CSVs and call out to Mahara's webservices to handle the actual adding/updating of users and getting them into groups.
There's some customisation involved on that particular Mahara, to accommodate things that aren't covered by Mahara's core webservices, and servicing their integration to their LMS, so I can't just share a version of it as-is.
We've also discussed building features to 'push' groups from Moodle to Mahara, but that's not gotten out of the planning stage yet.
I would be interested in learning a bit more about the use case specifically - how do you envisage the attributes mapping to groups? Some kind of series of rules maybe?
Peter
The one solution I've seen is what we have for one customer; they send us CSV files of users / groups / users-in-groups and we run a job to read those CSVs and call out to Mahara's webservices to handle the actual adding/updating of users and getting them into groups.
There's some customisation involved on that particular Mahara, to accommodate things that aren't covered by Mahara's core webservices, and servicing their integration to their LMS, so I can't just share a version of it as-is.
We've also discussed building features to 'push' groups from Moodle to Mahara, but that's not gotten out of the planning stage yet.
I would be interested in learning a bit more about the use case specifically - how do you envisage the attributes mapping to groups? Some kind of series of rules maybe?
Peter
Hi Peter
I suspect it will be a multi-headed approach, and I’m not sure our specific case will be worth a plugin per se.
The first task will be based on email claim matching our own domain, add user to an “internal staff group” - our first training challenge is to get our own staff playing with portfolio-based learning.
The second more complex one will be to add users to groups based on data from our CRM. We already have integration functions in the cloud that do something similar for Moodle, so I suspect this bigger use case will be to write code that talks to the Mahara api. Not done any of that yet, network connectivity is just using MNet and your new LTI submission plugin, so just aware of learning curve.
I suspect it will be a multi-headed approach, and I’m not sure our specific case will be worth a plugin per se.
The first task will be based on email claim matching our own domain, add user to an “internal staff group” - our first training challenge is to get our own staff playing with portfolio-based learning.
The second more complex one will be to add users to groups based on data from our CRM. We already have integration functions in the cloud that do something similar for Moodle, so I suspect this bigger use case will be to write code that talks to the Mahara api. Not done any of that yet, network connectivity is just using MNet and your new LTI submission plugin, so just aware of learning curve.
Sorry left my response and only posted half
Hi Peter
On further reflection I suspect it will be a multi-headed approach, and I’m not sure our specific case will be worth a plugin per se.
The first task was going to be based on email claim matching our own domain, add user to an “internal staff group” - our first training challenge is to get our own staff playing with portfolio-based learning. The more I think about it, the less it is going to be worth writing code. A bulk upload of users and a manual add to group will probably be fastest.
The second more complex one will be to add users to / remove users from groups based on data from our CRM. We already have integration functions in the cloud that do something similar for Moodle, so I suspect this bigger use case will be to write code that talks to the Mahara api. Not done any of that yet, network connectivity is just using MNet and your new LTI submission plugin, so just aware of learning curve.
The rules for this will live in our cloud orchestrations to map a change to a record in CRM to a change to a membership in Mahara. I don’t know enough (I.e. anything) about Mahara API to know if we will need to write a plugin to expose the endpoints we might need for that.
Julian
Hi Peter
On further reflection I suspect it will be a multi-headed approach, and I’m not sure our specific case will be worth a plugin per se.
The first task was going to be based on email claim matching our own domain, add user to an “internal staff group” - our first training challenge is to get our own staff playing with portfolio-based learning. The more I think about it, the less it is going to be worth writing code. A bulk upload of users and a manual add to group will probably be fastest.
The second more complex one will be to add users to / remove users from groups based on data from our CRM. We already have integration functions in the cloud that do something similar for Moodle, so I suspect this bigger use case will be to write code that talks to the Mahara api. Not done any of that yet, network connectivity is just using MNet and your new LTI submission plugin, so just aware of learning curve.
The rules for this will live in our cloud orchestrations to map a change to a record in CRM to a change to a membership in Mahara. I don’t know enough (I.e. anything) about Mahara API to know if we will need to write a plugin to expose the endpoints we might need for that.
Julian
