Multilitteratus Incognitus

[warning: lengthier post than usual] Before I left for December my mini vacation I had a holiday themed catch-up with a number of friends and colleagues on campus. With the semester winding down, and with the holidays as an excuse it was a good opportunity for people to get together and share some news about what had transpired over the past semester, share notes, best practices, and so on. One of my colleagues inquired how things are going in the office as far as admissions go. There seems to be some doom and gloom over falling admission on campus, but that's a topic for another day. Things are going well in my department (knock on wood), so much so that we are not able to admit all qualified applicants since we don't have enough people to teach for us. My colleague's solution (my colleague is a full time instructional designer, for what it's worth) was that we need to "change the model," instead of relying on tenure stream professors to teach our cou

It's the final stretch of 2014! This makes it my fourth year in exploring MOOCs - boy does time fly!  When I started off with LAK11 I was really just looking for ways to continue learning for free.  While I do get a tuition benefit at work, this also involves standard semesters of 13 weeks, getting work-release time (since online learning isn't covered by the benefit) and retaining the motivation to keep going through a predefined course and syllabus.  Even when MobiMOOC happened and we formed the MobiMOOC research team I really didn't foresee that the, oddly named, MOOC would catch on fire the way it did.  At the time I was eager to get some initial thoughts together on how to put together a MOOC (now they are called cMOOCs) and put together a Great Big MOOC Book , with others, that was a right mix of research and practice.  Since the MOOC has really expanded a lot over the years, with many different things being called a "MOOC" the original idea might be bett

Hey!  We've made it! It's the final blog post about #dalmooc... well... the final blog post with regard to the paced course on Edx anyway :)  Since we're now in vacation territory, I've decided to combine Weeks 9 and 10 of DALMOOC into one week.   These last two weeks have been a little light on the DALMOOC side, at least for me.  Work, and other work-related pursuits, made my experimentation with LightSIDE a little light (no pun intended).  I did go through the videos for these two weeks and I did pick out some interesting things to keep in mind as I move through this field. First, the challenges with this sort of endeavor: First we have data preparation. This part is important since you can't just dump from a database into programs like LightSIDE. Data needs some massaging before we can do anything with it.  I think this was covered in a previous week, but I think it needs to be mentioned again since there is no magic involved, just hard work! The other chall

Hurray! The first semester of my doctoral studies is done!  Well, it was done last week, but as I wrote in the previous post (on #dalmooc) it's been one crazy semester.  I had hoped that I would blog once a week on the topic of EDDE 801 , getting some interesting nuggets of information each week to share , but between MOOC like #ccourses, work, and regular EDDE 801 work, no such luck.  I felt I was putting in enough time in EDDE 801 and that I gave everything into the closed system that is Moodle rather than on the blog.  So, here's one blog post to try to re-capture some thoughts I had while the semester was in progress. Early on one of the things I really dreaded were the synchronous sessions, every Tuesday at 8PM (my time).  My previous experience with synchronous sessions was not a good one, thus coloring my expectations for this course. Most of my previous experience has been one-way communication webinars (yaaaawn), or mandatory online course synchronous sessions fo

Hello to fellow #dalmooc participants, and those who are interested in my own explorations of #dalmooc and learning analytics in general.  It's been a crazy week at work with many things coming down all at the same time such as finishing advising, keeping an eye on student course registrations, and new student matriculations, making sure that our December graduates are ready to take the comprehensive exam...and many, many more things. This past week I really needed a clone of myself to keep up ;-)  As such, I am a week behind on dalmooc (so for those keeping score at home, these are my musings for Week 7). In week 7 we are tackling Text Mining, a combination of my two previous disciplines: computer science and linguistics (yay!). This module brought back some fond memories of corpus linguistics exploration that I had done a while while I was doing my MA in applied linguistics. This is something I want to get back to, at some point - perhaps when I am done with my doctorate and

I see a lot of WTF behavior from learners. This is bad... or is it? Oh hey!  It's week 6 in DALMOOC and I am actually "on time" this time!  Even if I weren't it's perfectly OK since there are cohorts starting all throughout the duration of the MOOC (or so I suspect), so whoever is reading this: Hello! This week the topic of DALMOOC is looking at behavior detectors (types of prediction models).  Behavior detection is a type of model (or types of models) that we can infer from the data collected in the system, or set of systems, that we discussed in previous weeks (like the LMS for example).  Some of these are behaviors like off-task behavior such as playing candy crush during class or doodling when you're supposed to be solving for x . Other behaviors are gaming the system, disengaged behaviors, careless errors, and WTF behaviors (without thinking fastidiously?  or...work time fun? you decide ;-) ). WTF behavior is working on the system but not the task

Whooooa! What is all this? Alright, we're in Week six of DALMOOC, but as usual I am posting a week behind.  In previous weeks I was having a top of fun playing with Gephi and Tableau. Even thought the source material wasn't that meaningful to me I was having fun exploring the potential of these tools for analytics. This week we got our hands on Rapidminer a free(mium) piece of software that provides an environment for machine learning, data mining and predictive analysis.  Sounds pretty cool, doesn't it?  I do have to say that the drag and drop aspect of the application does make it ridiculously easy quickly put together some blocks to analyze a chunk of data. The caveat is that you need to know what the heck you are doing (and obviously I didn't ;-) ).  I was having loads of issues navigating the application, and I somehow managed to not get some windows that I needed in order to input information to, and I couldn't find where to find the functions that I

Wow, hard to believe, but we've reached the final module of Connected Courses (and boy is my brain tired!).  I found out last week that there may be a slim chance of me being able to teach Introduction to Instructional Design (INSDSG 601, a graduate course) at some point in the new future. This is something that was offered to me a couple of summers ago, but being away on vacation at the time (with questionable internet access) it didn't seem like a good idea to be teaching an online course. I've been poking around the course shell, here and there, over the past couple of years (even since teaching this course was a remote possibility) to get ideas about how to teach the course.  The previous instructor, who had been teaching this course for the past 10 years but recently refocused on other things, did a good job with the visual design of the course. It's easy to know what you are are supposed to do each week.  Then again, from the design of the course I can see th

It's been a while since Rhizo14 ended, but the community is going strong! Facebook may not be as active (or maybe facebook is  hiding most Rhizo posts from my timeline...that could be it...anyway), but we are still chugging along with the collaborative *graphy. I can't call it an ethnography, or autoethnography because variables have changed.  Some of us decided to get together and write an article for Hybrid Pedagogy on why the Collaborative *graphy article is taking so long (a meta-article if you will) but we got stuck there too (or it seems as though we are stuck).  I think others have written about their own personal views on this on their own blogs, so I've been working out what my own stumbling blocks are with this project. I think I have a way to explain things now! So, when working collaboratively in previous collaborative work situations your final product feel unified.  The main analogy that I can give give is the main root of one plant which looks like this:

Week 6 CCK11 blog connections I was trying for a smarter title for this episode of #dalmooc thoughts, but I guess I have to go with Armchair Analyst since I ended up not spending a ton of time with either Gephi or Tableau last week. So, the reflection for week 4 is mostly on theoretical grounds; things I've been thinking about (with regard to learning analytics) and "a ha" moments from the videos posted. I think week 3 and week 4 blend together for me.  For example, in looking at analytics the advice, or recommendation, given is that an exploration of a chunk of data should be question driven rather than data-driven.  Just because you have the data it doesn't necessarily mean that you'll get something out of it.  I agree with this in principle, and many times I think that this is true.  For instance, looking back at one of our previous weeks, we saw the analytics cycle.  We see that questions we want to ask (and hopefully answer) inform what sort of data w

CCK11 Tweet visualization Alright, after a few days of being sidelined with a seasonal cold, I'm back on #dalmooc.  Still catching up, but I have a feeling I am getting closer to being at the same pace as the rest of the MOOC ;-)  In any case, this is a reflection on week 3 where we started messing around with social network analysis (SNA).  This is cool because it's something that I had started doing on another MOOC on coursera, with Gephi, so it was an opportunity to get back on and messing with the tool. So, what is SNA?  SNA is the use of network theory to analyze social networks.  Each person in this network is represented by a node (or edge), and nodes  can be connected to other nodes with a vertex (or many vertices). These connections can indicate a variety of things (depending on what you are examing), however for my usage in educational contexts I am thinking of vertices as indicators of message flow, who sends messages to whom in a network, and also who refers

What do you get when you mix connected courses, thinking about academia, and cold medicine?  The answer is a blog post (which I hope makes sense) :-) As I was jotting down my initial thoughts on co-learning in the previous post I completely forgot to address some of the initial thinking questions for this module.  Here are some initial thoughts on co-learning and how I would address these questions: What is co-learning and why employ it? For me co-learning is when two or more people are working together to solve a problem and learn something new.  As I wrote in my previous post, the individuals in this community do not all need to start from the same point. There can, and will, be learners that are more advanced in certain areas as compared to others.  This is perfectly fine, and it's realistic to expect this.  This can be a community of practice, it can be a broad network of learning, or a loosely connected network of learning that centers around a hashtag.  The reason to co

I took a small hiatus from Connected Courses in the last module because everything sort of piled on at the same time and  I had little space to breathe.  Yes, I've been dalmoocing, so I guess everything is a choice ;-).  I guess that was my jump-out week of connected courses, and now I am dipping in again. I love the language of cMOOCs ;-)  The truth is that I've felt a little fatigued with #ccourses.  I am not sure if it's the length, or the time I've been engaged with it (7 weeks if you consider the pre-course and that's before we got to Diversity, Equity, and Access ), so I guess I needed a little mental break.  I don't think this is an issue unique to MOOCs because I've been feeling a mild case of senioritis in my first EdD course. Luckily I've done all of my deliverables, submitted them, and have gotten feedback, so now I am participating with my peers and engaging in the participation aspect of the course. Anyway, these next two weeks are ab