Showing posts with label software. Show all posts
Showing posts with label software. Show all posts

Wednesday, 26 September 2012

The eLearning Industry

This post is primarily aimed at students studying the final year eLearning Multimedia unit at MMU, although it would be great to get the views of other professional across the sector. The post hopes to give an insight into the types of jobs in the field of eLearning...



The eLearning industry has grown exponentially in recent years due to an increased awareness around the benefits of technology to enhance learning, teaching and assessment (and actually, the whole student experience). Some of the benefits of technology include;
  • Aid learning and retention (see Mayer)
  • Anytime, Anyplace access to materials
  • Support/facilitate social learning across geographical boundaries
  • Environmental advantages
  • Reduce travelling
  • Reduce costs

To this end, a range of new career pathways has emerged. According to video (below), the top 10 in demand jobs in 2010 did not exist in 2004. So by this very fact we are currently preparing students for jobs that don’t yet exist, using technologies that haven’t been invented, in order to solve problems we don’t even know are problems. This places an obvious challenge on our education system.



The careers developed for the eLearning industry range from being purely technical, to purely pedagogical, with some in between. N.B. the following is a brief summary of some these roles - there will be many things I haven't included, but if any readers if feel I've missed something important, please share your views in the comments section.

Technical jobs: might include scripting/coding to integrate various systems. Take for example, MMU’s Moodle installation. When you log into a unit, the information in the right hand column is created dynamically. The Assessments block, which enables you to access more info about coursework/exams, has been custom developed to link with the University’s Coursework Receipting system. The information it presents doesn’t actually live in Moodle. The same is said for Reading Lists.

Other roles may include the hosting and development of VLEs. For example Moodle is an open source VLE so developers can write bespoke themes based on CSS to adapt the look and feel of the VLE. The same applies to other systems as well; things like repositories and media servers.

Pedagogic jobs: often focus on the direct benefit of technology to teaching, learning and assessment. These roles often include working with course teams to plan what technologies may be used, how they will be integrated, the support structures around integration, and at what points in the course lifecycle they will be introduced. As such, role holders may often be qualified teachers/lecturers, which helps their understanding of theories of learning and teaching, but they may also come from computing backgrounds (or a bit of both).
These roles may also include aspects of training other staff.

Development jobs: These roles are probably more popular in the US than in the UK (I think), and often focus on Instructional Design and Content Development. Therefore role holders will liaise with Subject Matter Experts (SMEs) on actual content, and then develop this content into interactive and engaging packages, using a range of tools/technologies. Again, knowledge of teaching and learning might be a pre-requisite in order to understand and integrate suitable opportunities for formative and summative assessment.
Flash has traditionally been a key tool for bespoke software development here, but in recent times 3rd party ‘Rapid Development’ plugins convert Powerpoint presentations into interactive Flash files. Take for example, Articulate Studio, Adobe Presenter or iSpring. Other tools integrate Screencasting (a method of recording the activities of a computer screen) into such Flash packages. There are a number of free tools here, but Camtasia Studio is one of the leaders. This area of the industry is reacting to the Flash Vs HTML 5 debate by developing/releasing versions to output HTML 5 packages (as well as or instead of Flash, and to varying success). Many of these tools offer free 30-day trials.

Job titles across these three categories are often blurred. Variations on the ‘Learning Technologist’ role are quite common, and there is a lot of discussion across the sector related to the actual role of the Learning Technologist.
Further to these three categories, there is another higher level role, considering the strategic deployment of learning technologies. Again, these could be separate roles based on a technical or pedagogical focus, or even cover both.
It's probably fair to suggest these would be typical of roles in the UK Education Sector. If we expand this further, we see roles related to the Learning Management System (LMS) as well as hardware (SMART and Promethan) and software (PebblePad ePortfolios) companies.


Useful Resources 



Creative Commons License
This work by Peter Reed is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.

Tuesday, 19 June 2012

Visualising Openness

I've been revisiting my work around the Open Content Movement lately (both in prep for a presentation at last week's #Solstice2012 conference and also for a paper I have had accepted for Research in Learning Technology). In turning back to some of the literature alongside results I received from questionnaires, one particular quote sticks out for me;
"Openness is not like a light switch that is either 'on' or 'off'. Rather, it is like a dimmer switch, with varying degrees of openness" (Hilton iii, Wiley, Stein & Johnson, 2010)
I really like this quote and something I referred to earlier in the year when questioning if the OER movement was mainstream and sustainable. I also refer to Schaffert & Geser (2008), who suggest openness has four principles: Open Access; Open Licensing; Open Software; Open Format.
So in considering the quote alongside the four principles, I wondered a) if it's possible to somehow visualise openness, and b) has anyone already made an attempt? I don't know for either, so thought I would give it a go...

My initial thoughts centre around a Radar Diagram, but it would involve plotting the 4 principles with various points for each. With this in mind, the following diagram attempts to visualise varying degrees of open practice 
(for want of a better phrase). The coloured area represents the degree of openness, where a larger area (based on plot on each axis) demonstrating greater openness;







If this could be a method of visualising openness, a detailed breakdown of each principle would be required. To this end (and by no means correct or complete), this could be a start;
Open Access (A) points (might include)
  • Closed VLE 
  • Internal (Institutionally Owned) Repository 
  • Public (Institutionally Owned) Repository 
  • (National Repository) Jorum/Merlot

Open Licensing (L)
points (might include)

  • All Rights Reserved
  • Creative Commons
    • CC-BY-NC-ND-SA 
    • ...
    • CC-BY
  • GNU Public license

Open Software (S) points (might include)
  • Flash
  • Dreamweaver
  • MS Office
  • Google Docs
  • Xerte/GLO Maker

Open Format (F) points (might include)
  • Flash Movie
  • Document (.doc, .ppt, etc)
  • PDF
  • HTML

(N.B each of the points range from lowest to highest, closed to open, etc)


So to take a specific case to plot as an example, we could consider the development of an interactive Flash movie file that has been licensed with Creative Commons (CC-BY-NC) and placed within Jorum. The resulting visualisation might look like this;


The diagram/graph shows this case is a bit weak on the format and software side of things, but they are doing well in relation to Open Access and Licensing.

Considerations

This is just a quick attempt at visualising openness - it's by no means complete and requires much more thought. Immediately I can think of the following points;

  • Automation of a radar chart based on form input could reduce individual interpretations towards the 4 principles (this would require more specific details within each though)
  • More knowledge/understanding needed (both of Openness and Technical), and perhaps crowdsourced, required to flesh out points within each of the principles
  • The points on each axis could relate to the specific 'criteria' (as above)
  • It might be worth highlighting that software and format are inextricably linked, however this is not to suggest a 'closed' software produces a 'closed' format; for example consider the expensive Adobe Dreamweaver which produces open HTML formats.... 

I would really appreciate your views on this. Is it stupid? Worthwhile? Does it already exist?

Please use the comments to share your thoughts.


Creative Commons License
This work by Peter Reed is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.