14. School
PGT UG PGR
Yr1 Yr2 Yr3
Staff
Institution roles e.g.
“People Pyramid” by Nathan Rupert on Flickr
https://www.flickr.com/photos/nathaninsandiego/
17. Common Activities
A) Posting Lectures / Hand-outs
B) Receiving notifications
C) Organise Course/Module
D) Using Reading Lists
E) Posting Formative/Summative Assessment
Information
F) Communicating with Students
18. Knowledge
1) Structure Tips
2) Understanding Copyright in e.formats
3) Understanding accessibility in e.formats
4) Useable file formats and types
5) 3rd Party storage
6) Working Across Modules
7) Library / ereserves
8) Academic Regulations e.formats
19.
20. Difference between –
Drawing out and Drawing In
The ‘tool’ based support structure methodology
draws out (makes people try to find information
for themselves)
and what we want to do is draw in.
21. Progression and discovery
Often categorised by importance
placed on by students,
sometimes institutionally driven)
(My students want this……...
why should I want this?)
Processes or tasks driving
adoption of particular mechanism
(Now, I know I want to do this….
How can I go about it?)
Underpinning knowledge,
what’s needed to do it
correctly/sustainably
(What do I need to know to
support students properly?)
I’m Peter Rayment the Learning Technology Manager at Cardiff University. I manage the Learning Technology Team who support Central Learning Technologies across the university.
We work in close association with three Enhanced Learning Technology Officers who are located within the University Registry & Academic Services Department, who were employed to work to engage at College level in the university. Cardiff has three Colleges made up of 26 Schools. Diverse support levels within some schools having no Learning Technologists in place and others have teams with more staff than are available centrally. In this presentation I’ll talk about centrally managed support in a partially devolved College University structure.
Magic Button – Requested by a member of Academic Staff many years ago which provided him with the correct help materials for where he was in Blackboard – Eesysoft is that solution.
The Way Forward states “We will educate our students to the very highest standards and support them through the transition to independent learning.”
In December 2013 Consultants working for the university undertook analysis of the current situation relating to Student Experience at Cardiff, undertaking seminars and face to face sessions with a number of stakeholders. From this work the arose Student Lifecycle & Educational Technology Programme Planning - Analysis & Findings Report. Following this, the WF report detailed a high level action plan.
One outcome was a commitment from the University of £16 Million over four years to improve student experience. A number of projects have been started, including Lecture Capture, Admissions, Module Evaluation, etc.
But, we know that all of these have to be underpinned by a robust support mechanism.
When we set up the system originally we mapped our content to tools, as this seemed a sensible approach at the time and has worked well for us to this point. The structure therefore looked like this.
Close up of Content mapping for support
Over the past couple of years we have been using Eesysoft Messaging (Context sensitive help) and EesyAnalytics to help with central support. The messaging system has been used to provide context sensitive help for Cardiff Specific content.
Here you can see the blue support tab on the right showing (5) – this is the number of relevant support items in the system for the displayed page in Blackboard.
When the user accesses the Support Tab Area they will automatically see support related to the area of the VLE they are in. (the number (5) shown on the previous slide.
This data has been populated by us at Cardiff.
We have the ability to proactively display messages proactively highlighting
Known issues
New areas of functionality
These can be triggered by a number of different events (Scan of page for a piece of content, Mouseover of content, Click on Button or link).
And we also put in place Analytics software to gain an understanding of our users use of the system, and the impact of our engagement activities, something we have not yet realised to its full potential. More detail on this later.
We put in place monitors on a number of areas of functionality within the system. Examples of some are in this slide.
Example of one monitor point that we placed on the jump off to Turnitin
This slide shows percentage of users from each reported role that have accessed the Jump of point that has been monitored.
Both Perspectives, slide to prompt covering the changes and improvements that have taken place over the time we have had Eesysoft in place and their impact.
Eesysoft – Improved Analytics – Blackboard Support Populated – Service Packs populated. Reports prebuilt in Analytics and Dashboard to display.
Cardiff – Tactical Initiatives – Induction / Refresh Modules – Change in Way of supporting Learning Technology systems
Addition of all Blackboard support materials into system
This slide shows the Cardiff specific content being prioritised above Blackboard Generic Content when searching on “Assessment”
Changes in analytics with standard monitoring points.
Filters, ability to download CSV of those engaging/not engaging – Granularity.
Note drop off in use between Christmas and New Year is due to this being a copy of our dataset on a Development Box not because our system went down
This shows part of the new reporting Analytics aspect of the software – dashboards showing standard monitor points.
This has saved us a lot of time and provides a useful way to quickly see what the situation in within the system.
We can customise this (as cliet) to add in our own reports.
Can use the + to drill down in more detail in each area.
New interface has ability to toggle between % and actual users, and also between roles of user.
We make extensive use of institution roles in blackboard which we take from our identity management system. We currently have 720 institution roles which map to a number of things such as school, user role such as staff, UG Student, UG Architecture student in year 1. etc etc
We are now rethinking completely how we undertake support
In light of the recent work that we have been doing to improve use of the system (Learning Technologies) we are now reviewing this strategy and methodology. The ‘tool’ based support structure methodology draws out (makes people try to find for themselves) and what we want to do is draw in.
No longer Map to functionality but trying to map to tasks.
As part of the previously mentioned Portfolio of work we are currently undertaking a number of “tactical initiatives” In particular we are trying to improve usage of our centrally supported learning technologies. We have built online Induction Courses for both staff and Students as part of this, and currently an area we are working on is improvements in the use of learning technologies in support of assessment and feedback.
So now we’re rethinking how we do this in the context of Student Experience improvement. By ‘Drawing in’ we mean we want to build support into the fabric of Blackboard. It means thinking about the process or task, not from the tool first. It’s pushing out (timely) support to students/staff, instead of trying to pull them in. The focus will therefore be less on the ‘search’ mechanism where people have to look and interpret for themselves, but on continual ‘pushed out’ support… being there when they need it.
This is a whiteboard showing work in progress on new mapping to tasks.
Shows Baseline tasks against required knowledge.
Common Baseline Activites
Knowledge required to undertake the activities
Again the whiteboard
Light Blue numbers against each Task shows the associated knowledge required to undertake the task. So A) Posting Lectures/Handouts requires Knowledge from 2,3,4,5
Draw out and Draw in
Draw in should be better, it is more focused and time related.
To do this we need to move towards the notion of How? What? When?
What this will look like:
- firstly, answering the real questions they have, for example, around assessment, questions like - why should I do assessment online? how do I go about choosing the appropriate assessment tool?, how do University regulations affect the way I set my assignments up? etc..
- secondly, linking together the thinking process, why do I need to know this, what underpinning info do I need to have etc?
- thirdly, linking up with all aspects of improvement work, e.g. digital literacy plans, PgCUTL, basic IT training events, as well as learn tech events.
So the plan is to use Eesysoft as the “Glue” to bring together Proactive online support and face to face sessions.
We now have the ability to proactively alert users to new functionality and (in their case) unused functionality. To present to them reasons why they should be undertaking particular tasks, advising on the options available and then explaining how to undertake their chosen task at a functionality level.
We can target resources at “filtered” groups who have or have not used functionality, or who have or have not attended a face to face session (for example).
We can then utilise the analytics to reflect upon the impact of our “campaigns” and modify them as appropriate depending upon the impact we have observed of their effectiveness.
We’re at planning stages – and there’s more work we’ll do after year 1.
Also,
We will be planning an evaluation of this strategy –
- how will we go about recognising the impact of this new approach?
Please Contact Peter Rayment for more details regarding Cardiff Universities use of Eesysoft.
Please Contact Michel Visser for detailed information on the software, demonstrations of the system, and discussions regarding price etc.