Thursday, 25 March 2010

How to Moodle, Ray and Dave & Jobs!

A couple of weeks ago (March 9/10 and 15/16) we had some training, organised by a Moodle Partner called How to Moodle. We had 2 sessions, 1 the course creator workshop and 2, the administrator workshop.

The following is a list of jobs and things to investigate, that were identified throughout the workshops.


Blayn
•Change move arrows to a lighter colour against the block header colour.
•Can the gradiated background in the chat be removed and left as plain white or something. The dark text can’t be read against it.
•On the default theme, take out the topic outline text which appears at the top of the page.
•On default theme, figure out why, when uploading a file the choose option goes off the end of the page. It’s as though the table is set at a fixed size, larger than the size of the popup window. The same problem happens when using the quiz question matching question type. The answers appear to the far right of the screen.
•Change the link colour in the tab options on certain activities, because at the moment it is white on a white background making it invisible.
•Theme: look to change the theme once a user is in and make the top strip thinner. This is controlled in the php code. Logo and formal white both deal with this – so can be looked at as examples. http://docs.moodle.org/en/header_logo

Mark •Strip out the http:// from the add a file area. (setting in ADMIN)
•Add the role of auditor to the site and ensure that teachers can assign auditors to the roles.
•Remove Journal Activity as it is being stopped – do this for Maggie Holmes’s course.
•Make sure exercise is disabled
•Make sure workshop is disabled
•Do we need to archive in any way if we are having a lifecycle of 36 months for all courses?
o Is there a business requirement for extra storage space so that we can archive anything over 4 years old?
o What’s the university auditing requirements internally and externally (QAA)
•Site policy – need to set one up in moodle: Security > Site Policies – stick policy in the site files: Front page > Site files
•Show recent submissions in the Assignment module block. Should we disable this? It shows which users have submitted assignments in the Recent Activities block.

Jim
•Install the lightbox gallery – really nice photo gallery tool.
•Install quick comments block, quick way to ask questions via email - moodle.org
•Install the LRC block - allows tutors to add direct links to relevant journals etc
•Enabling open in new window for resources – option is set, but it doesn’t appear to take effect on document and web page files. See if there is a fix in Moodle Tracker.
•Feedback activity type (install)
•Questionnaire activity type (install)
•Install Comparative reports is an admin add on which allow you to look at more of the stats within moodle, such as most active users etc.
•Create a new language pack for Flexible Learning, so that we can set the assignment option for send for marking to something else.
•Manage updates on an ongoing basis. ‘composite’ version of moodle as each update is implemented.
•Use SVN to manage the version control – an open source product
•Need to figure out the upgrade strategy and how this will be managed
•Install a development server for testing and development purposes


•General Moodle Policies
Users never to be given course creator rights.
Teachers prevented from restoring courses from their own personal sites – this can be done, but must be requested through the e-Learning team.

•To consider
Should we disable email addresses being visible when users post forum messages?
Should we stop users from being able to see who has submitted an assignment in the latest news block?

1 comment:

  1. The development server is called Toodle and lives at http://toodle.yorksj.ac.uk. It is running 1.9.8+ and currently has lightbox, quick comments, learning resources block, feedback activity type, questionnaire activity type, a new version of turnitin and comparative reports installed.

    It contains the same users and permissions as the live moodle, so anyone can go in and try the new stuff out, although any changes made to courses will not make it across to the live moodle.

    I propose as a update/upgrade cycle:

    1. Toodle updated on Thursday with latest version of moodle, plugins and any new requested features (structure).
    2. Toodle tested.
    3. Moodle updated the next Thursday with the structural changes - course data, language changes etc not affected.
    4. Toodle is then updated with the data from Moodle so that it reflects course and settings changes since the last Thursday.
    5. Toodle and Moodle are now effectively the same and the cycle begins again with step 1 performed the same day.

    BTW

    Structure - which activities or blocks are available in courses, themes, security patches, standard language packs etc
    Data - course content, local language specification, events, reports, files, user profiles etc

    ReplyDelete