[Building Sakai] Control number of users in Sakai sites

Thu Jul 10 13:07:19 PDT 2014

You should put your thinking into the Jira directly. No guarantees that 
this will get done, but it seems like a good idea, so hopefully.

Thanks,
Neal

> alaanizar at iihem.ac.ma <mailto:alaanizar at iihem.ac.ma>
> July 9, 2014 at 9:03 AM
> Hi,
>
> Can you please make it configurable per site (OLD or NEW)!
>
> Meaning that we can modify this number in a given worksite if the need 
> arise. A project A worksite, created and got limited to 10 users, may 
> require more users. thus, the need to modify the number of 
> participants for this site only.
>
> Just like how quota works.
>
> Thank you
>
> Yours,
> Alaa
>
>
>
> > Yeah! That is pretty sweet. If he is asking you to open the Jira,
> > perhaps he will find time to work on it. Fingers crossed.
> >
> >> alaanizar at iihem.ac.ma <mailto:alaanizar at iihem.ac.ma>
> >> July 9, 2014 at 8:07 AM
> >> Hello,
> >>
> >> I created a JIRA for this issue: SAK-26624
> >> <https://jira.sakaiproject.org/browse/SAK-26624>
> >>
> >> Thank you Steve, sooo much!
> >>
> >>
> >> Yours,
> >> Alaa NIZAR
> >>
> >>
> >>
> >> > This would be pretty simple to do if it was global configuration
> >> like you
> >> > suggested in sakai properties. In the kernel a check could be added
> >> before
> >> > adding a user and throw a specific error if the limit had been 
> reached.
> >> > This should cover all cases of adding a user, site info, joining 
> a site,
> >> > profile site crwation and invitation, Web services, etc.
> >> >
> >> > The problem with doing it via webservices is that you would need to
> >> modify
> >> > the various tools that can add users to sites.
> >> >
> >> > File a jira!
> >> >
> >> > Cheers
> >> > Steve
> >> >
> >> > sent from my mobile device
> >> > On 09/07/2014 2:56 AM, "Alaa NIZAR" <alaanizar at iihem.ac.ma> wrote:
> >> >
> >> >> Hi,
> >> >> Definitely yes.
> >> >>
> >> >> A new feature will take more time and resources to be done.
> >> >>
> >> >> I hope if there is a work around it.
> >> >>
> >> >> I thought of a new link tool, with php. The idea is to let the site
> >> owner
> >> >> add/remove participants through forms and webservices.
> >> >>
> >> >> The control with be done softly in php nothing to do with sakai 
> code at
> >> >> all.
> >> >>
> >> >> What do you think?
> >> >>
> >> >> Yours,
> >> >> Alaa
> >> >>
> >> >>
> >> >> Sent from Samsung Mobile
> >> >>
> >> >>
> >> >> -------- Original message --------
> >> >>
> >>
> From: Neal Caidin
> >> >> Date:08/07/2014 16:51 (GMT+00:00)
> >> >> To: alaanizar at iihem.ac.ma
> >> >> Cc: sakai-dev
> >> >> Subject: Re: [Building Sakai] Control number of users in Sakai sites
> >> >>
> >> >> Hi Alaa,
> >> >>
> >> >> To clarify, I believe you are hoping such a feature exists or that
> >> >> something relatively easy could be modified to create this 
> capability?
> >> >>
> >> >> Thanks,
> >> >> Neal
> >> >>
> >> >>
> >> >> alaanizar at iihem.ac.ma
> >> >> July 8, 2014 at 12:16 PM
> >> >> Hi All,
> >> >>
> >> >> We have a special use case that I want to share with you and try to
> >> find
> >> >> solutions for it:
> >> >>
> >> >> I have normal project sites, that users can create by their own. 
> Those
> >> >> type of sites, and because they are available to anyone in the
> >> system to
> >> >> create, can grow high. I want to limit the number of users in this
> >> type of
> >> >> sites to a configurable number.
> >> >> Whereas online courses are created by the admin and the site 
> owner can
> >> >> add/remove participants. Because those type of sites use
> >> BigBlueButton as
> >> >> video conferencing solution, I want to limit the number of members
> >> that the
> >> >> site owner can add.
> >> >> Yet, I want Tutoring type of site to be limited to no more than 10
> >> >> students.
> >> >>
> >> >> Ideally, I should be some configuration like this:
> >> >>
> >> >> max.participants.count=4
> >> >> max.participants.project=20
> >> >> max.participants.course=50
> >> >> max.participants.onlinecourse=30
> >> >> max.participants.tutoring=10
> >> >>
> >> >> This way, the number of users per site is shown on the site 
> setup tool,
> >> >> while adding participants.
> >> >>
> >> >> This must be set by the sakai admin, with the possibility to change
> >> it per
> >> >> created site, just like how site quota works.
> >> >>
> >> >> Besides, we are not using any roster or student systems.
> >> >>
> >> >> To put it simple, **It's a quota for site members.**
> >> >>
> >> >> Yours,
> >> >> Alaa NIZAR
> >> >>
> >> >>
> >> >> --
> >> >>
> >> >> Alaa NIZAR, BA in MIS, LPIC
> >> >> IIHEM Network Services Manager
> >> >> +212 665 222 160
> >> >> www.iihem.ac.ma
> >> >> --
> >> >> This message has been scanned for viruses and
> >> >> dangerous content by *MailScanner* <http://www.mailscanner.info/>,
> >> and is
> >> >> believed to be clean.
> >> >> _______________________________________________
> >> >> sakai-dev mailing list
> >> >> sakai-dev at collab.sakaiproject.org
> >> >> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >> >>
> >> >> TO UNSUBSCRIBE: send email to
> >> >> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> >> >> "unsubscribe"
> >> >>
> >> >>
> >> >> --
> >> >> Neal Caidin
> >> >> Sakai Community Coordinator
> >> >> Apereo Foundation
> >> >> neal.caidin at apereo.org
> >> >> Skype me! (but let me know in advance for the first interaction) -
> >> nealkdin
> >> >>
> >> >>
> >> >> --
> >> >> This message has been scanned for viruses and
> >> >> dangerous content by *MailScanner* <http://www.mailscanner.info/>,
> >> and is
> >> >> believed to be clean.
> >> >> --
> >> >> This message has been scanned for viruses and
> >> >> dangerous content by *MailScanner* <http://www.mailscanner.info/>,
> >> and is
> >> >> believed to be clean.
> >> >>
> >> >> _______________________________________________
> >> >> sakai-dev mailing list
> >> >> sakai-dev at collab.sakaiproject.org
> >> >> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >> >>
> >> >> TO UNSUBSCRIBE: send email to
> >> >> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> >> >> "unsubscribe"
> >> >>
> >> >
> >> > --
> >> > This message has been scanned for viruses and
> >> > dangerous content by MailScanner, and is
> >> > believed to be clean.
> >> >
> >> >
> >>
> >>
> >> --
> >>
> >> Alaa NIZAR, BA in MIS, LPIC
> >> IIHEM Network Services Manager
> >> +212 665 222 160
> >> www.iihem.ac.ma
> >> --
> >> This message has been scanned for viruses and
> >> dangerous content by *MailScanner* <http://www.mailscanner.info/>, 
> and is
> >> believed to be clean.
> >> Steve Swinsburg <mailto:steve.swinsburg at gmail.com>
> >> July 9, 2014 at 1:31 AM
> >>
> >> This would be pretty simple to do if it was global configuration like
> >> you suggested in sakai properties. In the kernel a check could be
> >> added before adding a user and throw a specific error if the limit had
> >> been reached. This should cover all cases of adding a user, site info,
> >> joining a site, profile site crwation and invitation, Web services, 
> etc.
> >>
> >> The problem with doing it via webservices is that you would need to
> >> modify the various tools that can add users to sites.
> >>
> >> File a jira!
> >>
> >> Cheers
> >> Steve
> >>
> >> sent from my mobile device
> >>
> >> Alaa NIZAR <mailto:alaanizar at iihem.ac.ma>
> >> July 8, 2014 at 12:56 PM
> >> Hi,
> >> Definitely yes.
> >>
> >> A new feature will take more time and resources to be done.
> >>
> >> I hope if there is a work around it.
> >>
> >> I thought of a new link tool, with php. The idea is to let the site
> >> owner add/remove participants through forms and webservices.
> >>
> >> The control with be done softly in php nothing to do with sakai code
> >> at all.
> >>
> >> What do you think?
> >>
> >> Yours,
> >> Alaa
> >>
> >>
> >> Sent from Samsung Mobile
> >>
> >> -------- Original message --------
> >>
> From: Neal Caidin <neal.caidin at apereo.org>
> >> Date:08/07/2014 16:51 (GMT+00:00)
> >> To: alaanizar at iihem.ac.ma
> >> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
> >> Subject: Re: [Building Sakai] Control number of users in Sakai sites
> >>
> >> Hi Alaa,
> >>
> >> To clarify, I believe you are hoping such a feature exists or that
> >> something relatively easy could be modified to create this capability?
> >>
> >> Thanks,
> >> Neal
> >>
> >>
> >> alaanizar at iihem.ac.ma July 8, 2014 at 12:16 PM
> >> Hi All,
> >>
> >> We have a special use case that I want to share with you and try to
> >> find solutions for it:
> >>
> >> I have normal project sites, that users can create by their own. Those
> >> type of sites, and because they are available to anyone in the system
> >> to create, can grow high. I want to limit the number of users in this
> >> type of sites to a configurable number.
> >> Whereas online courses are created by the admin and the site owner can
> >> add/remove participants. Because those type of sites use BigBlueButton
> >> as video conferencing solution, I want to limit the number of members
> >> that the site owner can add.
> >> Yet, I want Tutoring type of site to be limited to no more than 10
> >> students.
> >>
> >> Ideally, I should be some configuration like this:
> >>
> >> max.participants.count=4
> >> max.participants.project=20
> >> max.participants.course=50
> >> max.participants.onlinecourse=30
> >> max.participants.tutoring=10
> >>
> >> This way, the number of users per site is shown on the site setup
> >> tool, while adding participants.
> >>
> >> This must be set by the sakai admin, with the possibility to change it
> >> per created site, just like how site quota works.
> >>
> >> Besides, we are not using any roster or student systems.
> >>
> >> To put it simple, *It's a quota for site members.*
> >>
> >> Yours,
> >> Alaa NIZAR
> >>
> >>
> >
> > --
> > Neal Caidin
> > Sakai Community Coordinator
> > Apereo Foundation
> > neal.caidin at apereo.org
> > Skype me! (but let me know in advance for the first interaction) - 
> nealkdin
> >
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> >
> >
>
>
> -- 
>
> Alaa NIZAR, BA in MIS, LPIC
> IIHEM Network Services Manager
> +212 665 222 160
> www.iihem.ac.ma
> -- 
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
> Neal Caidin <mailto:neal.caidin at apereo.org>
> July 9, 2014 at 8:22 AM
> Yeah! That is pretty sweet. If he is asking you to open the Jira, 
> perhaps he will find time to work on it. Fingers crossed.
>
>
> alaanizar at iihem.ac.ma <mailto:alaanizar at iihem.ac.ma>
> July 9, 2014 at 8:07 AM
> Hello,
>
> I created a JIRA for this issue: SAK-26624 
> <https://jira.sakaiproject.org/browse/SAK-26624>
>
> Thank you Steve, sooo much!
>
>
> Yours,
> Alaa NIZAR
>
>
>
> > This would be pretty simple to do if it was global configuration 
> like you
> > suggested in sakai properties. In the kernel a check could be added 
> before
> > adding a user and throw a specific error if the limit had been reached.
> > This should cover all cases of adding a user, site info, joining a site,
> > profile site crwation and invitation, Web services, etc.
> >
> > The problem with doing it via webservices is that you would need to 
> modify
> > the various tools that can add users to sites.
> >
> > File a jira!
> >
> > Cheers
> > Steve
> >
> > sent from my mobile device
> > On 09/07/2014 2:56 AM, "Alaa NIZAR" <alaanizar at iihem.ac.ma> wrote:
> >
> >> Hi,
> >> Definitely yes.
> >>
> >> A new feature will take more time and resources to be done.
> >>
> >> I hope if there is a work around it.
> >>
> >> I thought of a new link tool, with php. The idea is to let the site 
> owner
> >> add/remove participants through forms and webservices.
> >>
> >> The control with be done softly in php nothing to do with sakai code at
> >> all.
> >>
> >> What do you think?
> >>
> >> Yours,
> >> Alaa
> >>
> >>
> >> Sent from Samsung Mobile
> >>
> >>
> >> -------- Original message --------
> >>
> From: Neal Caidin
> >> Date:08/07/2014 16:51 (GMT+00:00)
> >> To: alaanizar at iihem.ac.ma
> >> Cc: sakai-dev
> >> Subject: Re: [Building Sakai] Control number of users in Sakai sites
> >>
> >> Hi Alaa,
> >>
> >> To clarify, I believe you are hoping such a feature exists or that
> >> something relatively easy could be modified to create this capability?
> >>
> >> Thanks,
> >> Neal
> >>
> >>
> >> alaanizar at iihem.ac.ma
> >> July 8, 2014 at 12:16 PM
> >> Hi All,
> >>
> >> We have a special use case that I want to share with you and try to 
> find
> >> solutions for it:
> >>
> >> I have normal project sites, that users can create by their own. Those
> >> type of sites, and because they are available to anyone in the 
> system to
> >> create, can grow high. I want to limit the number of users in this 
> type of
> >> sites to a configurable number.
> >> Whereas online courses are created by the admin and the site owner can
> >> add/remove participants. Because those type of sites use 
> BigBlueButton as
> >> video conferencing solution, I want to limit the number of members 
> that the
> >> site owner can add.
> >> Yet, I want Tutoring type of site to be limited to no more than 10
> >> students.
> >>
> >> Ideally, I should be some configuration like this:
> >>
> >> max.participants.count=4
> >> max.participants.project=20
> >> max.participants.course=50
> >> max.participants.onlinecourse=30
> >> max.participants.tutoring=10
> >>
> >> This way, the number of users per site is shown on the site setup tool,
> >> while adding participants.
> >>
> >> This must be set by the sakai admin, with the possibility to change 
> it per
> >> created site, just like how site quota works.
> >>
> >> Besides, we are not using any roster or student systems.
> >>
> >> To put it simple, **It's a quota for site members.**
> >>
> >> Yours,
> >> Alaa NIZAR
> >>
> >>
> >> --
> >>
> >> Alaa NIZAR, BA in MIS, LPIC
> >> IIHEM Network Services Manager
> >> +212 665 222 160
> >> www.iihem.ac.ma
> >> --
> >> This message has been scanned for viruses and
> >> dangerous content by *MailScanner* <http://www.mailscanner.info/>, 
> and is
> >> believed to be clean.
> >> _______________________________________________
> >> sakai-dev mailing list
> >> sakai-dev at collab.sakaiproject.org
> >> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>
> >> TO UNSUBSCRIBE: send email to
> >> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> >> "unsubscribe"
> >>
> >>
> >> --
> >> Neal Caidin
> >> Sakai Community Coordinator
> >> Apereo Foundation
> >> neal.caidin at apereo.org
> >> Skype me! (but let me know in advance for the first interaction) - 
> nealkdin
> >>
> >>
> >> --
> >> This message has been scanned for viruses and
> >> dangerous content by *MailScanner* <http://www.mailscanner.info/>, 
> and is
> >> believed to be clean.
> >> --
> >> This message has been scanned for viruses and
> >> dangerous content by *MailScanner* <http://www.mailscanner.info/>, 
> and is
> >> believed to be clean.
> >>
> >> _______________________________________________
> >> sakai-dev mailing list
> >> sakai-dev at collab.sakaiproject.org
> >> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >>
> >> TO UNSUBSCRIBE: send email to
> >> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> >> "unsubscribe"
> >>
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> >
> >
>
>
> -- 
>
> Alaa NIZAR, BA in MIS, LPIC
> IIHEM Network Services Manager
> +212 665 222 160
> www.iihem.ac.ma
> -- 
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
> Steve Swinsburg <mailto:steve.swinsburg at gmail.com>
> July 9, 2014 at 1:31 AM
>
> This would be pretty simple to do if it was global configuration like 
> you suggested in sakai properties. In the kernel a check could be 
> added before adding a user and throw a specific error if the limit had 
> been reached. This should cover all cases of adding a user, site info, 
> joining a site, profile site crwation and invitation, Web services,  etc.
>
> The problem with doing it via webservices is that you would need to 
> modify the various tools that can add users to sites.
>
> File a jira!
>
> Cheers
> Steve
>
> sent from my mobile device
>
> Alaa NIZAR <mailto:alaanizar at iihem.ac.ma>
> July 8, 2014 at 12:56 PM
> Hi,
> Definitely yes.
>
> A new feature will take more time and resources to be done.
>
> I hope if there is a work around it.
>
> I thought of a new link tool, with php. The idea is to let the site 
> owner add/remove participants through forms and webservices.
>
> The control with be done softly in php nothing to do with sakai code 
> at all.
>
> What do you think?
>
> Yours,
> Alaa
>
>
> Sent from Samsung Mobile
>
> -------- Original message --------
> From: Neal Caidin <neal.caidin at apereo.org>
> Date:08/07/2014 16:51 (GMT+00:00)
> To: alaanizar at iihem.ac.ma
> Cc: sakai-dev <sakai-dev at collab.sakaiproject.org>
> Subject: Re: [Building Sakai] Control number of users in Sakai sites
>
> Hi Alaa,
>
> To clarify, I believe you are hoping such a feature exists or that 
> something relatively easy could be modified to create this capability?
>
> Thanks,
> Neal
>
>
> alaanizar at iihem.ac.ma July 8, 2014 at 12:16 PM
> Hi All,
>
> We have a special use case that I want to share with you and try to 
> find solutions for it:
>
> I have normal project sites, that users can create by their own. Those 
> type of sites, and because they are available to anyone in the system 
> to create, can grow high. I want to limit the number of users in this 
> type of sites to a configurable number.
> Whereas online courses are created by the admin and the site owner can 
> add/remove participants. Because those type of sites use BigBlueButton 
> as video conferencing solution, I want to limit the number of members 
> that the site owner can add.
> Yet, I want Tutoring type of site to be limited to no more than 10 
> students.
>
> Ideally, I should be some configuration like this:
>
> max.participants.count=4
> max.participants.project=20
> max.participants.course=50
> max.participants.onlinecourse=30
> max.participants.tutoring=10
>
> This way, the number of users per site is shown on the site setup 
> tool, while adding participants.
>
> This must be set by the sakai admin, with the possibility to change it 
> per created site, just like how site quota works.
>
> Besides, we are not using any roster or student systems.
>
> To put it simple, *It's a quota for site members.*
>
> Yours,
> Alaa NIZAR
>
>

-- 
Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org
Skype me! (but let me know in advance for the first interaction) - nealkdin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/385daac7/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/385daac7/attachment.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1251 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140710/385daac7/attachment-0001.jpg 