[Deploying Sakai] [Building Sakai] Keeping access to graduated student's data

[Feliz Gouveia]

We use other providers other than Ldap, so that we can have other places to
go and fetch data. We used those providers basically for test data, and for
people outside our university - avoiding to register them as guests.

One solution could be to copy the student's data to another database, as
they leave Ldap, and update the provider's information. Other solution, as
mentioned, would be to copy the user to sakai_user.

The User Membership tool we developed allows an admin to search users in
providers other than the main, or standard authentication provider.

Feliz


On 18 April 2013 11:20, David Adams <da1 at vt.edu> wrote:

> Would it be possible to populate SAKAI_USER with the relevant data prior
> to the deprovisioning from LDAP?
>
> David Adams
> Director, Systems Integration and Support
> Virginia Tech Learning Technologies
>
>
> On Wed, Apr 17, 2013 at 11:31 PM, Steve Swinsburg <
> steve.swinsburg at gmail.com> wrote:
>
>> 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.
>>>
>>> --Sam
>>>
>>> _______________________________________________
>>> production mailing list
>>> production at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/production
>>>
>>> TO UNSUBSCRIBE: send email to
>>> production-unsubscribe at collab.sakaiproject.org with a subject of
>>> "unsubscribe"
>>>
>>
>>
>> _______________________________________________
>> production mailing list
>> production at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/production
>>
>> TO UNSUBSCRIBE: send email to
>> production-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
>
> TO UNSUBSCRIBE: send email to
> production-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>



-- 
Feliz Ribeiro Gouveia

Universidade Fernando Pessoa            http://www.ufp.pt
Centro de Recursos Multimediaticos      Tel 351-22.507.13.06
M.I.N.D. Lab                            Fax 351-22.550.82.69
Pr 9 de Abril 349                       fribeiro at ufp.edu.pt
P-4249-004 Porto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20130418/a72db3c6/attachment-0001.html