The mist is clearing!
After spending some days debating the pros and cons of various methods of creating the architecture for our template things have started to become a lot clearer. I had built an example purely using a file/folders structure but then created another version using learning modules to create each weekly entry.
I had been seduced by the learning module as this seemed the way WebCT had been designed to work. We were bending the model by linking to various file formats in the menu (lecture slides and handouts), but a key thing was that each weeks text (learning objectives etc) were held in a separate html which seemed to make much more sense than cramming this into a header under the files/folder model.
However, as the learning modules were created and tested the holes started to appear in this method. Navigation via Course Tools/Course Content menu was near impossible as the menu kept closing. The breadcrumb trail failed as it recorded every jump made rather than recording the structure of the hierachy.
But most of all was the realisation that each of the learning modules created as a weeks entry where also being collated under the Course Tools/Learning Modules button. This meant that any 'real' learning modules (eg. guide to academic writing, time management tutorial) where mixed with weeks 1 through to 24. Not good!
So (big breath), current thinking which takes on board many wise words for my various mentors, advisors and critics, leads me back to the original files/folders structure. This supports the delivery of accompanying files (lecture slides etc), allows for web links, provides editable space for the accompanying text (either in the header or as a linked html file) and allows for links to learning objects such as the time management tutorial.
I think this method works closer to the intended model on which WebCT has been built. Yes, we start with a document repository, but now the additional tools allow us to expand which may include new learning modules specific to our own units, online tests, discussion boards, online submissions or more practical elements such as group assignment or tutorial sign ups.
It's actually getting quite exciting now!
After spending some days debating the pros and cons of various methods of creating the architecture for our template things have started to become a lot clearer. I had built an example purely using a file/folders structure but then created another version using learning modules to create each weekly entry.
I had been seduced by the learning module as this seemed the way WebCT had been designed to work. We were bending the model by linking to various file formats in the menu (lecture slides and handouts), but a key thing was that each weeks text (learning objectives etc) were held in a separate html which seemed to make much more sense than cramming this into a header under the files/folder model.
However, as the learning modules were created and tested the holes started to appear in this method. Navigation via Course Tools/Course Content menu was near impossible as the menu kept closing. The breadcrumb trail failed as it recorded every jump made rather than recording the structure of the hierachy.
But most of all was the realisation that each of the learning modules created as a weeks entry where also being collated under the Course Tools/Learning Modules button. This meant that any 'real' learning modules (eg. guide to academic writing, time management tutorial) where mixed with weeks 1 through to 24. Not good!
So (big breath), current thinking which takes on board many wise words for my various mentors, advisors and critics, leads me back to the original files/folders structure. This supports the delivery of accompanying files (lecture slides etc), allows for web links, provides editable space for the accompanying text (either in the header or as a linked html file) and allows for links to learning objects such as the time management tutorial.
I think this method works closer to the intended model on which WebCT has been built. Yes, we start with a document repository, but now the additional tools allow us to expand which may include new learning modules specific to our own units, online tests, discussion boards, online submissions or more practical elements such as group assignment or tutorial sign ups.
It's actually getting quite exciting now!
posted by Richard E @ 4:41 pm
0 Comments:
Post a Comment
<< Home