web analytics

Glow account management in the “free world” #EDUScotICT

I have been tracking progress with the Glow reprocurement in recent months.  It seems that after the procurement exercise was started it was abruptly stopped.  This followed by a period of public consultancy – which I think is still underway.  The timescales which relate to the procurement process are quite critical.  I understand, the current contract will end in September 2012, further more this will be a hard stop in view of the fact that the original 5 year term was extended to 7 with in the terms of the original contract.  At the end of this extended period I expected that the current contract would end to be replaced by something new and better.

I want to use this post to reflect on one critical aspect of the old and possible future service.  I am concerned here with the need for a core service which manages the creation of user accounts.  In the original system this was done by an account provisioning service which took its inputs from School MIS systems and then created all the necessary accounts through a batch process.  I did not use the plural for account here by mistake!  In Glow each user needs to have account provisioned for a number of different services including the portal, email, discussion boards, Glow Learn and so on. In addition it is necessary for each user to be added to any Glow Group to which they should belong.  This is a none trivial process which I do not plan to elobourate on – but I do want to make the point that although user access to all services in Glow is controled by Core ID giving the impression that there is only one service.  The Single Sign On service was mandatory requirement of the original Glow service – I hope it will continue to be a feature of Glow Futures.

In order to explain my concerns I have produced a short video which provides a highlevel overview of the issues as I see them.  In the video I detail the original Glow service components and also specualte about what might be needed to maintain an environment where users need only be concerned with accessing and using their accounts and all the component services with-out any need to be concerned with account setup or registration.  The Schools and Local Authorities would remain the authority for user account creation and maintenance.

click the following link to access the video – be patient will take a few minutes to download.
Video about account Management in Future Glow

 

What could Glow become? #EDUScotICT

Introduction
I was very impressed by the following post http://markc.visibli.com/share/GwIYOZ entitled “Edmodo – Could this be the new Glow?”.  I was impressed by this post not so much because of the product featured but the general commentary about its usefulness and ease of use.

What Glow needs to become
I have written a number of posts in this blog recently concerning how Glow might develop into a system which addresses the weaknesses of the current platform and exploits its strengths.  It seems to me that the above post does a great job of highlighting in a very rational manner some of the barriers present in Glow to wider and easier adoption.  Edmodo certain ticks a lot of boxes when it comes to ease of use and I definitely support the need for Glow to adopt a similar approach in the future.  I am not shy about referring to Glow in a future context as I do believe that does have a future which builds on what has already been achieved in this context.

Edmodo – signing up for an account
I do have an Edmodo account which I was able to set up simply by going to the website and completing the registration process.  But here-in lies one of my concerns.  All new users need to go through a self-registration process and there appears to be no need for corroboration of the users identity and profile information.  In order for any future system to be adopted for use in Scotlands schools, I strongly feel that user accounts should be created using a tried and trusted mechanism.  For Scottish school users, this system already exists so it must be possible for this system to be deployed alongside any new platform components so that we can know that only people trusted by the education system (schools, local authorities and the government) can have an account.

The account should be auto provisioned so that each user should be able to access their account by entering their known UID and PWD.

Facebook-like ease of use
This point is very well made in the post.  I feel that services like facebook have set a pseudo standard in terms of ease of use and user interface etc.  I commend any future Glow development to adopt the general goal of achieving the same ( or better ) level in terms of ease of use etc as is already available through tools like facebook.  Another requiremet here is a need to support access from a range of devices – so there is a fundemental need in my view to have developed in parallel apps which provide native access on mobile devices.

The need for a contractual relationship
I do not believe that it can be acceptable for Scottish Education users intellectual property to be trusted to any system where there are no guarantees regarding availability and feature development.  The value of establishing a national platform to support teaching and learning should be a national priority.  The continued development of Glow should not be allowed to occur in an ad hoc and undisciplined manner.  Whichever products are used to build the platform it should be ‘a given’ that the service provider(s) is/are under an obligation to provide, develop, integrate and maintain solution to provide a coherent, easy to use, predictable and dependable experience for all of its users.

Another important consideration here is who will own the contractual relation ship.  I consider this to be a major factor which needs to be addressed – to suggest that we can get the quality of service needed from some “free offering” is a very high risk strategy in my view.  I should be unacceptable to consider any strategy for Glow Futures which puts the service on any platform where there is no contractual relationship which helps to ensure that Scotlands learners and educations receive the quality service they deserve.

The Scottish Government needs to step up and take the leadership role acknowledge its responsibility for ensuring that the next version of Glow builds on the current service.  It is vital that the Government continues to invest in order to realize real transformation in the use of ICT in Scottish Education – lets demonstrate that we have the bottle to “finish what we have started”!

Scottish Unique ID for all citizens #EDUScotICT

Introduction
Imagine if every Scottish Citizen had a unique and trusted digital identity (Scottish Unique Identifier – SUID) that could be used as a key to accessing all government services and potential a myriad of other services.  Ideally this account which once setup is accessed through the use of a Unique Identifier (UID) and Password (PWD) and will be a life-long facility.  This could lead to a position where each user will have access to all the digital content they need via the credentials that are associated with this account.
This system will be trusted by a wired landscape of service providers including the likes of facebook, Google, Twitter etc.  Each time a user access a service for the first time through their SUID an account will be provisioned for them automatically and they will not be asked to provide any data about themselves unless it is a specific additional requirement of the service in question.
In a later phase, SUID will be come effectively a Digital passport for access to services around the world.

SUID scope
The SUID will be the means of access to the whole range of public sector online services.  This will include service provided by National and Local Government.  It will permit access to services in all expect of the public sector including Education, Health and Local and national Government.  The account will be provisioned at birth or entry to this country (by legal means).  Procedures for account provision should be embedded into the birth registration system and users will be provided with access to their account as soon as they need it to access services.
All of a user’s medical records would be tagged to their account and as soon as the user starts school they would be using their account to access services for education.  All local government services would also be accessible using the SUID.
When children are very young a solution would be put in place for their parents to access their account.

Digital Passport
The SUID could be considered to be the digital equivalent of a traditional passport which is internationally recognized and accepted as confirmation of a users real identity.  As such, a user could enjoy access to a wide range of internet bases services without the need to register separately for every service encountered.  This could of course be distinct from a public internet based Open ID service which can used with out any real need to confirm the users real identity.
There will also be occasions where a user will be required to provide additional authorization data, equivalent to the need for an entry visa when visiting certain countries.  In these cases the service provider would be responsible for gathering any additional data which is supplemental to the data available through the SUID.

Advantages of this approach

  • Internet services providers would be able to use an existing, validated identity to authenticate users or its service.
  • Each user would need to maintain only 1 UID and PWD combination – but
  • The base UID an PWD could be supplemented by and service provider in some way where data security was considered of sufficiently high priority – this might apply when the user is access personal medical data or financial and banking services.
  • Generally easier for end users who will have increased access to resources without the need to register with all services they encounter.
  • Once a user account has been provisioned it can be accessed in any part of Scotland.

Disadvantages of this approach

  • All eggs in one basket – if authentication system fails for any reason user will be denied access to all services.
  • Government needs to understand the mission-critical nature of such a service and maintain it for low latency and high availability 24/7.
  • Third party providers may not trust the service
  • There would be a need to set up and maintain a federation of content or service providers who support the system.

 

Universal search a core Glow service #EDUScotICT

Discovery of learning assets through search was an original requirement of Glow.  This should continue to be a requirement and furthermore, it is essential that we learn from the experience of Glow 1 to provide search in the most efficient and useful way.  I certainly do not want to dwell on the past but I will start this post by describing the original Glow search service which was not perfect

The Context
John Connell has often told the story of how when interviewing teachers, council officers and Directors of Education early in the SSDN project  (pre – Glow ) were asked what they wanted from Glow (looking forward ) – a common response was “Stuff………”.  It would be good if John could offer a deeper insight into this matter as there is underlying message!
There is no doubt that stuff was made available in and throughout the Glow Platform – but were teachers able to find the content which had been  uploaded – if they were not directed to it.  Sadly the original search facility in Glow as not capable of returning useful results to every search conducted – this was the case for a number of reasons.

Original Setup of Search in Glow
Glow is made up of a number of services each we have their own repositories.  The portal (MS SharePoint ) and the Virtual Learning Environment (Glow Learn – based on RM Kaleidos) to name only two examples.  There was a search capability on the portal page which could search only the portal repository and there was a much more “powerful” search tool in the Glow Learn which could search both the Glow Learn repository and some external sources (the search of third party or external repositories is sometimes referred to as Federated Search).

Search Scope
There were two search ‘engines’ available through the Glow Portal and Glow Learn as follows

  • Glow Portal Search – scope could return results referencing content which was stored in the portal (MS Sharepoint) repository.
  • Glow Learn Search – which could return results based on content stored in the Glow Learn repository and in addition links to some external repositories including the Learning and Teaching Scotland website and SCRAN.  The later was initially achieved using SRW/SRU (see here for some further information on this search standard http://techessence.info/node/48)

So there were two different places in the Glow environment where a user could access search which would return two independent results to the same query – this was not helpful.

Meta Tagging

In Glow learn it was possible to tag assets in a more granular manner.  Taxonomies were written so that teachers could tag learning assets according to the curriculum area to which the resource had relevance.  This opened up the possibility that a teacher looking for “Stuff………..” which was relevant to a particular learning outcome in the 5-14 curriculum (for example) would be able to search against a specific learning outcome and receive back a list of results which were relevant etc.  The matter of teachers having to Meta Tag resources that they were publishing did raise some concerns at the time and it was agreed that a minimum requirement would be that on upload, a meaningful title needed to be added to the asset.

Have things progressed?
Thinks have indeed progressed.  Later in the Glow project it was possible for the contractor to implement Open Search using the MS Search Server 2008.  This was applied to the Portal Search engine made possible a number of new and improved features as follows:

  • Users were able to have results returned based on their account permissions to access content.
  • Users could limit search results to include particular content types from the following list this Site, Documents, Spreadsheet, Videos, Acrobat, Images etc ( this list was configurable)
  • It was possible to use Open Search to include results from other Open Search enabled repositories.  (Currently, this includes ‘Published Glow Groups’, The Daily What News and the Learning and teaching Scotland WebSite)
  • The list of open search possibilities amounted to about many other sources such as bbc.co.uk, Flickr, YouTube, bing, Google safe search etc…….  but these have not been included to date.
  • Search could include results from Glow Blogs and Glow Wikis but this has to date not been implemented.  Ideally Glow blogs and Wikis should include a search API which supports identity if this is not currently available.

At this point it was still not possible to conduct search across both Glow Learn and Portal search engines.

So what are the requirements for Glow Future in this regard?
Whatever the future platform is for Glow I believe that the following needs to be openly discussed and a fully detailed set of requirements published.   Glow feature requirement should not necessarily be limited to the features which are currently generally available on internet based services.

I offer the following definition which is referred to below

A Core Glow Service is defined as a service which is accessible directly through the Glow Authentication ( or Single Sign On ) service.

I offer for the following suggestions for further consideration:

  • Glow should feature a dedicated search service which is accessible form the main portal but my also be presented to the user in other parts of the system (Glow Learn, Glow Collaboration tools etc…..) perhaps  this should be a standard tool bar type feature which is always available after login.
  • Search should be universal to the Glow Platform – this means that the underlying search engine should have visibility of and teh capability to search any and all repositories which are connected to Core Glow Services.  This should be considered as a base level requirement.
  • When searching for content on core repositories, users should have the capability to filter search results based on the asset ownership – so the user can see only assets they own, or assets owned but some other user where they have appropriate read permissions.
  • Search should only return to the user results which link to assets to which the current user has ( a minimum of) read access based on their credentials etc. so the target service must take the user identity as a search parameter.  This must apply to the results from core repositories and should also apply to result from federated search where user identity is relevant (this should include Google Apps if deployed, for example )
  • Federated search should also continue to be both possible and supported – this may require the continuation of either or both of SRU/SRW and Open Search.
  • Where possible Federated search results should be filtered based on the users credentials.
  • Having conducted a successful search a user should be able to refine the search – to for example find more resource published by and owned by the same author.

 

Does the “knowledge explosion” affect Glow Users? #EDUScotICT

As I walked the dog this morning I took time to reflect on a book that I am reading at the moment.  The book which is called “Teaching as a subversive activity” by Neil Postman and Charles Weingartner contains the following quote which is used to illustrate the concept of the “change revolution” – it is a long quote but worth reading completely.

Imagine a clock face with sixty minutes on it. Let the clock stand for the time men have had access to writing systems. Our clock would thus represent something like three thousand years, and each minute on our clock fifty years. On this scale, there were no significant media changes until about nine minutes ago. At that time, the printing press came into use in Western culture. About three minutes ago, the telegraph, photograph, and locomotive arrived. Two minutes ago: the telephone, rotary press, motion pictures, automobile, aeroplane and radio. One minute ago, the talking picture. Television has appeared in the last ten seconds, the computer in the last five, and communications satellites in the last second. The laser beam – perhaps the most potent medium of communication of all – appeared only a fraction of a second ago.
It would be possible to place almost any aspect of life on our clock face and get roughly the same measurements.
For example, in medicine, you would have almost no significant changes until about one minute ago. In fact, until one minute ago, as Jerome Frank has said, almost the whole history of medicine is the history of the placebo effect. About a minute ago, antibiotics arrived. About ten seconds ago, open-heart surgery. In fact, within the past ten seconds there probably have been more changes in medicine than is represented by all the rest of the time on our clock.
This is what some people call the knowledge explosion. It is happening in every field of knowledge susceptible to scientific inquiry.

This is illustrated graphically below

The main point!
People are all individual and will be at a different stage in their experience of the knowledge of and use of ICT.  I feel it is unrealistic to assume that all users have the capacity to move at the same rate of change as the knowledge explosion is progressing.  This is why CPD, in the context of the use of ICT in the classroom, is a fundamental requirement for (I believe) the majority of teachers in particular.  Any suggestion that we can simply drop technology on the education system and it will have an automatic and positive effect is a fantasy.  For this reason it is essential that we continue to help teachers and other professionals to adopt and make best use of technology for the sake of a better experience of learning for today’s ( and tomorrow’s ) pupils.

I certainly acknowledge that there are some people who have a propensity to understand and adopt new technology but I feel these do not necessarily represent the majority position.

It seems to be that the human body has been subject to natural evolution  which has taken place over many thousands and millions of years and this is the natural pace of change.  How can be we realistically expect the human mind to adapt in every case to the “knowledge explosion” – we need to recognize the value of staged and gradual introduction of technology.

Glow is a current focus for this movement in Scotland and as such has a core role to play – any careless destabilization of this platform will set back the progress of adoption of ICT in Scotland’s classrooms.

And Finally!!!!!

Think how much has changed even in the time since Postman and Weingartner wrote the above referenced book – some 40 years ago! – the internet was in its infancy, the web didn’t exist, all the incredible development in the past 40 years have probably added a thousand-fold to the sum of human knowledge since even then.