ce6.1 migration checklist (for sites migrated from ce4.1)
I have made a checklist for our team to use when checking webct ce 4.1 sites migrated to ce6.1:
http://www.usyd.edu.au/webct/form/ce6upgrade/ce6-migration-checklist.html
It ain't perfect, but it highlights the issues we suspect we're going to find in many of the sites we need to migrate.
More things to mention in (or investigate before) the ce4->6 FD session.
We've got a lot of info sessions planned for our designers as part of the move from WebCT CE 4.1 to WebCT CE 6.1. The first session will be for our faculty designers and heavy users; those who look after a large number of courses and/or other designers (say 10-50 sites rather than the more usual 1-5).
Part of preparing for this session is having a look at what other institutions who've made the same switch have written in the doco they've made available online. I'm making notes of things to follow up & check out myself, and of things to mention.
WebCT Wishlist: selective release in all areas
In WebCT ce 4, "content module" (henceforth CM) pages are often used to present lecture materials. This means the files are presented as a simple hierarchicial list.
Another one for my webct wishlist: better site notification / visibility for students.
One of our most common student enquiries at this time of year (start of semester) is "Where are my sites?". Students often expect that there will be a site in WebCT for each of the units of study they're enrolled in. This isn't currently the case.
I need a CSS stylesheet for lesson plans.
As I go through my various work-tasks, I use a number of standard styles. Some I use across tasks, but over time I've broken up my standard styles into a number of separate style sheets. It started off being just about look and feel, but over time ash evolved to manage several functionally different document types.
