Kevin M. Brokamp - October 27, 2005
Here is how we currently handle renames at Indiana University:
1. We receive an incident from ITPO. Oncourse is usually the last stop on the rename train so all of the other accounts (ADS etc.) have already been renamed.
2. We run the following query which tells us if the user has ever logged into CL-
select title from sakai_site where site_id like '%username'
3. If they haven't logged in (query returns with a value of 0), we get in and rename them on the classic side. If they have logged in (query returns with a value of 1), we run the following queries to check and see if they have any items in 'My Workspace' resources-
!--Lists files in My Workspace resources select * from content_resource where IN_COLLECTION like '%/user/kmbrokam/%' !--Provides information on folders located in My Workspace resources select * from content_collection where collection_id like '%username%'
4. If they don't have any items in resources, we proceed by renaming them in original Oncourse. If they do have items in resources, we rename them in original Oncourse, create a local Sakai account under their old username, log in under that account and pull down the resource items manually. We then create a local Sakai account under their new username and upload the
resource items to that account. After this is complete, we delete both of the local Sakai accounts and use the 'Become User' tool to make sure the resources are appearing under their new username.
There are some concerns with this process as it does not address how the student shows up under the gradebook (and I'm sure there are other things that probably need to get updated on the backend), but this is the process that's currently in place.