Conversion to native Sakai code underway…

With Summer here, you would think we’d be taking it easy, but we’re hard at work converting our prototype application to native Sakai code. Once things are in reasonable enough shape, we’ll move the code to Sakai Contrib.

Questions asked

Last week’s presentation to faculty was very successful. Approximately 30 people attended, which is marvelous for the end of the semester, and they seemed very engaged and asked a lot of questions. I had a mole in the audience to make sure we noted down all of those questions (I was too busy trying to answer them to take notes).

I’ll start with the outline I posted at the beginning. As you can see, most of this ground has already been covered in the blog.

DESCRIPTION – What is the CLEo timeline tool and how does it work ?
APPLICATION – Using the timeline in & out of the classroom
ASSESSMENT – Concept maps of student timeline posts
OPINION – Survey of student attitudes

Here are the questions asked by the faculty, and a brief sketch of some answers

Did students work in groups? Short answer: no.

Why is some stuff off “the wall” (above main timeline)
The physical timeline corresponded to when the books were written; the students, however, kept posting about the time period when the books supposedly took place. I blogged about this in “When are we?”

Did you grade the concept maps? What is the relationship between the concept maps/posts and the assignments? I didn’t grade the concept maps, except as a “done/not done” grade. My most immediate plan now is to use them when designing research trajectories for the hands-on research methods session with the library in the fall. So they are going to have a significant impact on assignment design for me. In terms of student assessment, I think that they have a lot of potential as self-assessment tools, a way of getting students to reflect upon a learning process of which they may otherwise be unconscious.

Do you limit the number of words they can have in a post? Were they forced to discriminate the content, aka choose the valuable nugget of information? No, I didn’t limit. I did tell them informally that I didn’t think the timeline was an effective way of displaying large amounts of information, and then I think that their own experience demonstrated that to be true. So I think they were forced to discriminate the content, systematically and even extensively, but that this was almost a “natural” consequence of the format. In the cinema course, most posts averaged between 100 and 150 words. In the 19th-century literature course, posts were either less than 50 words (for little things encountered while researching the main post) or 200-250 words, most falling into the latter category.

In your survey, were your grumpy people always grumpy in their answers (and in class)? Mostly, yes. The person who preferred traditional lecture and didn’t want to listen to what a bunch of “dumb kids think” – well, that person wasn’t meant to be happy in my class even before the timeline assignment. ;-) I also strongly suspect that the three people who indicated that they spent less than 30 mins per timeline assignment got out of it (and out of the course) about what they put into it. This being said, the grumpy person(s) were very much a minority.

How did the students claim dibs on what items they would put in the timeline? How long do you think they took to make their posts? I told people not to double post – that if someone else got there first, you needed to post about something else. But since list view and the colored “what’s new” functions were added over the course of the semester, I didn’t really hold that line very hard. In any case, it was only very rarely crossed, and by accident. As for time to write a post, I told them initially that I expected them to spend about 45 minutes on a post, based on my own experience with how long it took to find things, and when I would hit information saturation. The majority followed that guideline.

Did you worry about plagiarism? Yes and no. We made the “source” field mandatory, although I only rarely checked on the sources listed. It was surprisingly easy to identify cut and paste, simply because the timeline post format was so dense compared to most of the sites they would consult. I think that in the next round I will be able to instigate a library resource requirement, a certain number of posts that must include paper sources, which will encourage responsible citing.

What happens in areas that are “dense”, full of events? Can you zoom in/out of the timeline? The SIMILE timeline allows you to hardwire in a “zoom” for a specific period, but we are still pretty far from making that available on demand. We’ve got it back on the list of development priorities under consideration.

Can you export stuff and re-import it in to other timelines? Not yet, but we’ll be adding that feature in the fall semester (2008).

(This question from a person who had observed a timeline class session) How do you think about the cost balance of doing this? Amount of time it takes relative to the pedagogical gain? What was useful to me in watching you do this is how you used this tool. I had originally been worried about this stuff just being interesting details for a generation that likes sound bytes. What I liked about what you did is how you kept bringing this back to the text. I felt very strongly that the payoff was worth the class time. I would say that if you aren’t willing to spend at least some class time with the assignment you probably won’t see a dramatic impact compared to other kinds of information presentation or organization. I do realize, however, that the structure of the assignment as I have planned it would really have to change with larger classes. One possibility we are looking at is making it possible to have multiple timelines within the same course. Then timelines could be created by teams, or could be used to present lab results, a chemical reaction… We are really looking forward to more diversity in the faculty test group, so that we can discover and address the needs of courses that deal with time on a less human scale.

Could this tool be adapted to organize things topically or a different category than time? For example in a novel, you organize things by character? I think that concept mapping programs might do this more successfully than our timeline. We’ve come up with a couple of examples of things that exist IN time, but not at a specific date – narrative time, for example, where an hour can take three pages, and a jump of ten years three words. Or “chemistry time” – a reaction that follows a specific timeline but does not necessarily exist, say, in 1998. These examples still respect a certain linear logic, however, that distinguishes them from category by type.

Minor release for duration events and timestamps

We’ve changed the code so that duration events (those with both a start and an end date) should only show as a discrete dot for the start date on the timeline instead of a bar that spans the distance between the start and end dates. The start and end dates are still reflected in the pop-up window.

The Modified and Created dates for events now include the time in addition to the date.

Highlighting entries (a.k.a. “What’s new”)

This is a great example of the shifting priorities of software design based on real-world testing experience.

We initially thought a “list view” would be the best way to view “what’s new” in the site. We found quickly, however, that without the temporal placement relative to other events, the entries were lacking critical context.

But it’s time for the coder to stop pretending to know what he’s talking about from a pedagogy standpoint. :)

I give you, What’s New version 2.0.0.0.0.1! <- Note the room for iterative revisions

What’s new

The default is what has been created in the past 7 days, but this can quickly be modified to use for search filtering. The idea is to leave the non-matching entries there when filtering to provide context rather than showing a limited set of entries, but we may find a need for the latter case where we only want to view a limited set.

Weekend update (no, not the SNL news)

This update is all about making life easier on the testers. There are enough bugs to worry about without having to follow strict input guidelines to avoid making the system go boom.

The summary list of what’s new:

  • The form is reorganized a bit, hopefully for the better
  • Required fields have more prominent labels
  • Fields with temperamental formatting, like dates, now have formatting examples
  • Form validation. No, not telling the form it’s clever or handsome, but rather telling you that you’ve left a required field blank before it will let you post. Or that you didn’t enter a valid date. And so on.
  • Trying to upload something other than a JPG file for the image no longer causes the system to go into fits. It also doesn’t create pesky “phantom” entries that are both there and not, and impossible to delete without rolling up one’s sleeves and getting into the database.

And now… screenshots!

Improved(?) form

Before the update, the edit screen looked like this:

Edit form before

Editors note: One of our testers is chronicling the rise and fall (and possible rise again) of Britney Spears.

Not very inspiring, is it?

Now, behold the new edit form:

New edit form

Isn’t that much better? All the required fields are more prominent, fields are laid out a little more cleanly, and we now have text hints for filling out certain fields.

But it gets better:

New form warnings

Form validation! No longer will leaving out the require Begin Date field simply post and then crash. You now must provide not just a value, but a valid date for this field. (P.S. I’m not sure whose crazy idea it was to try Jan 0, 2001, but we don’t have a validation check for non-existent dates yet. Soon to come) We can also see that the instructor-required Source field was not filled out when this was originally entered. Granted, it should have never been able to get through in the first place (programmer error), but this person must now provide a source if they want to ever edit this entry. I suggest “Intuition”.

The Incredible Exploding Image Upload

At present, the image upload function can only handle processing JPG photos. It does some processing, like creating thumbnails on the fly, that will require some extra work to handle PNG and GIF images. We will get there at some point.

Prior to the update, you were able to upload an file other than the accepted JPG and cause a nasty error where the timeline event would be half saved, but missing some key info, resulting in a “phantom” entry that showed no poster name and could not be deleted through the standard interface.

What’s worse is that the user would see something like this:

File error before

We’re now checking for this error, avoiding the phantom entry, and giving the user some clue as to what went went wrong. Also, they get a chance to try again.

File error after

Hopefully this will ease some of the pain of those testing the system in its early stages.

Thoughts? Comments?

Houston, we have a flat view!

In case the title doesn’t clue you in on what you’re supposed to be excited about, the flat view takes all the timeline events and displays them full text and image in a list. Eventually, this list will be sortable by author, post date, absolute date, astrological sign and so forth. For the moment, it default sorts by last modified. This means that we have a very rough but very functional “what’s new” page. Here’s a picture of the link. It’s across the top, between “Add new event” and “Open in new window.” I will post a shot of what the flat view looks like when you click on it as soon as the most recent entry no longer involves kittens.

flatviewlink.jpg

A footnote to this screenshot — further evidence that the duration function is not working very well. Those are “live” bars up there, but the titles are off screen and the bars rendered meaningless.

Features lost that now are found

The instructor control of the timeline parameters (setting the focus date, setting the scale and so forth) that we put in the very first version, before it even found a home in CLEo, disappeared when we went to CLEo.

After a few well-placed whines and snivels, it is now back! Frabjous day! So, we now have instructor control of the basic parameters. It looks something like this:instructor_control.jpg

The units for each pull-down menu are identical.

It’s not that you will want to be fiddling with this every day, but that when it’s wrong, it’s SO WRONG. And now I can fix it all by my liddle lonesome. Awesome.

Houston, we have print

So, we’ve got a print function now, and it looks great. I haven’t actually made it to a physical printer yet, but it’s looking fab on the screen.

Note that strange things happen in the print view when the original image actually IS the size that it displays in the smaller popups. If you look at the “Poubelle” entry, which is up in the 1880s, in print view, you see that the original picture is smaller than the new print size, and so pixelates all over the place. Is there any way to detect when the resize is making it bigger than the original, and just go w/ original size?

BTW, “poubelle” is the French word for garbage can. Because it was invented by this guy named… poubelle. Yup. Honest to gosh true.

Gentle(people), cite your sources!

Yay for “more info” and “source” fields!

The fields have been in the “new entry” form all along, but did not display in the popups. Now we are referenced, and it even scooped up things that had been entered before we enabled this feature. Nice.

Use the vertical pipe | to separate multiple links. It will even accept old-fashioned bibliography references, like books.

AND, as if this cornucopia of goodies did not already overflow, the timeline now automatically centers on your post when you add a new entry. This is fantastic – it was very disorienting to add a post to say, 1862, and then have the timeline jump you back to the same not-1862 midpoint. Now the thing you are thinking about… and then posting about… and then looking at… all flow together in one seamless moment. Gorgeous.

Big update deployed…

OK – the update is on the server.
We’ve got:
  • ugly date suppressed
  • nicer date below the title line (wouldn’t sandwich in with the title)
  • Sources and More Info display – took me a minute to figure out that some are referring to non-URL sources. Duh…
    • One glitch with this – I notice that very long URLs (like on the “Courbet’s A Burial at Ornans”) cause the window to scroll horizontally.
  • Added an edit icon in the hopes that it’s less distracting
  • Display Created and Modified dates
  • Oh yeah – found why the dates weren’t displaying on the bottom band and fixed it.