本讨论区帖子已移除
回帖数：12
本讨论区帖子的内容已移除，无法再访问。
I could be wrong, but I don't think you can do that from within Moodle per se. The closest I get to a solution would be the following (it should work):
1 - Create a specialized administrative role for each company and permission it only for their classes.
2 - Disable visibility to the full list of students across all companies
3 - Create an external application that company admins can use to manage their users. This is an extremely difficult thing to do. Indeed, it might be doable with mods of the administrative code that limited visibility based on the users. Either way, the institution field is probably the key to distinguishing users.
The key problem, of course, is that is that point 2 is incompatible with limiting company admins visibility to users from other companies without a code modification that only allows them to see users from specific institutions.
Davis Foulger
1 - Create a specialized administrative role for each company and permission it only for their classes.
2 - Disable visibility to the full list of students across all companies
3 - Create an external application that company admins can use to manage their users. This is an extremely difficult thing to do. Indeed, it might be doable with mods of the administrative code that limited visibility based on the users. Either way, the institution field is probably the key to distinguishing users.
The key problem, of course, is that is that point 2 is incompatible with limiting company admins visibility to users from other companies without a code modification that only allows them to see users from specific institutions.
Davis Foulger
回复Davis Foulger
Re: Offering the same courses to many enterprises (privacy concerns)
That should read "This is NOT an extremely difficult thing to do." Every PHP in the Moodle system is, in effect, a discrete application. The key thing is to rewrite the administrative PHP applications to observe the institution field such that institutional admins can only manage (or see) their users. This would probably be a great generalized addition to Moodle. The value of doing it outside, so long as it is not a generic feature of Moodle, is that you can upgrade standard Moodle code without affecting your instituational management code.
回复Davis Foulger
本讨论区帖子已移除
本讨论区帖子的内容已移除，无法再访问。
I don't know that the patches would be terribly extensive. You should be able to be able to update the databases with the institutional information by uploading update users lists with the institution information included. Given, however, that you already have group data in the system, you should be able to create a bit of SQL logic that fills in the institutional field based on the group data.
Once that's done the patches you need should be limited to the administrative modules directly related to users, including all the modules associated with users/accounts and, within classes, role and group assignments. That shouldn't be huge.
So long as you can create a single administrative role that is limited to managing users within their institution and have confirmed that the the user list is limited to their institution, things should be pretty clean.
This isn't nearly as hard as I thought it might be up front.
Once that's done the patches you need should be limited to the administrative modules directly related to users, including all the modules associated with users/accounts and, within classes, role and group assignments. That shouldn't be huge.
So long as you can create a single administrative role that is limited to managing users within their institution and have confirmed that the the user list is limited to their institution, things should be pretty clean.
This isn't nearly as hard as I thought it might be up front.
回复Davis Foulger
本讨论区帖子已移除
本讨论区帖子的内容已移除，无法再访问。
If you force separate groups on all of your courses and use Site-Wide Groups you could accomplish this very thing and you could only use one set of courses. You would need to throttle down some of the role settings for directors and turn of Messaging to keep things completely "clean".
You said your deadline was the end of the year, so I'm assuming you already implemented something. How did you go about it?
回复Dakota Duff
Re: Offering the same courses to many enterprises (privacy concerns)
Yes the kind of thing in this thread is a key reason for the plans happening here (for Moodle 2.0):
Development:Site-wide_groups
Development:Site-wide_groups
回复Martin Dougiamas
Re: Offering the same courses to many enterprises (privacy concerns)
Martin, where's the best place for me to submit my thoughts on this. We use groups like crazy so I have some very strong feelings about this. I read through the link you posted, which gave me even stronger feelings about the right and wrong ways to do this, but I'm not sure where to put my input.
Dakota, please feel free to add your thoughts to Development:Site-wide groups. If you want to add your name just type four tildes ~~~~.
Dakota, I guess you clicked on the 'View source' tab by accident. Anyway, you just need to login to Moodle Docs in order to edit pages.