I’ve just finished updating SLK for a UK school who had problems with learners disabled in Active Directory showing when they were assigning work through SLK. Firstly, I must say that this is a solution for a particular problem that they had and isn’t really a general purpose solution. If a learner is disabled, you should really be displaying them so you can assign then work. They may only be disabled temporarily, e.g. as puishment for computer misuse, but will still need to do the work when they are re-enabled.
The situation this school was in, is that they are running the Sims Learning Gateway (SLG). Part of how that works is that there is a component to create AD users and class groups based on the data in Sims. However, the users created by SLG are then ‘consolidated’ with the ‘real’ AD users, so these can then use the Sims web parts. As part of the consolidation process, the SLG users are disabled and the real users are added to the class groups, however the disabled SLG users are not removed from the AD groups.
Now the school were using these AD groups to assign SLK Learner permisssion to in order to assign work. So when the teachers came to assign work and selected their class group, each pupil was represented twice in the list which was a bit confusing.
The solution was to update the SLK code so that there is now a setting to hide disabled users. This will mean that when SLK goes to get the list of all Learners on a site it will ignore users in Active Directory groups who are disabled.
To get this set up you will first of all need to download and upgrade to the version with the setting in on the 1.3.2 build page . Then set the setting by:
- Go to the Configure SharePoint Learning Kit page in SharePoint Central Administration.
- Make sure that the correct site collection is selected and then click ‘Click here to download the current SLK Settings file’ near the bottom of the page.
- This will open up the SlkSettings.xml file in a new browser window. Save this to disk.
- Open the saved file in a text editor e.g. notepad (do not use Word or similar)
- Add the attribute HideDisabledUsers=”true” to the file as indicated in the screen-shot
6. Then upload the modified SlkSettings.xml file by adding it the page to “New SlkSettings file:” and clicking OK.
This will work for schools using Sims Learning Gateway with the same issues, but I wouldn’t necessarily recommend it for anyone else. My personal preference is to give the individual users the appropriate permissions on the class sites rather than using groups. Groups will always cause issues when it comes to rollover and I just think it’s cleaner and more intuitive to have the direct permissions. I would also have removed the disabled users from the groups. Of course I’ve got the toolset to do all of this easily.
One of the minor problems with SLK was that on the Assignment Properties page the Start and Due dates were always being shown in US format, no matter what the regional setting were. There was a really simple fix, you just need to set the LocaleId of the DateTimeControl and then it will display the date in the regional format of the site.
spDateTimeStart.LocaleId = SPWeb.Locale.LCID;
spDateTimeDue.LocaleId = SPWeb.Locale.LCID;
A version with this fix in is now available on the 1.3.2 build page.
The logo for the Learning Gateway User Group was designed by Sam Dolan of Pink Petrol. I just want to say that he’s done a great job on this and the SharePint one. I’m sure he’d be available to work on your site as well if you like what he does.
Alex Pearce has worked hard to get a Learning Gateway User Group up and running and it’s now live at http://www.learninggateway.net/. It’s all about the use of SharePoint in education, not just the CodePlex Microsoft Learning Gateway. So if you’re in education and using SharePoint, get yourself over there and register, and we can build a vibrant community and help everyone improve their gateway.
How do I see this in relation to the SLK & LG discussion forums?
I think that they compliment each other. I would see the CodePlex forums for more technical issues, mainly around problems with the typical user being the SharePoint administrator. Then the Learning Gateway User Group would be more about best practises, getting other application integrated and how to use it, with the typical user being more along the line of a VLE manager or user.
When an e-Learning package is accessed for the first time, SLK will cache the package on the web front end file system. Caching consists of unpacking the zip file and storing it on the file system. Subsequent requests will use the cached package, as long as they are not outside the cache expiration period. This will speed up subsequent showings of the package. Large packages are going to have a delay the first time someone accesses them after a cache expiration as they are unpacked.
Once the package is read from the cache then SLK will read the manifest to determine the navigation of the content and generate the table of contents for the frameset. Once this is generated the frameset is shown to the user who can then use the table of contents to navigate around the content depending on the sequencing rules of the package.
How the content is then sent to the user depends on how the content has been written. Typically each navigation node will be a separate item in the zip file, which will be downloaded when the user navigates to it. This will lead to a slight delay every time the user navigates between activities, the length of which will depend on the size of that activity and the network connection between the browser and SharePoint – just like any other web content being downloaded. I can also imagine that there are some packages which initially download all the content of all the activities. This will lead to longer start up times again depending on the size of the content, but quicker navigation within the package.
Cache Settings
The default cache settings are to use a cache on the individual SharePoint server and to keep it for 3 days. After this it will be removed. In a server farm this means that each web front-end server will maintain it’s own cache, leading to several initial requests as the load balancing passes requests to different servers. The cache location can be set in the SlkSettings file allowing the farm servers to share a cache. This should allow more hits on the cache and hence less unpacking.
Cache settings are set in the SlkSettings file and hence are on a per site collection basis, allowing you to have different settings for different site collections. The 2 settings are PackageCacheExpirationMinutes and PackageCacheLocation.