If you are registered (on MyCampus) for a course, and that mechanism is used
for the moodle course, then you should see the course listed already for you
personally, and clicking on it gets you there. I.e. no enrol step required
(although until you have joined it once perhaps your name won't appear
If not, you can still find the course through the long lists of all courses;
and will probably be asked for a "key" (a simple password for everyone on that
particular moodle course) and after using it once, you'll be enrolled.
If staff have to manually enrol you on a course, then you must first login to
Moodle itself, so that you are known to moodle, and your name can be
found by staff searching for it, in order to enrol you.
Joining as a guest: if the course is set to allow guests in; then you should
be able to enrol without a key, once you are logged into Moodle.
BUT the course has to be set to "be available to students", even though
enrolment may be set to "No". French 2 20010-2011
In comparison, in the
AAW moodle site
to create a new exercise, Katie does:
- "Add a new task"
- and chooses one of only 4 formats:
- Free Text. (Feedback is either Katie's proposed solution; and/or
- Select category: they select (drag across) a bit out of a
paragraph; and then a menu appears to select what type of error it is.
- Word click. Pick a word out of a paragraph; then freetext type
in of the corrected word.
Naming moodle courses
Moodle 1: obsolete
Notes on creating wikis/forums for my courses
Use "OU wiki" not "Wiki" (on menu "Add an activity").
A] What I want in my classes is to divide the class into groups; and for each
group to have its own forum that others can't read; and a wiki which others
can read but not edit.
- Go to "groups" in main page side menu. And the "groups" tab on that page.
- Repeat for all student groups you want:
- Create group
- give it a name
- add/remove users to insert students.
- Go to "groupings" tab.
- Repeat for each student group you want
(for me, this is one grouping for each group):
- Create grouping
- Give it a name
- Add/remove users just by inserting the corresponding group.
- Create a forum for each group on top page.
- To create a space on the top page between each group: insert a label with
an H6 heading but no text.
- Repeat for each of these forums:
- Go into the / each forum.
- Press "Update this forum".
- Name it.
- Type: — "Standard forum for general use".
( NOT "A single simple discussion" which has a bug in preventing
posting by students.)
- And you must add a description of it.
- Force everyone to be subscribed? — Yes, initially
- Read tracking on this forum? — On
- (Press "Show advanced", if necessary.)
- Group mode: Separate groups
- Grouping: Select the grouping/group for this forum.
- Available for group members only: — TICK
- Visible: — Show
[if Hide, students can't even see their own forums.
With Show but the other settings, they only see their own
forum on top moodle page.]
- Note that in Moodle jargon: "subscribed" means only that you
will get an email copy of forum postings: not that you are entitled to
post, or to access the forum.
Being "available" is what makes you able to post to it;
see the link to it, etc.
- Create one (and ONLY one) overall wiki on top page.
Use "OU wiki" not "Wiki" (on menu "Add an activity").
And it just instantly creates N sub-wikis, one per group.
- Go into the wiki.
- Press "Update this wiki".
- Name it. (Add description of it.)
- Press "Show advanced", if necessary.
- Wiki auto-linking options Disable CamelCase linking [tick]
- Sub-wikis: One wiki per group
- Group mode: Visible groups
- Grouping: None
- Now (to make the group wikis more visible to students), create a link
from top page to each (sub-)wiki.
- Go to top page; turn editing on.
- Click on (go into) top level wiki
- Using wiki for: — group 1: — change
- Use "Other wikis: Choose .." menu to go to the first group wiki.
- Copy the URL of this page, with a group=ddd
- Go back to top page
- Add a resource → Link to a file or website → paste in URL
→ Name the link e.g. "3) Volunteering"
- Repeat for every group.
- Go back over them and fix the group part of URLs
B] To let other students edit each others' group wikis: no obvious way to do
that. But the suggestion is to use the 'Locally Assigned Roles' feature in Wiki,
to make all the students 'Staff' inside the wiki.
- Do NOT go to Administration: Assign roles. That is where you would
naturally go, but don't. That would assign students a staff role in the whole
course, not just in the wiki.
- Go into a student wiki page
- Press "Update this wiki"
- Press the tab "Locally assigned roles"
- N.B. "Locally assigned roles" is also a tab, but with a quite different
meaning, elsewhere: in "Admin: Assign roles"
- Press "staff" in the list of roles
- Hopefully, you will see the list of potential users including students on
the course, and can select them to "Add"
- I don't know if you have to repeat this in each wiki or if once does it.
C] To freeze a wiki page i.e. prevent any more student edits of it (e.g. after a
classwork deadline has passed), yet leave it readable by (all) students:
New technique (new wiki style "OUwikis")
- Go into any part of the combined wiki;
- Press "Update this OU wiki"
- Change the "Prevent editing from" line:
- untick "Disable";
- Set the date to the day after the deadline (will act at midnight of
Old technique (old wiki module)
One technique is to set its Read page flags:
- Go into any student wiki page
- Use the dropdown menu "Administration" and select "Set page flags"
This shows the flags for all the pages (and students) in that wiki.
- Tick ("check") the checkbox "RO" (for "read only").
- This mechanism lets you control access to each wiki page separately.
(Unlike other mechanisms which seem to apply to the whole wiki or all wikis in
D] Eric Yao has the problem of wanting to give wiki pages to a subset of students
on that wiki course; let them see each other pages; but to lock out other
students who don't have any wiki page.
E] I want to have it so that students must submit an assignment and then but only
then can see all the other students' submissions. There is an obscure way to
do it with "workshops" (the RPC mech.). See above.
Issues for staff setting up moodle courses
It talks of permissions, but nowhere for staff to change them.
No way for students to upload files/images, at least in the wiki: just paste
in a URL pointing to one stored elsewhere.
"Students can upload documents in the assignment, database and the forum
activity, as long as you (as tutor) have set the activities to allow for this."
Notes on enroling students on a moodle course
If for a moodle course, the "course ID number" in "edit course settings" (which
you get to by "Admin"-"settings") is the course code, then students are
automatically enrolled. What actually happens is that when (but only when) the
student logs into that moodle, then the connection is made between that
student and their registered courses, and the latter appear in the personal
"my courses" list for that student. So it is completely smooth and effortless
for the student. And if they are deleted from the course, they will be
silently re-enrolled again when/if they login again to that moodle.
For the staff member the only drawback is that they don't appear in menus as
members of the course until they've logged in the first time.
If that isn't working, or the student isn't yet enrolled in MyCampus for the
course, then when and only when they login to the moodle, then staff can add
them to the course (Admin:: Assign roles:: Student role:: Add:: search).
To get round the "when and only when" you can get LTC moodle staff to add a
(short) list of students to a specified moodle; so you can get on with your
admin task of enroling them.
How to enrol someone apart from that. Searching for their matric; or staff
name. What if staff not on that moodle.
Warning about deleting a student from ?groups; !roles.
Notes on read/write permissions
I'm used to Unix view of file permisions, where an object (a file) you set
separately: read, write, (and execute) permissions, for each of: the owner, a
The "Set page flags" inside a wiki work quite like that AND affect each wiki
In a wiki setup,
- groupmode = 'visible groups' means everyone can read, only the designated
group (and staff) can write.
- groupmode = 'separate groups' means only the designated group (and staff)
can read or write.
- groupmode = 'no groups' means everyone can read and write. ??
HOWEVER: if there are separate wikis, then "visible groups" means other
students on the course can NOT read (or write) the wikis.
In forums ....
Notes on undos
Students in wikis; revert
Staff and enrol/groups
Notes on guest access
Set the course to let guests in without a key.
"Course settings:: Guest access: Allow guests in without the key".
BUT also: "Availability: This course is available to students".
Moodle1: Course enrollable: No. and Disable the dates
Moodle2: Enrollment method by self-enrol set to not allow.?
Below are recipes about my special uses of groups and how to set them up from
scratch; and saving old moodle versions.
I think typical resets clean out whole moodles.
To recycle a moodle, saving most content, then can get rid of last year's
enrolled students by:
Admin block -- Reset -- Roles (open tab/block) -- Select "student" only --
Reset course btn at foot of page.
This disenrols all students; and if the block enrols are in place, then
they will restore current students over night.
Stopping moodle forum emails
Notes on podcasts in moodle2
See also http://www.psy.gla.ac.uk/~steve/ipod/#sec5
Moodle2 keeps trying to impose the moodle player, which doesn't allow skipping
forward or back, nor downloading.
To get round this:
- Add the recording by "Add a resource" -- "file";
- (Still inside the upload screen):
click tab/section "Appearance" -- select "In pop-up" not "automatic".
- Can convert Phil's podcast uploads by:
- Turn editing on, start editing the resource on the page
(Edit -- Edit settings)
- Appearance -- Display -- In pop-up
- Can convert re-use an existing uploaded file by:
- "Add a resource -- file"
- Name it
- Click tab/section "Appearance" -- select "In pop-up" not "automatic".
- In "select files" -- click icon for "Add"
- Click "Server files" rather than "Upload a file"
and browse to find existing uploads;
and click on the one you want.
- Click "make an alias" rather than "make a copy"
- External links to this resource, if they are to launch without further
user clicks, need to be the hidden underlying Moodle file URL.
Notes on file updating: And adding an audio recording in Moodle
Intro: Things like audio recordings, PDFs etc. are files that can be stored in Moodle.
Unlike in Moodle1, these can be overwritten with new versions and links still
work provided the same filename is used.
Creating a file "resource" on the Moodle page, for end-users:
To add a file, whether podcast (audio recording) or word doc, whatever, you:
Add a resource -- file:
- Name field ["name1" e.g. 'Test resource file']:
This is displayed to the end-user on the moodle page.
- (Description field: may also be displayed)
- Filename of the file you upload ["name2" e.g. 'test.doc']....
- (If file is audio, then set:
Appearance -- Display -- (not 'Automatic' but) 'In pop-up')
- Content: drag and drop new file e.g. 'test.doc'
- This name may get changed (see below) ["name3"] e.g. 'test (1).doc'
The file now stored in Moodle is always available via a direct URL, even when
it is not the selected one of several for that "file resource" and within a
"topic" that is all hidden (from students), (but that file resource itself
cannot be hidden). So you can create one file resource; store lots of files in
it; hide all direct Moodle access to them, and still refer to them from
The URL is of this form:
The last bit is 'name1' i.e. original filename; and the rest is the same for
all files in that resource. The "/1/" may be the version number of that file
name1 in that resource.
Overwriting, re-naming, switching versions:
You can drop multiple files into that area, either at once or later.
You can set which the end-user gets by clicking on the file's icon and
then clicking "set main file".
If you re-upload a file of the same name (same name2), then it will ask
whether you want to overwrite the existing one, or rename the new one.
Thus you can update installed files by going to the on-page resource that uses
it; Edit -- Edit settings -- Content (the drag and drop area) -- and
re-up-load a new version with the same name; or indeed with a new name, but
setting it to be the "main file".
Re-using pre-uploaded files from another "resource":
In the Content (drag and drop area):
- Under the label "select files" just above drag and drop box,
click left hand mini icon ("Add ...").
- Click "Server files"
- You get a list of "name1" resources displayed as folders. (If you have
two resources on the page with the same name, then you will see both of these.)
- Clicking on one, it displays the set of one or more name3 files stored
under that resource.
- Clicking on one, it asks if you want a copy or an alias (pointer) to it;
and whether to select it.
Notes on guest access
Under "Admin, users, enrolment methods"; add method "Guest access";
turn it on (click on eye-icon).
It is unclear how I can find out what guests can do (controlled by system
How to give them read-only access.
But it seems that it is set so that when I enable guest access, anyone
can get directly in without course login (as opposed to Moodle general login).
Restricting access to a moodle page
Access to a whole moodle course is done by enrollment, done by course codes.
But individual items / activities / resources and also "topics" (page
sections) have, on their "Edit settings" admin page,
a tab about "restrict access". This allows you to restrict a section by
group or grouping; or date, or anything in their profile.
So the page (single moodle) for all PGT/honours options is accessible by all
PGT, all Hons L3, and L4; but they have set up on that page groups for each
course codes, and each item/section/topic has a restrict access specified by
Notes on Moodle 2 and my course
- (Put in course code in main settings: picked up later in enrolments.)
- For a plain front page: choose weekly format,
then say number of sections = 0.
- OR use new-ish collapsible sections, for organising big course pages but
giving an overview and making it easier for students to find what they want.
RHS Admin - Edit settings - Course format - Collapsed topics. [opens params]
Params: (leave all to defaults except:)
Nmb of sections e.g. 3 or 6.
Toggle bg: ccffcc
Toggle bg hover: 88ff88
At least for the section for slides and recordings, creater a folder in the
section (called e.g. "Lectures 2016: slides & recordings").
Set folder's "display folder contents" to "Inline on a course page"
- So students can see their group members.
Course settings; visible groups.
Then under "participants" students should be able to select a group and
see who is in it.
- To see which students are in NO group, have to:
(Admin) Users:: Enrolled users:: Enrollment methods -- All::
scroll down looking to see if they are in any group.
- Create groups. Manually;
OR read in csv file, one col., with group names; col header "groupname"
0-19 (too much hassle to give longer names)
- Wikis: create one top level wiki.
- "First page name": Give an empty / space / small-font name
for the wiki: you can never edit this, once created.
- Group mode = Visible groups
- Grouping = none
- Default format = HTML
- Wiki links: create a list of links straight into each group wiki page.
- Put the list as text inside the description of the wiki.
- Tick box for showing the description.
- It works; and it shows the list of links both on the top page
where the wiki is AND on each top page inside the wiki (a better
alternative for the dropdown menu of groups there)
- Forums: [for all types] Create one top level forum.
- Grouping = none
- Subscription mode = auto [all at first get email, but can opt out]
- News forum: To get rid of the news forum:
settings (Administration -> Course settings), set News items to show: 0.
- Social forum (whole class):
- Forum type = "Standard forum displayed in a blog-like format"
- Group mode = No groups
- Separate private groups forum:
- Forum type = "Standard forum displayed in a blog-like format"
- Group mode = Separate groups
- Tick "Available for group members only"
- Forum for collected critiques of other student groups' wikis:
- Forum type = "Standard forum for general use"
(the top level lists threads)
- Group mode = No groups
- Me start a thread for each and every group (create in reverse order).
- Enrollment: could use a key; and have the key assign them to a group
- A pain with the moodle2 wiki block is that they insist you name the top
page; then you can never change the name AND it is shown not only on the window
title but as a big (< H2>) header at the top of the page.
This undermines the whole idea of having the wiki do different things with
In principle, it should be possible to suppress it by redefining
CSS class "wiki_headingtitle".
- What I would actually like, to make the use of wikis in courses for
different groups but as a class resource go well, is:
A single student-editable place where they edit the name of the topic which
there group eventually does. This one place should automatically change all
- The first major heading on the group's top web page
- The window TITLE the group's top web page
- The group name: editing the title into part of the group's name, so
dropdown menus inside the wiki show it.
- The link text for links from the top course page into each group's wiki.
This is almost inherently needed for the concept of wiki with "visible groups":
because each group's product should be visible to all others; so you need an
index/ TOC of this.
Perhaps using the TOC which is automatically generated would do this,
if it were extended one level up instead of only separately for each
- Subscription (whether a person gets an email copy of a forum post) seems
only to be modifiable when in the page for writing a new post; AND doesn't
seem to be a setting you can inspect anywhere.
Creating groups and wikis in my courses
A] This is a note on my method for the Moodle part of group creation.
Can use jigsaw SS for this.
Or at least for small group size, do it in a simpler SS with rand nmb; and
categories of students.
Freeze in resulting group nmb.
In first class, shuffle the groups so that all who attend get to be in a group
with other attenders. Then afterwards reassign others as necessary.
B] This is a note on my method for the (Moodle) enrollment of students into
C] This is a note on my method for the Moodle part of group creation.
- Given an SS with student assignments to groups (partly auto done; partly
hand-adjusted), print this out to use.
- Manually enrol students into groups using
Admin -- Users -- Groups: select a group, see the members; and can add/delete
- Tedious: select a group but then must search students for each name
individually before can add it. I.e. in class of 100, 100 searches plus btn
presses to enrol.
- I have a spreadsheet (SS) with one nmb col. from 1-37 for the groups/topics;
and a col. with the title of the topic.
- In creating the groups, Moodle will take a 1-col SS list of group names;
which I generated from my SS. (Import groups cmd.)
- Best to put in this char as a non-break space into the group name as first
char in 1-digit group nmbs.:-
This is because the menus list groups in alpha order, so if group
titles start with their nmb., must be something to pad 1-digit ones.
- Same SS generates HTML for the first heading on each group's page (with
the topic title).
- Same SS generates HTML for index list for jumping straight from course
top page into each group's wiki page.
- I generate a sample text with text; Link; IMG; a 2nd section heading.
- In index, I use not pageID but groupID which runs sequentially because of
my import-groups. So doesn't matter which order I create each group's page.
wid= is one id for whole wiki block; title can be empty string but must be
given; group= is an id for the group.
- Then repetitive passes through the groups:
- Create group's wiki page
- Paste in std. page contents body (as text not html).
- Paste in HTML of heading at top for each group
- Paste in whole block of index links to something on the top page.
This is only one operation.
- ** Admin -- Users -- Enrolled users: Group -- All participants:
Can scroll through the long list and see which groups each is in; and can
add them into others right there. Particularly good for spotting double
enrols, and no group.
- Admin -- Users -- Groups: select a group, see the members; and can
- Navigation -- ... participants: Visible groups: :
You get a list of the students in that group, with full details. (Also
clicking on a student there, you see which group(s) she is in.)
Students can use this one too.
Enrollment. Moodle 2
Some extra notes on controlling enrollment.
See the Moodle help on this.