A stated role of the e-learning team is to develop an effective elearning community at the University, and to share effective practice. The primary vehicle to achieve this is the e-learning practitioners forum. This is both a face to face and an online community which aims to connect people and share effective practice.
I’ve not had a chance yet to look at the attendance of the face to face events, however, I have reviewed the online community. My first observation is that the online community is not working. In terms of participants then 57 people are enrolled on the course. This is a very low number given the number of staff engaged in e-learning at the University.
The following summaries the last accessed date; only 40 people actually accessed – so some got enrolled but never been in !
- accessed in last 30 days – 3 people
- accessed between 31 – 90 days – 5 people
- accessed between 91 and 200 days – 16 people
- accessed between 201 and 350 days – 15 people
- never accessed – 17 people
Given peoples poor access then this forum must offer little to meet peoples actual needs. Therefore, there needs to be a re-design, which includes a go back to basics and state the aims of the eLPF.
Other promotions – the eLPF needs to become the focal point, so the exit strategy for all face to face actvities should be visit the eLPF. Also, an activity in workshops should be to undertaken on the eLPF.
Finally, the eLPF needs to have a pre-booked number of events for the whole year.
So it is a great idea, there is a need for a vehicle to share effective practice, encourage people to connect with each other and promote a learning community. The eLPF is the vehicle to do this, it just needs to be given the clear focus and priority.
As many in the team know we have been experimenting with tags and yahoo pipes. I can now show a little of the output (thanks Nitin and Dan).
Scenario: Andy and Nitin are working on the audience response service, and we tag reading material using different social bookmarking tools. We want to display this in the audience response systems blog (http://blogs.bath.ac.uk/ars/). However, we can then also display this in the e-learning pages of the LTEO web site (see a test page … http://www.bath.ac.uk/learningandteaching/rsstest/test.php) the beauty of this is that we can wrap this with lots of other material, i.e., news items from different services etc., So a different audience can access the same information, and we don’t have to do any additional work 🙂
Given the recent progress I’d suggest that we use yahoo pipes to help bring information together.
LTEO e-learning web site – we can include and display an rss feed in the main area of the LTEO web site. This will allow us to use it as a rss aggregator to display rss content. I’d like to create a number of new pages;
pilots, projects and services – this will give background info to our current projects, pilots and services (Moodle, OUE, SMS, ARS, Heat3). This page will link to the individual blogs / wikis. Part of these services is that the lead person is expected to write a minimum blog post (a 250 word news update (once a fortnight)). These will be brought together via yahoo pipes. The RSS will be included within the page. This will act as a hook to keep people informed.
This is the feed of news (rss entries) from the internal services and projects run by the e-learning team. At the moment this is Moodle and Audience Response Systems. The pipe pulls in the the 2 most recent posts from the individual blogs.
For this to work then we need to standardise these support sites.
Another use of yahoo pipes is to collate what people are reading (bookmarking) about these services. For instance, see http://blogs.bath.ac.uk/ars/. Each site will include bookmarked resources that are drawn together from all people. For instance, the yahoo pipe … http://pipes.yahoo.com/pipes/pipe.run?_id=jpIxAu9u3RGcDLmDBR50VA&_render=rss collates Andy and Nitin’s delicious bookmarks. For this to work then members of the team need to inform me of the rss feed that they are using to bookmark this type of resource, and then stick with it.
If we take the idea of developing a team timeline as a means of disseminating information about events we’ve run, events we’ve been to, stuff we’ve read (bookmarks and reviews), stuff we’ve presented, working papers we’ve published then an example would be … http://www.dipity.com/user/andyramsden/timeline/e_learning_team_at_the_University_of_Bath
This would be really easy to maintain given our use of agreed tags.
we’ve recently been discussing the idea of a monthly newsletter. The aim of the monthly newsletter is to inform staff at the university what the e-learning team have been upto … this is to address the fact communication can be poor and many staff don’t realise what we have been doing. Infact this would really help with updating the team who are dispersed. However, a further improvement on this is to generate this automatically. Currently, we have lots of different tools that we use to capture information about what we are doing, for instance, personal reflective blogs, team blogs, social bookmarking software, twitter accounts, presentation sharing apps and photo sites. these all generate feed outputs. we also use yahoo pipes to bring things into one feed. therefore, why don’t we use something like dipity to create a timeline for our web site …. see ….
http://www.dipity.com/user/andyramsden/timeline/personal – this pulls from my blog and twitter account. However, I can fine tune what is accessed using the rss feeds 🙂
I’ve added the monthly “resolved rates” into the Blog.
Can you please ensure;
1. everything is logged and resolved as quickly as possible
2. enter the worked time for the job
3. If you have not already started can you start including telephone help queries