Author: Jan

A strong limitation of Microsoft LCDS

I have been playing quite some time now with Microsoft’s Learning Content Development System. I promised in an earlier post to put some content online, but that is where it went wrong. I just could not get the content published in any other LMS than the SharePoint Learning Kit.

After some testing, it seems that the content needs to be hosted on… a Microsoft IIS server. All my test systems were running Apache, PHP and MySQL (as most open source lms systems do).

For me, these are some serious limitations to LCDS as an authoring tool.

Adding a new language to Microsoft LCDS

Someone asked me if it would be possible to add a new language to the available language packs of the Microsoft Learning Content Development System. Well, as the system supports already multiple languages, that should not be that difficult. This is what I did (use at your own risk!):

  • Navigate to C:\Program Files\Microsoft\Learning\LCDSc\application\viewer. This folder contains a subfolder, one for every available language.
  • Copy the folder that corresponds most to the language you want to create. Or if no correspondence, copy any folder and give it a three letter language code.
  • Inside your new folder, go to the folder named shared. Inside that folder, there is a folder with the same language code, rename that to your new code.
  • Inside that folder, there is a file version.xml. Edit the file in Notepad and make the necessary changes.
  • Open the viewer folder inside that folder.
  • The file viewerstrings.js contains the different language strings for the viewer. Edit the file in Notepad and translate.
  • The Help and appart folder contain the help screens. Translate these if necessary.
  • Go back to C:\Program Files\Microsoft\Learning\LCDSc\application and edit the supportedLanguages.xml file with notepad. Copy one of the lines to add a new line for your language.

Done! The new language should appear when creating a new course!

Why “SharePoint for Dummies” is not enough for your end users…

Very often, I talk to IT-people about providing end user training for their SharePoint implementation. Recently, on two separate occations, two IT managers made the same remark: “Just give them the “SharePoint for Dummies” book and they will be fine.”

I really hate it when people talk about “dumb” end users. But this set aside, I want to make clear why this is not really a good solution for end user training for SharePoint:

  • A SharePoint end user training should always be a custom training: the SharePoint feature palette is so vast that while books discuss most of the features, companies only use their 20% of the functionalities. So why bother giving information about the ones you do not use?
  • There is more to it than just SharePoint functionality: very often, the implementation of SharePoint brings changes in work methods, procedures, information sharing… Those are specific for your organisation.
  • You need to sell your SharePoint solution to your internal audience. People are resistent to the change in their work habits, even if it is an improvement. Giving a book is not a very good sales pitch.

Microsoft released some interesting material to accomplish this. Very good material, but don’t make the same mistake: don’t throw this at your end user “as is”. Customize, customize…

Error at the end of approval workflow

An interesting problem this week: a customer configured a workflow in a document library, based on the out-of-the-box Approval workflow. The workflow seemed to work fine, but every time after the workflow completed, an error showed up in the workflow history: Error – System Account – An error occurred in <name of your workflow>. OK, I admit, I have seen more meaningful error messages ;–)

Nothing special was showing up in the logs. After some testing, we discovered that in the workflow the option “Update the approval status” was checked. As the document library did not have content approval activated, this was the cause of the error. Just deactivate the option or activate content approval.