If a web application has been configured, a site collection can override that by having its own mapping configured.

Note that configuring SLK for a web application will not create permission levels in the site collections within that all of its site collections. If required, you will have to script this manually.

A prime example of the use of this would be if you wanted the Assignment List Web Part (ALWP) in the learners’ My Sites. You can configure the My Site web application and the the web part will be usable in every users’ My Site. As the ALWP defaults to learner view if an SLK permission is not set, it works nicely for showing their assignments.

As SLK runs on 2007 & 2010, I’ve so far been trying to keep the codebase the same for both versions which is why I haven’t added any PowerShell commands. I expect that I’ll change this in the next couple of versions.

The commands allow you to configure and list site collections and consist of:

slk-configure

This command allows you to configure, or re-configure a site collections’s SLK mapping. It allows you to set up the SLK database, the permissions used and the slksettings file.

stsadm -o slk-configure

-url <url>

[-databaseserver <database server name*>]

[-databasename <database name>]

[-createdatabase]

[-instructorpermission <instructor permission name>]

[-learnerpermission <learner permission name>]

[-createpermissions]

[-uploadslksettings <SLK Settings XML file name> | -defaultslksettings]

[-application]

* By default, integrated authentication is used to connect to the database. To use a SQL Server user ID and password instead, append the appropriate connection string information to the database server name — for example, instead of "MyServer", use

"MyServer;user id=myacct;password=mypassword".

For security reasons, integrated authentication is strongly recommended.

Only one of -uploadslksettings and -defaultslksettings can be used

-application must be used when configuring a web application rather than a site collection

slk-deletemapping

This command allows you to delete an SLK mapping for a site collection or web application.

stsadm -o slk-deletemapping

-guid <site-guid>

Not that you must use the site collection ID. The easiest way to get this would be by slk-enummapping.

slk-enummappings

This command lists of the SLK mappings in the local farm.

stsadm -o slk-enummappings

An example output is:

http://laptop01 (1c8288b8-ec84-4912-bc55-3569e7626b3a) –> Server=LAPTOP01;Database=slktest

http://laptop01/sites/gsdt (1eb7c24c-e7cf-4dea-9c3d-c49c7478f359) –> Server=LAPTOP01;Database=slktest

http://laptop01/sites/slk (25ac1434-a59c-4c78-8cf3-d343f0c79e92) –> Server=LAPTOP01;Database=SharePointLearningKit

http://laptop01/sites/gdst (e0ee8d39-7076-4d30-bc8f-601850f49ac7) –> Server=LAPTOP01;Database=SharePointLearningKit2

In this output the first line describes a mapping for a web application, while the other 3 are for individual site collections.

slk-getconfiguration

This command returns the details of a mapping for a site collection or a web application.

stsadm -o slk-getconfiguration

-url <url>

-guid <guid>

Returns the configuration for a site or web application.

Use either url or guid.

An example output is:

Database server: LAPTOP01

Database name: SharePointLearningKit

Create Database : False

Instructor Permission: SLK Instructor

Learner Permission: SLK Learner

Create Permissions: False

Reason

The reason I added this functionality is that a customer had a need, was willing to pay to get it developed in the timescale they needed and I decided it wouldn’t negatively impact the project. They needed it as they were using Active Directory Federation Services and had implemented some custom functionality in their projects which allowed them to associate users in the federated domains, with local Active Directory groups. Of course, SLK didn’t understand this, and couldn’t link the membership of the groups with the federated users. As SLK is a key part of their SharePoint implementation this was a problem.

They could have used the federated users in SharePoint groups which would have worked out of the box with SLK, but decided that it didn’t fit in with their architecture. So we figured out a pluggable method of enumerating the group members would work best. They can write a class which understands their architecture and just plug it into SLK.

Do Not User Active Directory Groups Implementation

As part of the implementation I’ve created a plug in which prevents the use of Active Directory groups for assigning work through SLK. This was mainly as a test case for the pluggable architecture, but I choose this as it is a potentially useful functionality rather than just a random test. When this plug in is chosen no active directory groups are displayed when choosing SLK Members. The two main areas where SLK Members are displayed are the assignment properties page when creating or editing an assignment and the SLK Members web part.

I don’t expect this to be used very often, but I can see the occasional use of it.

Configuration

This is configured in the SlkSettings.xml file i.e. at the site collection + level. To configure it you add a DomainGroupEnumerator element just before any Query elements.

The DomainGroupEnumerator has two attributes:

1. Type. This is the fully qualified type name of the class which is being plugged in.
2. Assembly. This is the strong name of the assembly containing the type.

So for the Do Not Use AD Groups implementation the configuration entry would be:

<DomainGroupEnumerator Type="Microsoft.SharePointLearningKit.DomainGroupEnumeratorNoGroups" Assembly="Microsoft.SharePointLearningKit, Version=1.3.1.0, Culture=neutral, PublicKeyToken=24e5ae139825747e"/>

As this is part of the SLK project there is a short version of it which is

<DomainGroupEnumerator Type="None"/>

To use the default implementation, which enumerates AD groups just leave out the DomainGroupEnumerator element or have an empty Type.

Implementing Your Own Domain Group Enumerator

To implement your own version of a Domain Group Enumerator, all you need to do is:

1. Be using a version of SLK which supports this functionality. i.e. 1.7 onwards, or source code change set 683742a29967 onwards (24 March 2012).
2. Create a class inheriting from DomainGroupEnumerator.
3. Override the method EnumerateGroup. The method signature is:

public abstract DomainGroupEnumeratorResults EnumerateGroup(SPUser domainGroup, SPWeb web, TimeSpan timeRemaining, bool hideDisabledUsers); 

The parameters are:

1. SPuser domainGroup.
2. SPWeb web: The SPWeb the permission is for. This may be needed to add users to SharePoint if they aren’t already added. Used by the default implementation as not all group members may have accessed SharePoint before. May not be needed for other implementation.
3. TimeSpan timeRemaining: The time remaining to enumerate all groups. This can be ignored as SLK will check it before enumerating any more groups if there are any. Used by the default implementation to check time elapsed before enumerating nested groups.
4. bool hideDisabledUsers: Whether to hide disabled members of the group. Primarily used by the default implementation.

The return value is a DomainGroupEnumeratorResults. This has 3 properties which must be set by the implementation:

1. IncludeGroup. bool. Whether to include the group in the SLK membership. Defaults to true.
2. Users. List<SPUser>. Add the group members to this list.
3. Errors. List<string>. Add any errors to this list.

If you want to look at the two included implementation, all the domain group enumerator classes are in the source code in Slk\Dll\enumerateDomainGroups.

The following is a simple proof of concept script to initially set the SLK permissions on a site. It will add permissions for specified Active Directory users or groups to specified existing sites in SharePoint. You could easily extend it to create sites by checking to see if the site exists first, and if not running New-SPWeb.

The script runs from an input csv in the following format:

Site,User,Role
http://laptop01/sites/slk/class1,demo\learner1,SLK Learner
http://laptop01/sites/slk/class1,demo\learner2,SLK Learner
http://laptop01/sites/slk/class1,demo\teacher,SLK Instructor
http://laptop01/sites/slk/class2,demo\teacher,SLK Instructor

For each line in the input file it adds the user to the given site, with the given permission level.

To use save the following PowerShell as a ps1 file, create an input csv file called sitePermissions.csv in the same directory and run the script.

Add-PSSnapIn Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue

function AddPermission($web, $userName, $permission){    # Break inheritance if required. Argument is true if copy existing permissions or false to strip all    # permissions    if ($web.HasUniqueRoleAssignments -eq $false)    {        $web.BreakRoleInheritance($true)    }

    $user = $web.EnsureUser($userName)    $roleAssignment = New-Object Microsoft.SharePoint.SPRoleAssignment($user)    $role = $web.RoleDefinitions[$permission]    $roleAssignment.RoleDefinitionBindings.Add($role);    $web.RoleAssignments.Add($roleAssignment)}

$csvData = import-csv sitePermissions.csvforeach ($line in $csvData){    $web = Get-SPWeb $line.Site    AddPermission $web $line.User $line.Role    $web.Dispose()}

Running this with the sample data above gives the following before and after screenshots on the permissions:

Notes on the script:

1. There is no error handling so if your input in incorrect e.g. typos in your site, user name or roles, you will get screens of red error messages.
2. Line 1, Add-PSSnapIn ensures that the PowerShell comandlets are added into the current session if not already present.
3. The actual adding of the permissions is put into a function to break up the script and improve readability and maintainability.
4. Permissions can only be added to sites which have unique permissions, so if the site doesn’t already have permissions it breaks them and can either copy the existing conditions, or start from none depending on the value of the argument passed to BreakRoleInheritance.
5. EnsureUser is used to make sure that the user is added to SharePoint before trying to give them permissions
6. To change the name of the input file, just change sitePermissions.csv in the script.
7. It’s not particularly optimised as it opens a new SPWeb for every line. You could check to see if it’s a different site on each line and only dispose and create a new one if it is different.
8. The script will still work if the user’s permission already exists.

This is a simple script suitable for initial setting of SLK permissions. It doesn’t attempt to remove any permissions if no longer required, or do anything else to the site apart from breaking inheritance.

For a more comprehensive solution which can completely provision a set of sites, including setting any setting on a site, adding and removing permissions and automatically adding teachers’ sites to their list when assigning permissions, as well as a multitude of other functionality, then please investigate our managed service Salamander SharePoint. This will do all this and more.

To counter this there is now an option to show the delete option or not.

When this is enabled the delete option is present for files and directories.

When it is disabled the option is not there.

Note that the Show Delete option is only valid if Is Writeable is enabled as well.

By default the Show Delete option is disabled, and so is safe for users by default.

Summary

Earlier this week, preliminary documentation was released for the next version of SharePoint. One of the really exciting features from our point of view is a new educational component. Buried away in the mass of documentation is a document about the Client Side Object Model access to the educational features.

This functionality seems to have some concepts similar to SharePoint Learning Kit (SLK), but then expands it and obviously it’s built into to SharePoint as a first class component. Whether this is a core part of SharePoint at one of it’s license levels, or an additional product with or without additional licensing costs is unknown at the moment.

As the document I’m working from is about the Client Side Object Model access to the educational features so it’s all a bit of my guess how it all works. It may well all change of course, or even be dropped.

Core Concepts

Reading between the lines it looks like everything is stored in standard SharePoint lists and sites, rather than a separate database like SLK. There seem to be 2 core concepts:

1. Academic Document: "An education entity that represents any document stored in a SharePoint library for a course. An academic document includes, but is not limited to, lessons, assignments, submissions, events, and grades."
2. Education Community: "Represents an academic collaboration site (2) for a course. An education community includes, but is not limited to, courses and study groups, and also includes a collection of education entities."

An education entity is anything to do with the education functionality.

My reading of this is that the teacher and learner roles are going to be controlled by access to SharePoint sites, whether this is custom permission roles as in SLK, or some other mechanism linked to the site is unclear.

Then all the artefacts associated with learning are going to be items in lists and/or document libraries. This makes a lot of sense as it makes transitioning to the cloud and Office 365 vNext, much easier. One of the things which stops SLK working in Office 365 is the necessity for an additional database, and one of the ways I could see round that was to rework it to run off lists rather that a DB, which is obviously a huge amount of work.

Sites

So, just like SLK, it looks like the groupings are based around sites in SharePoint, where these are defined as Education Community and a sub-type of that called Course.

A Course looks like the type of site you would normally use as it has the associated entities you would expect to teach with such as assignments, lessons, grades, events, documents and more.

The base community site really just has memberships so is probably just used as a building block in the object model to build other types of communities off. Although study groups are mentioned above, that’s the only mention of it I could find. Maybe you would use a base site for storing content for self directed learning.

Finally, an education community can have a status of Planning, Active, InActive or Archived. It looks like the students only get permissions when the status changes to Active, and the site turns read only when changed to InActive.

Archived is an interesting concept for classes/courses from previous years, but there’s no more mention of it.

Notes on Academic Documents

Assignment

This is a similar concept to an assignment in SLK.

• You can assign to all members of a community or a subset of them.
• It has a start and a due date. No clue as to whether the assignment is available after the due date or not.
• It has a format which is one of None, Document, Quiz and NonDigital. Does this mean that there will be a quiz creation tool built in? My guess is that it does and that packaged content such as SCORM packages will be a document type.
• The assignment result can be numeric or a grade which are separate objects.
• There is a property to show if they need submitting or not, which would handle assignments such as read chapter 3 of your book.
• There is a sequence property which specifies the order in which it is used for content delivery. Presumably this allows you to chain assignments together to create a course delivery structure.
• Status. An assignment has various statuses it goes through: Unassigned, Assigned, Grading Started, Grading Published. This seems very similar to how SLK handles it, just more explicit. Category.
• An assignment can have a category. These look to be specific to a community (site) and have a weighting, which must be used in giving an overall grade for the course.
• CourseMaterials. A collection of documents associated with the assignment. Looks like you can have multiple supporting documents.
• Events. A collection of associated events.
• Lesson. The associated lesson for the assignment.
• AssignedAssignments. The assignations to students.

AssignedAssignment

This represents an assignment as assigned to an individual. The concept and most of the properties are similar to SLK. Differences are:

• Documents. These are of type PersonalMaterials which are presumably documents personal to the student and no one else can access, except potentially the teadher. Must be a similar concept to the SLK drop box.
• Submissions. What the student has actually submitted. There’s not much information on what this actually is, but when submitted it becomes read only to both students and teachers.
• Status. One of Unsubmitted, Submitted or Graded.

Lesson

This looks fairly self explanatory. It basically has a name, description and sequence. It can have assignments, documents, events, child lessons and a parent lesson.

I imagine that it will be based around a core document, although what format that is and how it displays is anybody’s guess.

Grade

Assignments can either be marked as a numerical value or be assigned a grade.This have a name and a score – the score presumably for giving a score across the course. A grade is associated with a course (site). I don’t know if they can be shared across courses.

Event

Represents a scheduled event. I’m not entirely clear what role this plays.

That was a short summary of the core types in the education component. There are many more, but hopefully it’s enough to give us an insight a feel for how the component is going to work.

Package Formats

The object model has methods for importing Common Cartridge packages. The precise text is "Application-layer request to initiate import of a common cartridge or content packaging file". So potentially other formats can be used as well.

The import looks like it will import it into a specific Course (site) and create lessons based on the content, which makes sense to me as that’s basically what Common Cartridge is designed to model.

There is no mention of SCORM in the entire document. However, the object model doesn’t seem to cover actually performing the assignment as such, so any package player would seem to be out of scope of the Client Object Model. I would be highly surprised if SCORM packages were not supported given that it’s the most common assignment format (of packaged formats of course) and the entire US military electronic training runs on them.

Overview

This looks like a fantastic addition to SharePoint for educators. First class support for a learning environment built in to SharePoint with features above and beyond what SLK delivers.

I’m really looking forward to getting my hands on it when it’s released to Beta.

However, where does this leave SLK?

Well that all depends on the licensing model. If it’s free in all versions, then SLK will be pointless for anyone on SharePoint vNext. If there’s a cost to it, even if it’s just because it’s in a higher edition to that which you have licensed, then SLK may well continue to be a useful tool, especially if you need to play SCORM packages.

Of course, as the concepts seem to be very similar, there’s a great argument for using SLK now to get used to this type of functionality. After all it’s not going to be available until late 2012 at best, probably more like 2013.

Cascading drop downs are where you have linked drop down boxes where the contents of the second drop down depends on the selection of the first one. They are used to target selections and make choosing them much easier. The canonical example is choosing a city where in the first drop down you choose the county/state and the second drop down is then filtered to the list of cities actually in that county/state.

SharePoint Support

SharePoint 2007 didn’t natively support cascading drop downs in list forms. There were a couple of workarounds which either involve adding a solution onto the server or building a JavaScript version using the SharePoint web services.

However, in SharePoint 2010 Enterprise version, you can implement Cascading Drop Downs out of the box with no code. The 2 features which make this possible are:

1. InfoPath list forms.
2. Browser based support for the cascading drop downs in InfoPath 2010.

Background

In this example I’m going to implement a system for listing after school activities. The school is split over 3 sites and as part of creating the activity the teacher needs to choose the site the activity is on, which will then allow them to choose the room the activity is in. In addition to this, we’ll add some finishing touches so that the room value is cleared when the site changes and the room drop down shouldn’t be enabled until a site has been selected.

How to Implement Cascading Drop Downs

Before you begin make sure that the site collection feature "SharePoint Server Enterprise Site Collection features" is activated or you won’t have support for InfoPath forms.

1. Create the Lists

Firstly you need to create 2 lists to store the sites and the room. So create a custom list called Site and add some values to it, in this case I chosen Centre, East and West. No additional columns are required.

Next create a custom list called Room and add a lookup column to the Site list. This column should be required and link to the Title column in the site list.

Next add some rooms to the Room list.

Now we need to create the actual after school activities list. This can contain whatever columns you require for its use, but also a site a room column which are lookups to the Site and Room lists. Here’s the list with a couple of entries in.

Now when we Add a new item you can see that the room drop down contains all the possible values, no matter what the site selection is.

2. Link the Room Drop Down to the Site Drop Down

Now we need to modify the form so the the room drop down depends on the site drop down. To enable this select the list tab in the ribbon and click Customize Form. For this you need InfoPath 2010 installed on your machine to edit the form. Once the form is published your users do not need InfoPath installed locally.

Once you click on Customize Form it will open up in InfoPath.

There’s now several steps to go through to enable the cascading drop downs. In a nutshell you create a new data source pulling from the room list, then add a filter on the Room drop down to only show items from the room list with the same site as that in the Site drop down.

Create the Data Source

First of all right click on the Room drop down and select Drop-Down List Properties to bring up the properties for the drop down.

First we need to add a new data source so click on Add next to Data Source,

and step through the wizard. You want to create a new connection to receive data i.e. the defaults, and select the source of the data to be SharePoint library of list.

Next you select the location of the site which as we opened from within SharePoint should be already correctly prefilled, and in the next step select the Room list.

In the next step you need to select the fields you want from the data source. You need to select the ID field as that is the actual value written to the activity room column, the Title column to display and the Site column for the data to filter on. You can sort on any column you want, but in this case only Title makes any sense. You can then choose to store the data in the form template for offline mode, but this generally isn’t required.

Finally you need to choose a name for the data connection. As long as it’s descriptive and unique it doesn’t matter what you choose. The default name is the name of the list with a 1 on the end. When you finish you’ll be taken back to the properties form where the name of the data source will have been changed to the new one you have just created.

Filter the Values

Next we need to filter the values in the Room drop down based on the selected Site. To start this we click on the button next to the Entries value, then on the Select a Field or Group window click on Filter Data at the bottom.

To add a filter click the Add button and then select the Filter Conditions.

For the filter we are looking to create one which limits the data to only those rows which have the Site value equal to the selected Site i.e. the site from the main data in the form. To generate this the filter needs to be "Site" "is equal to" "Select a field or Group".

This will pop up another window to Select a Field or Group. You need to change the Fields drop down to Main and then select the data field Site. Finally click OK and the result will display Site in the third drop down in the Specify Filter Conditions window.

Click OK to go back to the Filter Data window, OK to go back to the Select a Field or Group window and then OK again to go back to the Drop Down Properties Window.

Finally in the drop down List Box Properties you need to change the Value to d:ID by selecting it via the button to the right. This is because internally the lookup value stored is actually the ID in the lookup table. If you leave it as d:Title you will get an error when you try to save the list item. Once this is done click OK.

Final Touches

At this point you can publish the form and you will have a working cascading drop down. When you select a site the room drop down will be populated with the appropriate rooms. However, there are a couple of problems with it. Firstly, the Room value is not cleared when changing the Site. As the room value will not be in the filter for the new site value it will get changed to the id value which will be confusing for your users. Secondly if the Site is not a required field the Room Drop Down is still enabled if there is no Site chosen.

Both of these can be resolved with rules.

Clear Room Value When Site Changes

To clear the room value when the site changes you need to add a rule to the site field. In InfoPath select the site field then, from the ribbon use Add Rule | This Field Changes | Set a field’s Value.

Then it’s simply a case of selecting Room for the Field and leaving the Value blank.

Publish the form and test – It’s as simple as that.

Disable Room Drop Down When No Site Selected

To disable the Room Drop Down again add a rule, but this time you need to add a conditional formatting rule. To add this select the Room field and then from the ribbon select Manage Rules. This will open the Rules side bar. From this side bar select New | Formatting. This will then add the formatting options to the side bar.

Choose a suitable name for the rule then click on the "None" under condition. This will open the Condition window which is very similar to the Filter Condition one before. This time we choose "Site" "is equal to" and "Use a Formula". The Insert Formula windows pops up and just enter "" for an empty string.

Once you click OK to save the condition, just select "Disable this control" in the side bar and we are done. Publish the form and test, this time the room drop down will be disabled when no site has been selected.

Conclusion

SharePoint 2010 Enterprise Edition allows us to easily create powerful InfoPath forms incorporating cascading drop downs without any code or installing any additional solutions onto the server.

SharePoint Saturday is a free community event devoted to SharePoint, and this year is being held in Nottingham. There’s more information at Home – SharePoint Saturday UK. It’s got a fantastic line up of speakers and well worth attending if you have any interest in SharePoint, whether an IT Pro, Dev or End User.

I’m attending so if anyone wants to talk SLK or SharePoint in education, I’d be happy to meet up.

I’ve just released SLK 1.6 to Beta on the CodePlex site. This has actually been ready to go for a while, several months in fact, but I haven’t managed to find the time for documentation of the new functionality. I’ve now taken the decision to release it without the documentation so that people can at least start using it and feeding back any problems.

The main changes are:

• Better handling of not quite fully compliant SCORM content
• Textual grading as well as numeric (optional) e.g. ABC type grades
• Quick assignment type. That is assignments not based on a document. This should make it much easier to use for a homework diary, especially if the assignment is along the lines of "Read chapters 1 & 2 of book y."
• Email alerts. The most requested extra functionality.

An example from a school might be:

Here’s a sceenshot of the calendar’s overlayed in month view. The Whole School events are in green, the Exams in yellow and the staff in blue.

  This all works great out of the box. The problem comes when you don’t have permission to one of the calendars. So when a student views this they can see all the events from the Whole School and Exams calendar, but also get the error message "Unexpected response from server".

This doesn’t look very good.

Luckily there’s an easy solution to this. You just need to add the following css to the page. The easiest way is through a content editor web part, either directly in it, or my preferred method is to link to a text file with it in so it can be reused.

<style type="text/css">.ms-acal-error{    display:none !important;}</style>

This will hide the text and error image from showing so they won’t know that anything is amiss, or that there is a calendar they don’t have access to unless they look at the page source.