Tuesday, September 9, 2008

Online Learning: Monitoring Metrics of Most Worth

Simple question: What measurable metrics do you think would be worth monitoring in online learning environments? Simple question must have a simple answer then – right? Wrong!

First of all where do you draw the line on what is/is not a ‘learning environment’ when most all online environments could be broadly defined as such? Getting past that… I thought this would end up being a simple listing of some generalized data that would be helpful to know – and I could probably make a quick list of those. However, that got me thinking about how to systematically produce that list. The more I thought about that, the more complex things got. This is a rather haphazard enumeration of some of my thoughts:

1) Some of the data to track will be ‘application’* specific, and some will generalize to all applications, others will be specific to types or families of applications. It would be most helpful to start with a (maintained by someone?) list of the latter two, and then just have to think hard about what is specific (if anything) to this app.

2) One aid in helping to analyze or ferret out the data to track, might be to do so by design layers. I’ve not yet determined if imposing a ‘layered structure’ clarifies and helps to define the data to track – or if it just serves as a reasonable organization of “bins” into which the interesting data bits can be categorized. For example: right off I know I want to track where the user ‘came from’ and where s/he travelled in ‘my world’ and where s/he went after leaving. So I look at this and say – hmmm seems to fall into the ‘Control’ layer. On the other hand I might say: What else do I want to track in the ‘control’ layer? I also know I want to see what the user was “searching for” (if anything) when they found/arrived at my application, this seems to fit in the Message Layer. It gets really weird (with a folding over) when I started to consider the data/management layer – which is kind of what the web analytics is all about anyway, but we would probably want to track info about that as well. Is that meta-meta data?

3)Many of the attributes of tracked data are common such as: Counts (how many times), Durations (how long), Frequencies (how long between), and Sequences (order). These attributes would apply both internally(within my application) and externally (to/from my application)

4) Many of the metrics dealing with assessment (mastery/proficiency) could be found in SCORM, or other LMS -- but do we really want to take on that 'load'?

*By way of clarification, when I use the word “application” it is in a very broad sense and could be referring to a tool, widget, blog, wiki, learning object, an interactive (as if there existed a non-interactive) data-base, etc., etc.

Read More......

What I hope to gain from our webanalytics class

I want to have enough 'hands-on' experience with webanalytics to understand how I could use it (and the information it provides) in furthering objectives for electronic media used for education, training, research, and personal purposes.

Currently, I'm specifically interested in applications for:
1) computer adaptive testing
2) more information about the success (or lack thereof) of a pilot group blog I'm planning to set up in conjunction with personal leadership responsibilities. Read More......

Every Command with 'Eggs'actness

Assignment: "Something" funny.

I've shared this with several classes I've taught - or attended. I haven't quite figured out what makes it so "funny" yet - but I do know that even though it took place years ago, I continue to find parallels to life and lessons I've learned.

One summer during my college years while working as a waitress I was having a particularly 'bad' day. The dining room was extremely busy, at least one waitress had called in sick, and the cook was even more cantankerous than usual, as were the customers – or so it seemed. I wondered why I seemed to get all of the patrons who wanted special menu items, treatment, or substitutions. As the morning wore on, we quickly ran out of several items, which did not improve the attitude of the cook or the customers. It was in this state that I met Ms. Demanding.

Ms. Demanding ordered a "2 minute" egg, meaning an egg boiled for two minutes. My first reaction was to ask her where she was from. She looked at me a little quizzically, and curtly answered "California". I then tried to explain that a two-minute egg in California was NOT the same as a two-minute egg in Utah. Obviously dismissing my comment as one which made no sense, she emphatically restated: "I want a two-minute egg! NO MORE, NO LESS! Do--you --understand?"

"Yes ma'am!", I replied as I quickly walked away, trying to decide whether to give her exactly what she ordered as a sure way of educating her, or to simply translate the boiling time in consideration of altitude. My inner debate was cut short when the cook told me to put the order up on the wheel, or go away until I was ready to do so. Of course when he saw what was ordered, he swore – at the customer and me. He also started to explain in as demeaning way as possible what a two minute egg would be like. I just said "I know, but she insisted." A sinister little grin crossed his face as he put the egg in the boiling water, and set the timer for exactly two minutes.

A few minutes later when the cook rang the bell to indicate the order was ready, everything looked great. This was a relief as previous versions of pancakes, waffles and hashbrowns had come out of the kitchen that day with a hue ranging somewhere between charcoal and midnight black. The soft boiled egg was in a little bowl with the shell still perfectly intact. I delivered the meal to the table where Ms. Demanding sat, and was met with: "We need more coffee here as soon as possible!".

When I returned to the table with a pot of coffee, she had cracked the egg open and viewed a two-minute egg in Utah – in all its slimy splendor. "Take this back – I can't eat this! I ordered a TWO-MINUTE egg!!" she shrieked.

I replied as civilly as possible: "Ma'am, that IS a two minute egg in Utah. Higher elevations require a longer cooking time."

"Well take it BACK and give me what I WANT!" she shrieked again, her pitch even higher. I wondered as I returned to the kitchen, just what she expected me to do, put it back in the shell, and boil it longer? Just then I noticed.........the microwave!.

[In my defense, and at the risk of dating myself, I need to explain that at this time, due to their cost, microwaves were not yet common household appliances.]

Just then the manager walked by, and I told him of my predicament. He warned me that I needed to watch the egg very carefully, as they would explode in the microwave if cooked for too long. So I took extra precaution to set the 'dial' on the very first mark (digital time settings were a future design improvement) and waited. I did this about three times, until the egg looked perfectly soft-boiled. It did not explode. Finally, something had gone right for me today! I hurried to return the egg to Ms. Demanding. Upon receipt of the egg she informed me that her waffle was now cold, and to take it back and re-heat it – another command which I diligently obeyed.

As I was standing at the microwave waiting for the waffle to reheat, my manager hurried into the kitchen area and told me "You'd better go check on your customer – her egg just exploded on her!"

It seems that at the very moment Ms. Demanding had pierced the yolk with her fork, her egg had stunningly exploded. I was told that it sounded just like a gunshot, and that everyone in the dining room jumped. I tried to compose myself, and to stifle any trace of a smile as I approached Ms. Demanding's table.

The egg was literally (if not figuratively) all over her face, and down her shirt. By the look on her yolk-covered face, I thought I was going to need to treat her for shock, but she quietly excused herself to go to the restroom. As she left, her husband exclaimed: "What the hades do you feed those *%&!@# chickens in Utah anyway, gunpowder?" (edited version)

I spent the rest of the day cleaning egg off of EVERYTHING. It was on the ceiling, it was on the chairs, it was on the carpet, and it was even on the walls clear across the dining room.

What did I learn? Simply this: "Don't nuke the egg!" (even if the client's requirements seem to demand it) Although it took several experiences in software development to connect the day in the dining room to the day in the conference room, it is a strong analogy that I will probably not forget.
Read More......
 
Locations of visitors to this page