By Domi C Sinclair, on 16 December 2014
When you have a problem or question E-Learning Environments (ELE) are always more than happy to hear from you, and will do all we can to help you as quickly as we can. However, this process can be slowed down if we don’t have all the information we need to investigate your problem, or answer your question. So here are some top tips for what to include in an email/ ticket to ELE, so you can help us to help you.
1. Course name (and link)
UCL is a large university with hundreds of courses, and even more modules. Therefore it is very difficult for us to investigate a problem without knowing the name of a course/ module, so that we can look at the problem and try to replicate it. A lot of problem solving is reverse engineered, so we will try to replicate the problem for ourselves and then figure out what is wrong, by using our familiarity with the components of the technology. It is also helpful to include a link to the course/ module in question, as sometimes these are not obvious when searching in Moodle/ Lecturecast. Asking for the course name is always our first step, and so by including this in your original email then you will save time and help us resolve the problem faster.
2. Activity/ resource name (and link)
As well as there being a lot of courses at UCL, individual courses may have more than one of a particular activity, such as a Turnitin assignment or forum. It will take ELE extra time if we have to search through all of them to find the problem, and it also means that sometimes we are not always sure if we have found the problem. By including the name and location of the activity in the original email ELE can go straight to it, and get to work determining the problem.
When we look at a course, it might not always be possible for ELE to replicate a problem. This might be because the issue is related to a particular browser you are using, or due to permissions on your account. As these parameters might not apply to ELE we may not be able to see the problem, which makes it much harder for us to help with the answer. If you can take a screenshot (using the PrtScn key) and then paste that into a document and send it as an attachment, it will help us see the problem and any error messages you are receiving. It can even mean that we can answer the question or give a solution straight away upon seeing the screenshot.
4. Error messages
Screenshots of error messages are good, but if you can’t take one then including what an error message says will help ELE to diagnose and resolve the problem. It also helps us if we have to deal with any third party suppliers (such as Turnitin).
A summary of the problem is best as ELE might not have a lot of time to read a long email, and it may be possible to determine and resolve an issue with only a few key details, listed above. However it can also help to be specific. If you are reporting a problem then list what steps you are taking that are causing the problem, which buttons are you clicking and in what order? Details are also helpful if you are asking a question about a new activity you’d like to start, but you’re not sure which tool to use. If you include specific details about what you want to do then ELE can suggest the tool that fits your needs best.
By following these tips you will have an easier and quicker experience with ELE, and we will be able to get through more problems or questions in less time.
Please feel free to send your queries to ELE via our email address, email@example.com