Category Archives: DoOO

Neither Locked Out Nor Locked In

I want to make sure before I begin that I extend my thanks to both Reclaim Hosting and the University of Oklahoma for organizing this event and for including me in it. Domain of One’s Own is a project that has consumed a large amount of my professional life for the last four or five years (and a large part of my heart and imagination for probably another 5 years before that), and building it back in the day with Jim and Tim at UMW was truly one of the most rewarding professional experiences I can ever hope to have. Moreover, seeing it flourish and grow and develop at institutions like the University of Oklahoma under the leadership of people like Adam Croom has been fascinating and humbling and richly instructive. I learn much more from DoOO and all of you who are involved in it than I can ever hope to contribute back to it.

Continue reading Neither Locked Out Nor Locked In

Messy & Chaotic Learning: A Domains Presentation at Keene State College

The following is the text of a presentation I gave at Keene State College on March 31st, 2017. 

When I was asked to come speak at Keene it was due, in part, to a presentation I gave last summer at Digital Pedagogy Lab Institute at Mary Washington. My presentation was titled Making & Breaking: Rethinking the Web in Higher Education, and the purpose of that talk was to disentangle a bit of the history of the Web within colleges and universities. My thesis was that we in higher education have spent far too long avoiding larger conversations about the Web: what it means to our culture and communities; how it’s re-shaping our social and political landscapes; how it’s altering the work of our individual disciplines; and, on a whole, what role schools of higher education should be playing in helping our citizenry understand all of these factors. Continue reading Messy & Chaotic Learning: A Domains Presentation at Keene State College

Looking (again) to Domain of One’s Own

When I moved into my new position at UMW a year and a half ago, directing the Digital Knowledge Center, I knew that while I was moving out of faculty development  and instructional technology that I would still be working with our Domain of One’s Own project. However, I wasn’t exactly sure what my role in that project would continue to be on a day-to-day basis. A year after the start of the new position, in summer 2015, the Center was actually moved out from under the Division of Teaching and Learning Technologies, moving me further away, organizationally, from the base of operations of DoOO within DTLT. On top of that, a wholesale turnover of my colleagues in DTLT from summer 2015 to summer 2016 has meant that many things have been in flux around here, generally, and, specifically, that’s meant a new consideration of how Domains fits into the work of our larger unit (Teaching, Technology, and Innovation led by Jeff McClurken) as well as how it integrates with my own particular position at the University.

Continue reading Looking (again) to Domain of One’s Own

Refactoring Domain of One’s Own (and everything else)

It’s been over a year since I wrote in this space. There are lots of reasons for that. Most significantly, the last 12 months have seen enormous change in the division that I’ve worked in here at UMW, Teaching and Learning Technologies. If you follow me on social media, you know all about the changes. Suffice it to say, I spent the first part of this period of change largely grieving the departure of many people who I consider friends in addition to treasured colleagues. Luckily, I’ve spent the second half of this transition welcoming a new group of wonderful people to the University. Change is hard and sucks; change is good and valuable.

Continue reading Refactoring Domain of One’s Own (and everything else)

Visualizing & Exposing Domain of One’s Own Activity

Now that Tim and I have successfully built a site at community.umwdomains.com that aggregates the activity of the project, I’ve been focussing my efforts recently on what we can do to visualize and expose that activity. Every site that is created (as long as it uses Installatron to install a Web application) on the server as well as much of the content on those sites (as long as the content is available via RSS feed) is being pulled into the WordPress install that runs Community. That means currently we have information about 800 sites and almost 3000 pieces of content from those sites. For sites, we ask users to self-report the course they’re building it for as well as their “status” (student, faculty, staff). From the course data, we’re able to glean instructor and department. We’re also tagging sites with semester information. Content from these sites is similarly tagged with course, instructor, department, and semester information.

That’s a lot of content to play with, and it’s been fun to develop tools to allow users to explore all of the information.  Continue reading Visualizing & Exposing Domain of One’s Own Activity

A Few Models of Teaching in Domain of One’s Own

A few weeks ago, I blogged about the current status of UMW’s Domain of One’s Own project and this prompted UMW’s own Mark Snyder to respond on Twitter:

Which was very nice except that I didn’t really think my post did much to describe ways that faculty could use DoOO in their classes — it was more a rundown of our successes and challenges in getting the project up and running over the last six months. So, I told Mark that I would try and do a post that dealt more specifically with how Domain of One’s Own is being used by faculty in actual classes.

This one is for you Mark — never say I never do anything for you!

Continue reading A Few Models of Teaching in Domain of One’s Own