[Deploying Sakai] [Building Sakai] Keeping access to graduated student's data
steve.swinsburg at gmail.com
Wed Apr 17 21:31:07 PDT 2013
Whilst not ideal, msgcntr stores the user's name with a post, possibly for
this reason (ie if students are removed) - gradebook could do the same and
fall back to that info if the user is not available - there would need to
be a way to fully purge a user from a site though.
Whilst I agree with Sam in that you could leave the users in LDAP and just
disable their ability to login/be added to new sites, this can potentially
be at odds with the normal deprovisioning practice of many institutions, so
a Sakai specific solution might be required.
On Thu, Apr 18, 2013 at 4:19 AM, Sam Ottenhoff <ottenhoff at longsight.com>wrote:
> We are looking for suggestions and ideas on how other schools are
>> dealing with this.
> If you still want to access information related to graduated users, they
> should continue to live in your central user directory, LDAP.
>> If you keep graduated students in the ldap, do you
>> see any performance issues as the ldap database grows? How large is your
>> ldap database (i.e., number of students)?
> I'm sure there are institutions and organizations with many millions of
> user records in their LDAP database. Unless your institution is storing
> large amounts of binary data for each LDAP user, the records are extremely
> small. LDAP was built for this use case, with its highly configurable
> structure and containers. I can't think of any better solution that
> continuing to store the users in LDAP.
> production mailing list
> production at collab.sakaiproject.org
> TO UNSUBSCRIBE: send email to
> production-unsubscribe at collab.sakaiproject.org with a subject of
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the production