Richard Willis – SharePoint Learning Kit Coordinator, SalamanderSoft Owner

Note: This is all based on preliminary documentation and could all change and so the following is pretty much just speculative. The information below is all from publically released sources. It may well be dropped before final release.

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.

What are Cascading Drop Downs and why do we want them?

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.

There are currently still places available for SharePoint Saturday in November.

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.

The Calendar Overlays in SharePoint 2010 is a fantastic feature which allows you to display multiple calendars in the same view. This allows you to logically partition your calendar events into separate calendars and view them all together without having to lump them all in one calendar. This makes maintaining the calendars far simpler, especially as each calendar can have it’s own permissions limiting read and write access to the events.

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.

Introduction

As part of our Salamander Online Reporting Web Parts we needed to convert students’ reports from Word format into pdf format. There’s no built in functionality for doing this on the fly in SharePoint, and installing and using Word itself on the SharePoint server itself to use would be a great way of bringing down SharePoint, as Word Automation is not designed for server side processes.

So after a lot of searching and evaluation we decided to go with Aspose.Words which we embedded in our web parts. As part of our purchasing negotiations Aspose asked us if we would review their Aspose.Words for SharePoint product which they have recently released. As this could be of interest to my readers, and would reduce the cost of it to use, I agreed. Fundamentally, it is Aspose.Words embedded in a SharePoint solution which gives you easy access to its functionality through SharePoint.

It works on SharePoint 2007 & SharePoint 2010 and on all the versions including the free WSS3.0 and SharePoint 2010 Foundation.

Installation

Installation is a cinch. You just need to run Setup.exe on a SharePoint server and it will detect your version of SharePoint, install the correct solution file, deploy to selected web applications and activate the web application level feature.

Once installed, what does it do for you? It has two main features, document conversion and reporting.

Document Conversion

The Document conversion uses the engine in Aspose.Words. In their own words:

Aspose.Words for .NET lets you convert any document to any format that the product supports, these conversions are performed through our high fidelity processing engine which ensures minimal formatting loss. Simply put, your document conversions will look great!

Having used this to convert Word Xml documents to pdf for school reports I can attest to this. It’s not perfect, there are still a few issues when images are floated in Word Xml documents, but it’s probably as good as you can get without opening in Word. The best thing about it though is their support, this is fantastic. Even as an evaluation customer you can log issues on their forums and they will quickly get back to you and usually fix the issue very quickly and include it in their next release every month or two.

In Aspose.Words for SharePoint they wrap this functionality up in an easy to use format so you don’t need to write the .Net code to do it. You can convert either individual documents or entire folders at a time.

To convert a single document all you need to do is select "Convert via Aspose.Words" either on the document drop down (the edit control block)

or the button in the Ribbon (Copy group in the Documents tab) in SharePoint 2010.

Once selected you then choose how you want to convert the document, which of the 11 output formats you want to convert to, where to save the document and whether to overwrite an existing one.

Helpfully to choose the destination folder you can either type it in or use the button with ellipses on (…) to bring up a document library browser.

Once you have selected all of your options, or left them as default which is pdf format in the same document library in the same folder, called the same except for the extension, just click Convert and you are done. You are given a short report and the option to return to the source library or destination library.

Although convenient, converting individual documents in SharePoint probably wouldn’t justify the price for most organisations. You could easily open the document in Word and "Save As" the individual document in another format straight back into SharePoint. What Aspose.Words does give you is the ability to convert multiple documents at the same time and also, what is probably the most powerful conversion feature, use conversion in Workflows.

Multiple Documents

To convert multiple documents you can either select a folder instead of a document and "Convert via Aspose.Words" or, in SharePoint 2010, select multiple documents and then "Convert via Aspose.Words" on the ribbon.

The process is then very similar to that for individual documents with the converted documents ending up in the specified output folder. You also have an option to combine them into a single output document – which could be very useful for creating reports from individual documents. When combining multiple documents you can specify which order the documents are in the output document. One little bit of missing functionality is that when converting multiple documents which are not combined, you don’t have the option to change the name that will be saved as, it is just the original name with the extension changed.

Workflows

As I mentioned above, I think that the ability to use the document conversion in a Workflow is probably the most powerful feature of the conversion side of the product. Once installed, it adds two workflow actions to SharePoint one for converting documents and one for the reporting functionality. It’s as simple to use as any of the built in workflow actions.

For such a powerful feature, it’s so simple to use that there’s not much to say about it. As you can see from the screenshot you specify the output format, where and name to save and whether to overwrite existing documents, and that’s it. I’m sure you can think of many ways to build this into your processes.

Reporting

In addition to the document conversion functionality there’s a whole another side to the product which I will briefly mention. This is the ability to produce templated reports from data sources such as databases, SharePoint lists or XML data files. It uses the standard Word mail merge templating capabilities to design the visual layout and an xml configuration file to link up to the data. As with the document conversion, there’s an accompanying workflow activity and I can see the possibilities of doing interesting things combined with InfoPath forms, which after all are just xml documents.

This is definitely more complex and involved than document conversion, and you will definitely need a Power User or developer to write the configuration xml linking up the report template to the data. I can see it as a useful halfway house instead of using the developer tool Aspose.Words and completely coding the report generation.

Alternatives

There are alternatives to the document conversion which you would need to consider before purchasing.

1. Use Word’s Save As. As mentioned above, you can of course just open the document in Word and use the Save As feature to save in a different format directly back to SharePoint. This is obviously more clunky and it will depend on the number of documents you need to convert as to whether it’s suitable.
2. Use the Word Automation Services in SharePoint 2010 (Standard & Enterprise). SharePoint 2010 has built in document conversion functionality in the Word Automation Services. The biggest downside of these is that’s there’s no ease of use with them. You either need to write .Net or PowerShell code to convert your documents. Another big difference is that the Word Automation Services are asynchronous, i.e. run as a timer job which runs every 15 minutes by default. Whether this is a problem depends on your requirements. As expected the output fidelity of the Word Automation Services is spot on and the list of output types is very similar, although Aspose.Words for SharePoint does include epub digital book format.

So it is possible to do document conversion without Aspose.Words for SharePoint, however the product does wrap it up in a very easy to use format and doesn’t require any developers. I don’t think that there’s any doubt that the product is a lot easier than the alternatives above.

Conclusion

Aspose.Words for SharePoint is a very capable and easy to use product for converting Word documents within SharePoint. If you also use the reporting capability, then it’s even better. As with any 3rd party SharePoint product, there’s usually other ways to do the same thing, and you need to weigh up the benefits against the cost involved in buying the product or in replicating another way.

When running Update-SPSolution you can sometimes get the error:

Admin SVC must be running in order to create deployment timer job

There’s a very simple solution to this. Ensure that the SharePoint 2010 Administration service is started.

Once you have started that the command will run correctly.

Having removed the "Use a Meeting Workspace" option from individual calendars in my previous post, I wondered if there was a way to remove them from all existing and new calendars within a site collection.

I found a way to do it by modifying the calendar schema in the hive folder. However, although this works, it technically leaves SharePoint in an unsupported state, so I didn’t want to go down that route.

Then I had a thought that all the items in a calendar list are of the Event content type, so if you can modify that, to make the Workspace option hidden, then it would be removed from all calendars.

Unfortunately when you look at the Event Content Type in the Site Content Types gallery, the Workspace column is greyed out so you can’t edit it.

However, it proved to be remarkably easy to script using PowerShell:

# Script to remove Use a Meeting Workspace from all calendars
$siteUrl = "http://myserver/sites/mysite"
[system.reflection.assembly]::LoadWithPartialName("Microsoft.Sharepoint") > $null
$site = New-Object Microsoft.SharePoint.SPSite($siteUrl)

$contentTypeId = [Microsoft.SharePoint.SPBuiltInContentTypeId]::Event
$eventContentType = $site.RootWeb.ContentTypes[$contentTypeId]

$fieldId = [Microsoft.SharePoint.SPBuiltInFieldId]::WorkspaceLink
$field = $eventContentType.FieldLinks[$fieldId]

$field.Hidden = $true
$eventContentType.Update($true);

# Dispose the site object
if ($site) {$site.Dispose()}

The only slightly tricky bit was needing to use the FieldLinks property instead of Fields.

The $eventContentType.Update($true); line ensures that it updates all existing calendars in the site collection, otherwise it will just be for new ones.

I’ve actually increased the script by 2 lines to fit it in my blog by adding in the $fieldId and $contentTypeId. Originally it was even more compact.

Again, this takes effect immediately throughout the entire site collection with no need for an iisreset or an application pool recycle.

I’ve just deployed a custom meeting site to a customer to handle multiple meetings within one site. Hence the option to “Use a Meeting Workspace” when creating a new or updating a calendar item is unnecessary, so they asked me to remove it to prevent anyone using it by mistake.

When creating a calendar item (or updating) this is the dialog you get, with the Use a Meeting Workspace highlighted.

From SharePoint Blues I discovered that if you set the calendar list field to hidden then this option would no longer display. Taking this concept, I created a PowerShell script to set this to hidden on a one off basis.

The script is:

# Script to remove Use a Meeting Workspace from a specific calendar

function RemoveWorkspaceLink ([String]$siteUrl, [String]$calendarName)
{
[system.reflection.assembly]::LoadWithPartialName(“Microsoft.Sharepoint”) > $null
$site = New-Object Microsoft.SharePoint.SPSite($siteUrl)
if ($site -eq $null)
{
return
}

$web = $site.OpenWeb()
$list = $web.Lists[$calendarName]
if ($list -eq $null)
{
“Invalid list name ” + $calendarName
}
else
{
$field = $list.Fields[[Microsoft.SharePoint.SPBuiltInFieldId]::WorkspaceLink]
$field.Hidden = $true
$field.Update()
“Updated ” + $calendarName + ” on ” + $siteUrl
}

# Dispose of the SharePoint objects
if ($web) {$web.Dispose()}
if ($site) {$site.Dispose()}
}

RemoveWorkspaceLink “http://myserver/sites/site1″ “Calendar1″
RemoveWorkspaceLink “http://myserver/sites/site2″ “Calendar2″

I’ve written this as a function so that you can update multiple calendars at the time. If you saved this as a .ps1 file and then run it, the 2 calendars referenced at the bottom would be updated. Alternatively you could . source the file and use the function interactively, or just hard code the $siteUrl and $calendarName variables each time you run it.

The option is removed immediately you have run the script with no iisreset or application pool recycle required.

So with the script is run this is what you see with the Meeting Workspace option removed:

This works well for hiding it on individual calendar lists, but doesn’t affect any other existing calendars or ones created afterwards.

I’ve since found a way to update all calendars in a site collection.

I was recently creating some departmental sites for a school in SharePoint 2010 and wanted some metadata to attach to documents. I couldn’t find any ready made ones, so had to create my own.

I found a Mathematics taxonomy in the Journal of Online Mathematics and its Applications which is based on the Math NSDL Taxonomy Committee Report, April 2, 2002, with draft changes proposed for Section 9 by CAUSE, May 16, 2004. Further changes to Section 9 were approved by the Math Gateway Partners Group, April 29, 2005.

It looks fairly comprehensive to me, but obviously wasn’t in a suitable format for importing into SharePoint 2010, and was certainly too large to type in. So using vim and some macros I fairly quickly converted it into the correct csv input format for SharePoint 2010. It’s quite a detailed taxonomy and at a school level you will probably want to delete some of the terms, but it’s a good start.

Then I added a Managed Metadata column to the document libraries for the department, linked to the Mathematics term set. I made this required and allowing multiple selections, but defaulted it to the top level. This means that they can add more explicit tagging to help with searching and findability, but it doesn’t prevent the users adding documents if they don’t have the skills or inclination to tag properly.

You can download my finished csv file from here. I also created one for the level of content, covering Key Stages, years and qualifications and added another optional column for this. Finally I created another one for ICT, but this one is really basic as I couldn’t find a decent taxonomy for it and wasn’t really sure what’s covered at a school level.

Update: With thank to @stevegillott I now have a vastly better ICT set of metadata which I’ve updated here as well. It’s based on the UK National Curriculum.

Learning Possibilities+ are holding a free SharePoint event for schools on the afternoon of 8 March 2011 in Northampton.

The speakers are:

Stephen Heppell on the Future of Online Learning

Stephen works with governments and national agencies throughout the world on the strategic development of ICT. He will be talking about the future of online learning within the current economic climate.

Tom Rees on "How ICT and VLE’s can transform learning"

Tom is head teacher at Little Harrowden Community Primary School, and driving force in the Northants BLT ‘Better Learning using Technology’ Network.

Tony Sheppard on "Parental Engagement – moving beyond government targets"

Tony is the educationalist technologist, harnessing technologies manager at Northamptonshire County Council

There’s also demonstrations and technical queries of the LP+ platform and Adopt Consultancy.

For more details and to book see https://learningpossibilities.lpplus.net/Pages/NorthantsEvent.aspx.