Permaview vs tags

Permaview is really wonderful as I can decide what tiddlers to open and create a URL that opens them.

However - I think that tag might be more appropriate: tag:CIPeL added to the address will open TW with all the tiddlers tagged CIPeL.

Unhowever - I have created a link for admin and this has two tiddlers that I don't want to re-tag.

Swings and roundabouts.

Editing and showcasing

My original plan was not to edit any of the examples at all.

However (there's always got to be a "however!") - there were inconsistencies, some of the file names were long or didn't reflect the content and some things did not reflect the re-usability aspect, containing module codes for example. Some were very much "work in progress", and as a result had a very long last page.

So I edited them according to the page in the wiki: http://cipel.pbwiki.com/EditingExamples


While doing that, I identified pages for showcasing the individual examples and took a screen dump of them.

Finding what to showcase

Every single example has something that can be showcased!

Every type of question has been used, despite my only talking about multi response and (in later sessions) gapfill.

Despite my only demonstrating cgPageTitle and mentioning cgComment when demonstrating the template, 12 styles have been used!

Some used the Flash Card that I demonstrated and many used internet links - no different from the normal use in Word.

Some included an index page, others removed it.

There were also some images and tables.

So I set up Tables to analyse what had been used. This was very useful because I could get at a glance what was there.

Then I needed to consider individual examples, so I assigned one page per example.

Debate - displaying all of the pages

Do ALL of the resulting pages need to be displayed? I think not because

1. It diverts attention from the purpose of the examples, which is to highlight how Course Genie can be used to create interactive web pages.

2. We need to get the reader to focus on the style of the examples, not the content, although the content will be one of the hooks.

It may be appropriate to remove long pages but keep the cgPageTitle and cgSectionTitle, to maintain the structure of the pages.

Another debate - could a TW be used for the comments (both theirs and mine?)

Pros -

Showcases TW

A good method of indexing text

Cons -

Not so accessible! Would need a text-only alternative for searching.

Style vs Content

I have an idea what I would like my e-learning object to look like when it's finished. It's very tempting to think about the appearance of it, especially when trying to explain to the Learning Technologist how I want things arranged.

I have just got involved with the TW again and am sure that this is the best way to put in the written information. It gives tutors an opportunity to search for items needed. And to engage with new e-applications!

Back to the content!

One decision - cut out superfluous text in the examples, so that people can concentrate on the items displayed. The superfluous text arises in the "work in progress" where pages have not yet been formatted, so the last page can be very long. (I suggested that people start from the beginning, considering one page at a time, and continually regenerate the files.)

"Critical Friend"

It was extremely useful to have a colleague act as "critical friend". Basic attempts to explain what I was doing helped me!

Useful things:
Categorise the objects, highlighting various aspects of them.

Looking through the examples

Not too difficult to look at the structure and categorise what types of questions and formats have been used.

The formats were by guessing and remembering the requests of colleagues from the sessions. I may need to go back to the original Word documents to check.

I will also need to anonymise the documents where people have put in their own names. But I have put that on my list.