Warning: Constant FS_CHMOD_DIR already defined in /home/umwdtltc/public_html/wp-config.php on line 101

Warning: Constant FS_CHMOD_FILE already defined in /home/umwdtltc/public_html/wp-config.php on line 101

Warning: Cannot modify header information - headers already sent by (output started at /home/umwdtltc/public_html/wp-config.php:101) in /home/umwdtltc/public_html/wp-includes/feed-rss2.php on line 8
Domain of One’s Own – UMW Division of Teaching and Learning Technologies https://umwdtlt.com Fri, 06 Apr 2018 16:28:28 +0000 en hourly 1 https://wordpress.org/?v=7.1.5 https://i0.wp.com/umwdtlt.com/wp-content/uploads/2017/11/cropped-dtlt-black1.png?fit=32%2C32&ssl=1 Domain of One’s Own – UMW Division of Teaching and Learning Technologies https://umwdtlt.com 32 32 103540615 What’s a Sysadmin to Do? — Avoiding Digital Detritus on a Blogging Platform Older than All of My Kids https://umwdtlt.com/whats-a-sysadmin-to-do-avoiding-digital-detritus-on-a-blogging-platform-older-than-all-of-my-children/ Fri, 06 Apr 2018 15:28:36 +0000 http://umwdtlt.com/?p=57639 We have a lot of blogs.

I don’t just mean those of us in DTLT — we do have a lot of blogs. I mean the University of Mary Washington. UMW currently has over 2500 active domains in our Domain of One’s Own program (and almost 3500 domains all-time), and that’s to say nothing about how many blogs and websites are on those domains and their subdomains.

But before there was Domain of One’s Own there was (and still is) UMW Blogs. After three years of DTLT staff and a few UMW faculty experimenting with blogs in and out of class, UMW Blogs launched in 2007 — a WordPress installation that allowed any student, faculty, or staff member to get their own subdomain (like mygreatblog.umwblogs.org) and WordPress site, administered by DTLT. Since then, the 600 blogs of 2007 grew to over 11,000 blogs and 13,000 users in 2018!

Maintaining these platforms can be quite a challenge. Domain of One’s Own is more individualized, stable, and flexible, and we get great support from our hosting company, Reclaim Hosting. But maintaining our legacy system, UMW Blogs, at the same time seems to alternate between idyllic bliss and mass panic. It’s not very heavily used, but when something goes wrong, it goes really wrong, bringing down every site on the system. And with a number of sites that haven’t been updated since the twenty-aughts, there are many outdated themes and plugins that are poised to cause such problems.

Of course, we can’t just pull the plug. Some of our faculty and students are still using UMW Blogs, and many of the sites no longer being maintained are important to our institution and its history — whether it’s an innovative (for its time) course website, an awesome student collaboration, or an important piece of institutional history. Even while we encourage students and faculty now to use Domain of One’s Own, we want to ensure the UMW Blogs system works and those important pieces of our institutional history don’t become digital flotsam.

With that in mind, we’ve embarked on a major project over the past few months to ensure the stability of our legacy system and the long-term preservation of UMW’s digital history. On my last day as a member of DTLT 🙁 I’m going to chronicle some of those efforts, both for the benefit of the UMW community and for those at other institutions who find themselves (or soon will) in a similar situation.

Digging deep

UMW Blogs has some really interesting stuff on it! A group of students (some of whom are now UMW employees) catalogued the historical markers throughout the Fredericksburg/Spotsylvania area, mostly from the Civil War, providing important historical context. A student wrote love letters to his girlfriend at another university regularly for several months, leaving her coded messages and invitations to dinner dates (“don’t forget the coupon!”). (I’m not linking to that one because, while it is public, the couple may not remember that they are still public… more on that issue later.) Two colleges on campus hosted their Faculty Senate sites there (no longer public). Student government leaders (and campaigns) hosted sites on UMW Blogs. And there are historical sites from many student clubs, activists, and research groups. And who can forget Ermahgerd Sperts! Or my nomination for best username: umwblogs.umwblogs.org.

That said, we also have about 700 sites that were last updated on the same date they were created. (“Hello, World!”… and nothing since :/ ) We also have a number of sites that have “broken” since they were last maintained — mostly using themes and plugins that have not been updated to retain compatibility with upgrades to the WordPress core platform. And sites that, while valuable to some at the time, have been neither updated nor visited in a loooooong time.

In fact, we identified over 5000 blogs on the platform that have not been updated since 2015 or earlier, are not administered by any current UMW community members, and have either not been visited at all in the last two years or have been visited less than 100 times in the time period for which we have analytics. That’s essentially half the platform that is inactive and no longer providing benefit to users, but which is also open to vulnerabilities or “bit rot” that can cause problems for the active sites.

Here’s the thing, though. Some of the inactive sites we identified are also important pieces of institutional history.

So I did my data-science thing and identified a list of blogs that meet all of the following criteria:

  • The blog has not been updated since before Jan 1, 2016.
  • None of the blog administrators are current members of the UMW community.
  • The site has either not been visited at all in the last two years, or has logged less than 100 visits all-time.

And then Lee, our two student aids Bethany and Stefanie, and I went through the entire list to identify sites important to our institutional history, as well as course websites that are less than five years old. (Some courses are offered every three or four years, and having relatively recent course websites live can be useful for faculty and students, even if they haven’t been visited in the last couple years.) These are sites that we either think should be kept on the platform, or — more likely — that we think would be good candidates for UMW Libraries’ new Digital Archive. The latter will create a flat-file archive (no databases or dynamic content) that will be far more future-proof and less likely to just break one day. (You’ll likely be hearing more about that in the future!!)

Now, we didn’t visit all 5000+ blogs manually! Rather, we looked carefully at the metadata — site titles, the person(s) attached to the sites as administrators, the administrator’s email address, and the dates the sites were created and last updated. This gave us a really good idea if the site was created by a student or faculty member, if the site was a course website, collaborative student project, personal blog, etc. We identified almost 300 sites from this collection that we did check manually, often consulting with each other about them, before deciding on the 62 of these 5000+ sites that were important to keep public or submit to the Digital Archive.

What to do with all these blogs?!

In the end, we determined that of the 11,333 blogs on the UMW Blogs platform, 6012 of them were important to keep active (including about 50 which would best serve the UMW Community by being frozen and publicly archived before “bit rot” and broken plugins bring them down). The other 5321 blogs, many of which were important in their time, are ready to be removed from the platform. Now, we’re not talking about just deleting them! We are working with Reclaim Hosting to create a flat-file archive and a WordPress XML export of each of those blogs, which DTLT will retain for probably 2 years before permanently deleting them. We are also preparing to email the administrators of those sites to let them know our plans so they can download their content before we remove anything from the platform (or, worst-case scenario, ask us to email them the backup archive after we purge the platform). But ultimately, it is important for the health of the platform to streamline the database and focus on supporting the more recent and active sites.

There’s another issue that has been pressing on our minds — mine especially. UMW Blogs does not have a Terms of Service like Domain of One’s Own does. And while past members of DTLT (none of which are administering the platform anymore) told users that their UMW Blogs sites would be hosted basically forever, that presents a major data ownership and privacy issue. The internet is a different place than it was in 2007. According to Paul Mason, the entire internet in 2007 was smaller than Facebook is today! And that’s to say nothing of the changing ways in which we view our personal data, even our public creative work, since GamerGate, Ferguson, and Cambridge Analytica. And as the birthplace of Domain of One’s Own,  UMW (and DTLT in particular) has focused more and more on the ownership aspect of writing and working on the web — empowering students to make critical decisions about what they put on the web, what they don’t put on the web, and what they delete from the web.

We’ve received a number of requests over the past couple of years from alumni for us to remove their blog from UMW Blogs, or a specific post they created on a faculty course site, … even specific comments they left on classmate’s blog as part of an assignment. We are well aware of the vulnerabilities that working in public can create, as well as the ways in which we as people change and grow, leaving behind aspects of the (digital) identity that we once shared with the world.

And so, beyond the need to streamline the platform, we think it’s important for the sake of our former students and faculty that we take the initiative to remove old content from our public platform, and pass it along to them so they can decide what of it should be public and where it should be hosted.

So over the next few weeks, after everything is archived locally and before anything is deleted from the platform, DTLT will be reaching out to those former students, faculty, and staff, letting them know our plans, and providing them the opportunity (and documentation) to export their data and preserve it publicly or privately, in a place of their choosing.

This not only helps those currently on the platform have a better experience, but it helps our former community members once again reflect critically on their public digital identity and take a bit more ownership over their data and what’s done with it.

I hope that helps explain a bit of the what and the why of what we’re doing here. As a proponent of “digital minimalism,” I often tell my students and colleagues that what we delete is as important a part of curating our digital identity as what we publish. And our freedom to delete increases our freedom to experiment. As the attention economy and algorithmically driven content discovery have radically changed the internet since the early days of UMW Blogs, it’s worth rethinking both what we as an institution hold onto, and what we as individuals decide to keep in public venues.

This process has been more than just streamlining a platform to make it run more efficiently. It’s been a time for us to reflect on these things a unit. And hopefully it will encourage others to do the same.

]]>
57639
Introducing the Bootstrap Starter Kit https://umwdtlt.com/introducing-bootstrap-starter-kit/ Mon, 16 Oct 2017 14:41:56 +0000 http://umwdtlt.com/?p=56606 Bootstrap is an amazing library for web developers. It has almost every element most developers need, pre-defined in ways that are easy to use, and truly attractive. No messing with margins, padding, pixel widths, hexadecimal color codes, custom-designed buttons and menus — you simply write your text, use basic HTML, and with a few custom Bootstrap options in your code, you’re well on your way to a functional, visually appealing site. And there are a lot of custom themes floating around. It’s a great way to build a website with the control and stability of hand-coding, but also the visual appeal of more advanced design tools.

In other words, Bootstrap helps you make hand-coded websites, without them looking hand-coded.

The problem is that many of the themes don’t come with everything you need! For a seasoned designer/developer, that’s not a problem. But for students like mine, it can be a big problem. So I built something to try and help.

The backstory

Lots of students want (or need) to learn HTML, CSS, and maybe a little JavaScript, so they can get under the hood and make their websites really stand out. But if you’ve hand-coded a website from scratch, you know how long it can take to get your coding skills to the point where you can make it look the way you like. And that’s assuming you have training in design (or at least a good eye for it).

I had one such student in my office last week. She’d done WordPress before, and wanted to try something different for her domain project in my Digital Storytelling class. After wrestling for a few weeks with Known, she decided she wanted to just learn some HTML. Even if it wasn’t the world’s greatest website in the end, she’d have learned a new skill. And she already knew WordPress, anyway.

I suggested she use Bootstrap to frame her domain project. After all, once she picked her theme and started the site, she’d be doing the same HTML work, and I could help her get it all organized…

90 minutes later, we finally had enough of the dependencies collected that she could start putting some content on her site! I thought, there’s got to be a better way. (And after lots of Googling around, it seems that there really isn’t.)

So before I forgot what we did, I picked a theme, collected all those files, fonts, and folders on my own computer, and built a small sample website. Then I zipped it up, so anyone could download it, extract it into their shared hosting environment, and start building their own site.

The result is Bootstrap Starter Kit.

The details

Bootstrap Starter Kit is based on the United theme for Bootstrap (inspired by Ubuntu Linux’s “Unity” desktop theme), made by Thomas Park and licensed under the MIT License (open-source). United is one of many themes available from Bootswatch — a place to find some great stuff, but where clicking “download” doesn’t give you all you need. (In fact, even clicking the drop-down menu and downloading all the files listed doesn’t give you everything you need.)

If you go to the examples page, you’ll see all the things the Bootstrap theme can do out-of-the-box. And that examples page is included in the ZIP file, so you can copy and paste the code, tweak it to your heart’s content, and learn how it all works in the process.

I’m hoping this starter kit will be useful for people, especially students learning HTML and CSS. If you use it — or if you find it’s still missing something! — let me know. And if there’s a lot of demand, I’ll look to coding some other themes and posting them as well.

Happy building!

Featured image by Jonatan Pie on Unsplash

]]>
56606
Digital Knowledge: a Domain of One’s Own Faculty Initiative https://umwdtlt.com/digital-knowledge-a-domain-of-ones-own-faculty-initiative/ Tue, 25 Jul 2017 12:03:18 +0000 http://umwdtlt.com/?p=54982 As UMW’s President Paino said in his inaugural address, digital fluency is the ability “to consume and produce digital knowledge critically, ethically, and responsibly, as well as creatively adapt to emerging technology.” He talked further about the importance of “reconstituting the liberal arts for the digital age.”

We often see the digital as ephemeral, as virtual, as not real, but it has had an increasingly direct impact on our lives, politics, culture, and education. Putting the word “digital” in front of “knowledge” or in front of “liberal arts” begs a whole host of questions: What work does “digital” do as an adjective? What do we imply or privilege if we use it as a noun (“the digital”)? How do digital technologies change the ways we produce, disseminate and consume knowledge? Does social media indeed have a democratizing effect, as many have suggested? What inequities has it unearthed or enhanced? How are virtual spaces helping to enliven (or disengage us from) physical spaces?

And, importantly, when we say “digital knowledge,” how can we see knowledge as acting also upon the digital? What is the role for educators in helping construct new pathways into, out of, and around the digital? At University of Mary Washington, how does our shared commitment to the liberal arts give us tools for critically evaluating our digital technologies and for asserting agency in digital spaces where that agency might be under threat?

UMW’s Domain of One’s Own (DoOO) is both a platform and also a philosophical approach for exploring these questions — for helping educators and students alike think through their digital identities and their role in the larger community of the Web. DoOO also offers an incubator for experimentation with digital pedagogies and ethical online learning.

A Community of Practice

In Fall 2017, the Division of Teaching and Learning Technologies will gather together 6 – 10 UMW faculty and staff members for a series of discussions and practical labs centering around this idea of “Digital Knowledge.” We will meet 7 times throughout the semester for two hours. The first hour will be dedicated to discussing historical, theoretical, and pedagogical foundations for our work together. Some of these will be chosen in advance, but many will be suggested by the group, allowing the trajectory of our conversation to emerge organically based on the expertise and interests of the group. During the second hour, we will work individually and collaboratively to design digital projects for a future course or educational experiences (with support from members of DTLT and the DKC).

A Continuing Cohort

Members of this faculty initiative will be paired with one or more instructional technology specialists in DTLT for continuing support of their project. They will have the opportunity to gather in the Spring to reflect on their work. And we will host a panel in late Spring 2018 as part of our series of Digital Liberal Arts events.  

A sampling of the kinds of readings we’ll discuss during the first several weeks:

Ray Bradbury, “There Will Come Soft Rains”
Audrey Watters, “The Web We Need to Give Students”
David Weinberger, Small Pieces Loosely Joined (preface and chapter one)
Seymour Papert, Mindstorms (preface and introduction)

UMW Full-time Faculty, Adjuncts, and Staff can click here for additional information and application instructions. (Applications are due by August 11.) But anyone can follow along via the event page, this blog, and the #DoOO hashtag.

Featured Image by Lance Asper on Unsplash

]]>
54982
#Domains17 Reflections https://umwdtlt.com/domains17-reflections/ Mon, 12 Jun 2017 18:51:12 +0000 http://umwdtlt.com/?p=54946 Has it been a week already since #Domains17 started? Was it already a week ago where I was getting ready to hear Martha Burtis’ amazing keynote, while reconnecting with so many people in this community of critical digital pedagogues?

Martha asked us, if the Web were a concrete space, what would it look like? I wonder, if DoOO were a person, what would she look like and who would she be?  

Conferences are strange, liminal spaces for me. You fly away somewhere, often to meet with people who live just up or down the proverbial road, or people you’ve been connected with for a long time on social media. You’re taken out of your usual routine, allowed for a brief moment, to rediscover and then focus in on what matters to you most, and in this case, it’s the Domain of One’s Own project, as it has been reimagined, iterated, integrated in different places.

I was representing my employer and my unit, the University of Mary Washington’s Division of Teaching and Learning Technologies, the birthplace of DoOO, the place that others at the conference are looking to. Personally, though, I feel like many of them probably do – still new to the project, to the initiative, despite (again, like many) having followed the project from afar for a long time. Maybe even a little intimidated, still, by the scale and scope and importance.

DTLT is well-represented, with Jess talking about working with students and then faculty on and with DoOO and Jesse asking what if bell hooks made an LMS. Kris chimed in from afar, interrogating what we mean when we talk about ed-tech being indie, open, and free. Myself, I spoke about our DoOO curriculum briefly, before handing it over to the participants to remix their own curriculum modules (see the GitHub page I created for the session). I didn’t have a catchy take-away, other than creating spaces for collaboration and creativity, even under tight time constraints, can be productive. And, I want to share what we’ve done, and share in what others are doing. That session, and these modules, are a version of an olive branch, to plant, to grow, to flourish.

Like any conference, I live-tweeted the sessions I attended (I also set up a full archive of the conference hashtag). I focused on sessions addressing pedagogical issues, like Lora Taub’s talk on Valuing Voice and Jim Luke’s on Running for Ideas at a community college and starting a DoOO project (see the full itinerary, as well as links to a majority of the presentation).

 

 

 

And I was struck, as I often am, by this particular slide from Jim Luke, and then by this tweet from Audrey Watters and it led me to ask, who are these DoOO schools? By and large, UMW is still an outlier as a public, liberal arts college, much like Lansing Community College, where Jim Luke works, is an outlier as the lone community college on the list. The dominant schools are either large R1 institutions or small private liberal arts colleges (the exceptions really being CSUCI and UW Green Bay – CUNY is only available through The Graduate Center).

(Update: Lauren Brumfield from Reclaim Hosting tweeted out that the list of DoOO schools had been updated. There are more than a few community colleges and public state institutions have been added to the list. But that wasn’t reflected in the attendance at the conference, unsurprisingly, but that’s the issue, as well isn’t it? Resources available to faculty/technologists from those institutions to attend a conference like this.)

So what does this mean? It means that, for most, the potentially most innovative, liberating, forward-thinking, pedagogically empowering piece of ed-tech is restricted to those privileged enough to attend a top school, which means the socio-economic makeup of the students benefitting from DoOO is in a lot of ways a monolith. I want students at Hispanic-Serving Institutions, HBCUs, regional public teaching-centered state universities, which have traditionally served first-generation students to benefit from the transformative potential of DoOO, instead of being subjected to digital redlining and surveillance.

There was a tension during the two days between the practical and the aspirational, how we “sell” DoOO versus how we conceptualize and teach with and through the project. As I said in my Virtually Connecting session, there is always a danger of leaving people behind, or making them feel excluded, because of where we hope to go with our students through the project. A small handful of schools are trying to shift the conversation, but it’s still a small handful. We have done well to shift, but have we done as well as we can at expanding that conversation and including the practical concerns that a wider variety of institutions have “on the ground” in order to make something like this a reality?

So where does that leave me, post-Domains 2017? I’m committed to the open, collaborative spirit of the project, now more than ever. But I am also committed, in that same spirit, to finding ways to create more seats at the table. I really think that Jon Udell’s work in simplifying and de-complexifying work around domains has potential (think minimal computing), so I am excited to help amplify these initiatives. There’s a spot in the garden for everyone.

Featured Image by Karsten Würth on Unsplash

]]>
54946
Domain of One’s Own at UMW: The Data https://umwdtlt.com/domain-of-ones-own-at-umw-the-data/ Fri, 24 Feb 2017 15:50:29 +0000 http://umwdtlt.com/?p=54052 How many students are on Domain of One’s Own? How many faculty? How many sophomores signed up last semester? Which freshman seminars are using Domain of One’s Own? How many domains will expire this month? Which of those belong to graduates, and which need to be renewed? Which platforms are most frequently installed? (WordPress, Known, DocuWiki, Omeka, etc.)

Each of these questions requires looking at data that lives in a different place. In fact, some of them require comparing data from multiple sources to answer. This can make it difficult to gain even a bird’s-eye view of the program, as even some of the big, overview questions require getting into the nitty-gritty details in order to properly merge databases and get an accurate answer.

But not anymore.

Total active domains by month over history of UMW Domain of One's Own

Over the past three months, in between other projects, I’ve been building a data management and reporting system for UMW’s Domain of One’s Own program. Today I’m happy to announce that the public-facing part of that system, the dashboard-like site data.umwdomains.com, is now live! This site is a Shiny App run on a Digital Ocean virtual private server, built on R scripts that pull and merge data daily from several different sources:

  • our Enom domain registrar account (current information via their robust API)
  • a manual Enom transaction report (for historical account data)
  • user account data on umw.domains (via the WordPress REST API)
  • Banner, our institutional information system (via a manual pull from UMW’s SharePoint database system)
  • WHMCS, our client management system (merged with Banner in SharePoint)
  • Some manually created data tables containing information missing from one or more of these sources (usually for former employees or irregular accounts from the original DoOO pilot)
  • coming soon: data from an installatron plugin written by Martha Burtis that records app installations and asks users to volunteer information like if the site is for a class, and if so, which class and instructor

New DoOO registrations per academic year, students and faculty

This is a lot of data. Figuring out how to clean, wrangle, and merge it all into a single coherent entity was a challenge, especially as I was learning a lot of the tools involved while doing it! But we now have all of this data in one place, making it much easier to ask questions like how many sophomores signed up last semester? or how many students will be graduating (and need to migrate their data) this spring? This is a big help for our planning, our account management, and ― as we get more data about usage in specific courses ― our faculty development offerings and our creation of documentation and other resources.

While this dataset makes it easier for us to access the data we need, it also raises questions about user data privacy, something that DTLT cares about deeply. So I should note that we (and the keepers of the institutional data at UMW) have been careful not to collect data we don’t need or that will compromise user’s privacy. In fact, the only new data collection is the plugin that records app installations and asks about class usage. Other data is already necessary to run Domain of One’s Own (name, domain, email address, student/faculty/staff status, active/inactive/graduated student, etc.) or are standard university personnel data (class, matriculation date, anticipated graduation date, etc.). We’ve also taken care to ensure that the API links between umw.domains, data.umwdomains.com, and Enom are secure, and that the online data storage is secure.

We’ve also drawn a clear separation between what we’re comfortable sharing publicly on data.umwdomains.com, and what we’re restricting to internal reports. As you can see on data.umwdomains.com, we only post broad, aggregate data in public: total domains allocated over time, signups by year/semester/month, divided by faculty/staff and students. In the future, we’ll also likely add information about app usage (once we have more data), and  break down student data by class ― Fr/So/Jr/Sr/Grad (once I write a couple functions to convert current class and/or graduation date into student class when they signed up).

Internally, we collect and report more information. I’ve written an RMarkdown script that will generate a report each month containing more detailed information. Here’s a sample of the test report for January:

Monthly report: January 2017


We had 82 new domain registrations, 533 renewals, and 3 domains expire in the month of January 2017.

New registrations by group

group class count
Student Senior 31
Student Junior 27
Student Sophomore 13
Student Freshman 9
Faculty/Staff Senior 2

Domain registrations by class, past six months

Below the class-by-class breakdown is a list of all the students and faculty/staff who signed up for Domain of One’s Own last month, with their domain URL, their email address, their status (student or faculty/staff), and their signup date. Once I’ve added course data to the mix, we can add that to the report as well. The monthly report also gives us a list of domains and users whose domains expired in the past month.

The report also does some projecting for future months. Here’s a sample of the test projection for February.

Monthly projection: February 2017


In February 2017, we have 7 domains scheduled to expire (or renew).

Based on a linear model of past Domain of One’s Own registration activity, we expect approximately 34 new registrations in February 2017. Please note that these projections are only rough estimates, based on a small data set without accounting for special events and initiatives that may have contributed to registration counts in the past.

All DoOO February registrations

Note that student class in this plot represents their current class, not their class at the time of signup. Most of the time, then, ‘NA’ means graduated students. In the future, I’ll add some nuance to this so that we can see both “Class of 2017”, “Class of 2016”, etc. and Fr/So/Jr/Sr/Grad at the time of signup. Both of those distinctions will be helpful for us to track, but requires a little more wrangling of the data to produce.

The report also contains a list of the users and domains set to expire or renew that month, so we can ensure that auto-renew is on or off, as appropriate. Knowing who is rolling off or renewing, and knowing how many new domains to expect in the upcoming couple of months can help ensure that we’re properly supporting and funding the program.

I’m really excited about this. It was fun to build, I learned some cool things while doing it, and it will help us ensure that we’re doing right by UMW’s students, faculty, and staff as Domain of One’s Own continues to grow. If you’re at another institution with a Domain of One’s Own program and want to see if these reports will fit your setup, please checkout the code on GitHub. Private data has been omitted, but all the scripts for the data wrangling, the Shiny App, and the RMarkdown report are there for you to test out!

Header image by Bruno Scramgnon (CC0).

]]>
54052
Can Higher Education Save the Web? https://umwdtlt.com/can-higher-education-save-the-web/ Tue, 14 Feb 2017 19:26:28 +0000 http://umwdtlt.com/?p=53989 As an author, I can’t be sure whether you are reading this article online or in print. But if you are reading it online, something depressingly familiar is about to happen.

If I’m lucky, maybe you’ll enjoy the article. Perhaps I’ll make a point that you think you agree with, then another. And if you’re like most Internet users—addicted to Facebook or Twitter—it’ll be around the third “mmm-hmmm” that you will begin to struggle with the overwhelming question: should I tweet out a link to this? Should I share this article on Facebook? You will read the article, but only half read it, with one-half of your brain evaluating the Facebook-ability of your post and the other half attending to my words.

This is by design, of course. As many commentators have noted, the recent technologies we use for the web bear more in common with slot machines than books.1 They are primed to keep us clicking, watching, and pulling-to-refresh, ever desirous to find the next new thing that everyone will be posting and tweeting.

We’re not distracted only when reading, of course. Consider that 59 percent of links shared on social media have never been clicked; this means that the majority of users are sharing articles they have never actually read. Algorithms that decide what we see produce “filter bubbles” that trap us in cocoons of homogeneous opinion. Facebook’s algorithms for selecting trending stories routinely surface fake news stories, encouraging users to spread them further.2

Just yesterday, a good friend of mine shared a story on Facebook from an anti-Semitic conspiracy site. My friend is neither anti-Semitic nor a conspiracist. But over the course of the 2016 U.S. Democratic primary, he had signed up for certain Facebook pages associated with supporting Bernie Sanders. Since content that induces anger is among the most viral content,3 pages and clickbait websites competing for clicks over a too-long primary season were pushed further and further into promoting conspiracies. Eventually my friend was sharing anti–Hillary Clinton material, including some from a pro-Putin site—a site whose other articles were outlining the vast machinations of the Rothschild family and the Illuminati to take over the world.

Welcome to the World Wide Web, circa 2017.

I know I’m not the only person noticing this. If you’re online, you have seen this as well: formerly mild-mannered people engaging in mob behavior on Twitter; previously quiet and thoughtful people spreading conspiracy theories; originally tolerant people moving into ever smaller cocoons of thought. And at the center of this decline is the web as it has come to be.

Saving the Web

For as long as I have been in the educational technology field, pundits have asked whether the web can save higher education. There have been many waves of this discussion, from the early techno-utopianism of the 1990s to the recent fascination with MOOCs. In this line of thought, education is calcified, creaky, rusted. The web, on the other hand, is vibrant and agile, fueled by innovation and creative destruction. The idea is that if we could tap into the web’s vitality and innovation, we could “fix” education. We could make education work. Revitalize it. Optimize it. Disrupt it.

But what if the pundits have this backward? What if it’s actually the web that needs saving? And what if it’s higher education that is best suited to save it?

This is not as bizarre as it sounds. Vannevar Bush, whom most consider the grandfather of hypertext, drew his inspiration from academic culture, with its dense interweaving of cross-references and annotations. Ted Nelson, the person who first applied that vision to the digital computer, saw hypermedia as a method for modeling networks of agreement and disagreement in a way conversation could not, attempting to realize a design that modeled the understanding of experts. And the earliest users of both the Internet and the web were academics, who built a sharing and cooperative culture founded on the best traditions of a community of scholars.

As development of web technology moved from universities and research centers to Silicon Valley in the mid-1990s, progress and innovation accelerated. But as the financial model of the web formed around the twin pillars of advertising and monetization of personal data, things went awry. The social layer of the web provided by Web 2.0 products was a welcome addition to our shared networks, but the set of economic incentives underlying those products led us to the web we have today, with its pull-to-refresh addictions, clickbait conspiracy sites, and mob-like behavior.

Toward a Reflective Networked Future

With today’s web careening, Hindenberg-like, to the ground below, maybe, just maybe, it’s possible that our higher education institutions can save the web from its current trajectory. What would that look like? How could we do it?

First, we must put digital literacy at the core of the curriculum. We spend countless hours teaching our students to navigate the world of research and published books. And yet we graduate them into a world where the vast majority of the information they consume professionally and personally will come through the Internet. The literate culture of books and published articles is one of the great achievements of our culture; it is necessary to lifelong learning and must remain central to the education of our students. But it must be placed side-by-side with instruction on how to best use and critique the information environments that students inhabit on a daily basis.

Second, we need to provide the general population with access to better-quality information and just-in-time education. Initiatives around open access and open educational materials are important not only for reducing cost to students and researchers but for furthering public education as well. I have no illusions that these resources will be spread as widely as conspiracy clickbait, but for people trying to inject some sense into a conversation, they may provide a start.

These two elements—emphasizing digital literacy curriculum and providing citizen access to high-quality information—provide a start at stemming the damage in our current media environments. But it is the final element that is most crucial: we—the researchers, faculty, students, and staff of higher education—must design and model new ways of working on the web. I am not talking about a small set of bolt-on activities. I am not talking about adding one or two courses that use blogging or Facebook comments. I am talking about making, designing, and modeling the information environment of the future as our core educational mission, in ways that will radically transform what education looks like and will create a networked future capable of serving the common good.

What are some examples of this new way of working on the web? I do not have enough space here to outline such an agenda. Luckily, I have been given a chance to use the New Horizons column to show what that agenda looks like by inviting folks engaged with these issues to detail what their institutions and classes are actually doing to save the web. Over the next year, we will share that vision in this space. We hope you will follow along with us.

And if you’re reading this article online, it’s OK: you can share it now.

Join us for Mike Caulfield’s talk, “Teaching Digital Literacy in a Post-Truth World,” on March 15th at 4:00pm in the HCC Digital Auditorium! If you can’t make it in person, we’ll also be streaming the event live.

Notes

  1. Ted Greenwald, “How Facebook and Candy Crush Got You Hooked,” Wired, December 23, 2014.
  2. Maksym Gabielkov, Arthi Ramachandran, Augustin Chaintreau, and Arnaud Legout, “Social Clicks: What and Who Gets Read on Twitter?” ACM SIGMETRICS Performance Evaluation Review 44, no. 1 (June 2016), 179–192; Eli Pariser, The Filter Bubble: What the Internet Is Hiding from You (New York: Penguin Press, 2011); Caitlin Dewey, “Facebook Has Repeatedly Trended Fake News Since Firing Its Human Editors,” Washington Post, October 12, 2016.
  3. Matthew Shaer, “What Emotion Goes Viral the Fastest?” Smithsonian Magazine, April 2014.

This piece originally appeared in Educause Review. 

Image by Mariya Georgieva licensed CC-0

]]>
53989
Domain of One’s Own: A Corpus Study, Part 4 – Topic Model https://umwdtlt.com/domain-of-ones-own-a-corpus-study-part-4-topic-model/ Wed, 18 Jan 2017 15:00:33 +0000 http://umwdtlt.com/?p=53876 This is the fourth of four posts taking a deep data dive into a collection of over 300 articles written about Domain of One’s Own. Part 1 and Part 2 explored who has been writing about DoOO, the most common words and phrases used by those authors, and how the use of some terms change over time. Part 3 briefly explored a sentiment analysis of words and authors in the corpus. In this post, we take a look at emergent topics in the DoOO corpus.  All data, visualizations, and code for this project can be found in its repository on GitHub.

A common tool in text mining to uncover topics in more nuanced ways than individual words or n-grams is topic modeling. A topic model looks for words that tend to occur in the same documents with great frequency, but which are not typical of the entire corpus, thus providing a weighted list of words that tend to express a particular topic. It’s a helpful early-stage analytical tool to uncover pieces that explore the same topic, even if they use slightly different vocabularies.

Now this corpus is already united by a single topic: Domain of One’s Own. But while a topic model may not uncover radically different emphases in these pieces, it does uncover some subtleties that we might otherwise miss, and which are worth taking a closer look at.

Refining the model

One difficulty with topic modeling is choosing the number of topics to look for, as this is an input, not an output, of the analytical algorithm. Too small a number and the model doesn’t tease out the different topics well. Too large, and the distinctions are too fine to be useful. For example, here’s a 6-topic model of the DoOO corpus. (Each chart includes the 10 words most strongly associated with a topic, showing their weights or “beta” value. For more details on the math behind topic modeling, see Mark Steyvers’s “Probabilistic Topic Models” or David Blei’s “Introduction to Probabilistic Topic Models.”)

6-topic model of the DoOO corpus

These charts show the ten most distinct words of each topic found by the algorithmic analysis, as well as their weights for that topic (shown by the length of the bar). There are many of the same words in each topic, showing that the model is not distinguishing topics very well at this level. I tried a few other topic numbers and found, at least for the purposes of this study, that 16 topics seems to provide helpful distinctions.

16-topic model of the DoOO corpus

One obvious thing that jumps out here is Topic 3, which is clearly the result of a failure of the web scraper to strip the html tags from the post(s). There are topics tied to specific course experiences (like Topics 10 and 16). There are topics tied specifically to sysadmin work (like Topics 12 and 14). There are WordPress-/blogging-specific topics (like Topics 4 and 15). And there are general ed-tech-themed topics (like Topics 6 and 7). Here are the number of posts per topic.

Plot of number of posts per topic in DoOO 16-topic model

The issue with topic modeling in this corpus is that because the corpus is already centered around a single general topic, when we increase the number of topics to parse different (sub-)topics finely enough, we get a lot of overlap. That’s why many of the actual topics listed above correspond to multiple topics in the model. That said, we can still use these results to tease out articles related to these different topics, and to each other. (And to find the posts where the scraper unsuccessfully stripped the html code!) And we can use the topic model to find which authors tend to write about which topics, and which topics tend to be written about by which authors.

Heatmap of topics covered by authors

For instance, this visualization helps us see pretty quickly which topics are most popular, which authors are most prolific, and which topics and authors pair together. It doesn’t answer any major questions, but it can help guide us towards interesting patterns worth chasing down. For instance, one of Jim Groom’s most prominent topics is Topic 5, which is associated with APIs and student data more than, say, WordPress, DS106, or digital pedagogy. This also happens to be a pretty rare topic overall though, with posts by Marguerite McNeal and Chad Jardine being the only others to score highest for this topic. (Those posts are both centered on giving students control over their own data.) Why is this such a popular topic for Jim but not overall? And why are Marguerite’s and Chad’s posts the only other ones to get binned in this topic?

My attention is also drawn to Topic 10, a very small topic with articles only by Jim Groom and Jeremy Dean. Since this looked initially like a DS106-heavy topic (and thus one I would assume to be limited to UMW authors), Jeremy’s inclusion here stands out. I’m not sure exactly why, but it’s grabbed my attention, and I want to take a closer look. (That’s exactly what a topic model is good for: directing attention to things worth a closer look.)

It turns out that while Topic 10’s top words are very DS106-centric, when we look further down the list, we can see that it’s really more of a pedagogical topic, one that focuses on the cultivation of community, often in a class. And that’s largely what Jeremy’s post is about ― how to use WordPress and hypothes.is on DoOO to help cultivate a community of collaboration among students. (It’s also worth noting that because Jeremy’s post has a fair bit of how-to about it, the topic to which this model assigns it the second greatest weight is Topic 4 ― another rare one, and the one dominated by Tim Owens’s more technical explanations of DoOO.)

Conclusion

These are just some of the cool things we can do with the data from this corpus of articles about Domain of One’s Own. Thanks to Lee who assembled the list! And, of course, to everyone who wrote these insightful pieces! Feel free to visit the GitHub repository and play around with it yourself. Maybe you’ll find something cool that I didn’t. 🙂 And look out for Lee’s upcoming pieces in which she follows up on my quantitative “distant reading” with a few qualitative, “close” readings of her own.

Featured image by Bernard Spragg.

]]>
53876
Domain of One’s Own: A Corpus Study, Part 3 – Sentiment Analysis https://umwdtlt.com/domain-of-ones-own-a-corpus-study-part-3-sentiment-analysis/ Tue, 17 Jan 2017 14:52:58 +0000 http://umwdtlt.com/?p=53869 This is the third of four posts taking a deep data dive into a collection of over 300 articles written about Domain of One’s Own. Part 1 and Part 2 explored who has been writing about DoOO, the most common words and phrases used by those authors, and how the use of some terms change over time. Part 4 will be published Thursday, exploring emergent topics in the DoOO corpus. In this post, we briefly explore a sentiment analysis of words and authors in the corpus. All data, visualizations, and code for this project can be found in its repository on GitHub.

How do people feel about Domain of One’s Own? Well, sentiment analysis is a tricky aspect of natural language processing. It requires a lot of nuance (and coding) to fully account for context when determining sentiment algorithmically. But we can have some fun looking at rough estimates, as long as we take it with a grain of salt.

For this sentiment analysis, I’m going to use a common sentiment lexicon developed by Bing Liu, et al. that tags a subset of English words as either positive or negative and make article-level and author-level classifications by simply counting the relative proportion of positive and negative words. There are problems with using such a simple approach: words have different sentiments according to context, the algorithm will count “not happy about” as a positive sentiment because of the word “happy,” etc. But it can give us some rough and interesting results to play with and, if so desired, to prompt a closer reading of some texts in the corpus to gain insights we otherwise might have missed.

To start with, here’s a chart of the sentiment analysis of each piece in the corpus (linked rather than embedded, due to its size).

Somewhat more interesting is this chart of the overall sentiment of the works of each author in the corpus (normalized for each author’s individual word count).

Sentiment analysis by author, normalized for author word count

In my opinion, this doesn’t give us much interesting and useful information without looking at specific pieces, but it could prompt us to look at some things more closely. For example, only three authors have a net-negative sentiment. Is this characteristic of their writing in general? something specific about the piece(s) in question? a problem with the method of calculating sentiment? All of the above?

Somewhat more useful (and enlightening when attempting to answer those previous questions) is an analysis of which words in the corpus tend to lead to positive and negative sentiment results. Here is a word cloud of the most common positive- and negative-tagged words in the DoOO corpus.

Word cloud of most common sentiment-tagged words in DoOO corpus

A few things immediately stand out to me. First, the word reclaim jumps out as the most prominent positive-tagged word in the corpus. Not surprising given the fact that the two most prolific authors are the co-founders of Reclaim Hosting and that many institutions use Reclaim to power their DoOO program, but striking nonetheless. What also jumps out to me are the number of negative-tagged words that are likely positive or neutral in this corpus: cloud, issue(s), critical, disruptive, disruption, impossible (maybe?), rhetoric (!), breaking (maybe?), fall (probably the season), and punk. So maybe those net-negative articles use these terms a lot? It’s also easy to see the enthusiasm surrounding DoOO in this corpus by looking at words like awesome, love, brilliant, excellent, etc. in this sentiment word cloud.

Again, this kind of sentiment analysis doesn’t give us a lot of nuanced insight on its own, but it can give us some directions we might want to look for a more detailed analysis in the future. Stay tuned for the final installment of this corpus study on Thursday, in which I walk through a topic analysis of the DoOO corpus.

Featured image by chivosol.

]]>
53869
Domain of One’s Own: A Corpus Study, Part 2 – Bigrams and Changing Trends https://umwdtlt.com/domain-of-ones-own-a-corpus-study-part-2-bigrams-and-changing-trends/ Thu, 12 Jan 2017 15:00:40 +0000 http://umwdtlt.com/?p=53804 This is the second of four posts taking a deep data dive into a collection of over 300 articles written about Domain of One’s Own. Part 1 explored who has been writing about DoOO and the most common words used by those authors. In this post, we look at two-word phrases, institutional references, and how the use of some terms change over time. Parts 3 and 4 will be published next week and will explore sentiment and emergent topics in the DoOO corpus. All data, visualizations, and code for this project can be found in its repository on GitHub.

Single words can tell us a lot, but n-grams (phrases of n length) can help us tease out more details. Just what are we “syndicating”? What kind of “bottlenecks” or “standards” are people writing about? And are every “Jim” and “Tim” in the corpus really Jim Groom and Tim Owens?

Here are the top bigrams in the corpus.

DoOO stats visualization: most common bigrams

There’s understandably a heavy UMW focus at the top of the list, given that UMW authors occupy three of the top four spots on the most prolific authors list. So let’s split UMW authors (again, this will be mostly Jim Groom’s posts) and non-UMW authors. Here are UMW authors:

DoOO stats visualization: most common bigrams from UMW authors

And here are non-UMW authors:

DoOO stats visualization: most common bigrams from non-UMW authors

As before, we can see differences more clearly and starkly using a two-dimensional visualization. (Click on the image to explore the high-resolution visualization.)

DoOO stats visualization: comparing bigram frequency from UMW and non-UMW authors

In this plot, we can see that both UMW and non-UMW authors refer to key things like Reclaim Hosting, digital identity, and online presence with relatively equal frequency. One key difference involves the names of people found in each corpus. UMW authors are much more likely to refer to important figures in the history of DoOO and DS106 like Martha Burtis, Tim Owens, Ryan Brazell, and Alan Levine. Non-UMW authors are more likely to write about Jim Groom (who wrote most of the UMW corpus), and to refer to institutions like UMW, Emory, OU, and Davidson.

It’s also interesting to note, again, how much more the non-UMW corpus focuses on bureaucratic elements like learning analytics, and general topics like learning environment, learning management, digital learning, digital humanities, and educational technology (though the short form ed tech is more prominent in the UMW corpus). I think this is most likely because of how many of the UMW corpus posts describe the specifics of building DoOO ― both the technical infrastructure and the people doing the work. But teasing that out would require a deeper look at specific articles.

Another key difference is in the relative frequency of personal and institutional names. UMW Blogs is more prominent in the UMW corpus, while Davidson Domains, Emory University, and OU Create are more prominent in writings from those outside UMW. However, I’m suspicious that this has less to do with who’s writing and more to do with when they are writing. Most of the UMW corpus was written by Jim Groom during, and even before, the pilot of DoOO at UMW, before the DoOO incubator session in Atlanta, before OU received funding for a major rolling out of DoOO on their campus, etc.

DoOO stats visualization: dates when UMW and non-UMW content was written

As shown in this figure (based on word counts over time), the non-UMW corpus begins in late 2012, right about at the first quartile for the UMW corpus (meaning 25% of the UMW content had already been published). The first quartile and median of the non-UMW corpus match up with the median and third quartile (75th percentile) of the UMW corpus respectively. So it makes sense that things more prominent in the UMW corpus may simply be published earlier, and vice versa. Is that the case for these terms?

Let’s look at institution names. Here is the month-by-month relative frequency of occurrence for various institutional names in the whole corpus.

DoOO stats visualization: mentions of institutions over time

And here is the same just for UMW authors.

DoOO stats visualization: occurrence of institution names over time, UMW authors

And for non-UMW authors.

DoOO stats visualization: occurrence of institution names, non-UMW authors

While UMW is discussed more by UMW authors, and Oklahoma in particular is discussed less by UMW authors, the peaks for most institutional words tend to line up. And the highest peak for mentions of Emory in this corpus comes from the UMW corpus before the earliest non-UMW article. So it seems the difference in frequency of different institutional names between UMW and non-UMW authors can largely be attributed to when the piece was written.

Another interesting change over time has to do with the names of the various platforms institutions use. A number of programs ― like UMW, Emory, and Davidson ― tend to call their program Domain of One’s Own or [Institution] Domains. It seems that more recently, there has been a rise in programs (like OU and Middlebury) using create rather than domains in their title. And then there’s the use of the word reclaim, which like create is both the name of a platform (Reclaim Hosting) used by many institutions and a verb describing what students and faculty do with DoOO (reclaim your domain/space/digital identity/etc.). How does this pan out over time?

DoOO stats visualization: usage of create and reclaim over time

Once reclaim enters the corpus in 2013 (the year Reclaim Hosting was founded, and also the year that DoOO rolled out to the whole campus at UMW), it maintains a pretty steady presence. Interestingly, though, create drops at right about the same time as reclaim enters. Is there a conscious reworking of the narrative going on here, with the notion of doing creative work on the web shifting towards reclaiming ownership of our own space on the web? Or is this just an apparent shift in the whole corpus that’s really simply a shift of the two most prolific authors in the corpus as they begin work on their startup?

Well, here’s the same plot, limited to posts by Reclaim Hosting founders Jim Groom and Tim Owens.

DoOO stats visualization: reclaim vs create, Jim Groom and Tim Owens

The familiar dip in create as reclaim enters the corpus is clear. Now here is the rest of the corpus.

DoOO stats visualization: create vs reclaim, no Jim Groom or Tim Owens

There is no dip in create when reclaim enters the corpus! So it was just Jim and Tim. (Investigating why that dip happens would be an interesting “close reading” follow-up to this “distant reading” project.) There are some rather obvious spikes in this non-Jim-and-Tim corpus worth noting: a spike in reclaim roughly when the word (and the hosting startup) enters the scene, and a spike in create in late 2015, right about the time that OU Create went campus-wide.

Again, these are just a few of the insights and patterns that we can find from this data. If you find this interesting, be sure to stay tuned for Parts 3 and 4 next week, which will unpack a sentiment analysis and a topic model of these articles. And, of course, you can always download the data and code from GitHub if you want to take a closer look yourself and chase down other patterns in the data.

Featured image by Runs With Scissors (CC BY-NC-ND).

]]>
53804
Domain of One’s Own: A Corpus Study, Part 1 – Words and Voices https://umwdtlt.com/domain-of-ones-own-a-corpus-study-part-1-words-and-voices/ Tue, 10 Jan 2017 15:00:36 +0000 http://umwdtlt.com/?p=53787 This is the first of four posts taking a deep data dive into a collection of over 300 articles written about Domain of One’s Own. In this post, we’ll explore who has been writing about DoOO and what kind of vocabulary is used to describe the program. Part 2 explores the most common phrases used by those authors, and how the use of some terms change over time. Part 3 briefly explores a sentiment analysis of words and authors in the corpus. Part 4 takes a look at emergent topics in the DoOO corpus.  All data, visualizations, and code for this project can be found in its repository on GitHub.

What do people talk about when they talk about Domain of One’s Own? Which voices are most prominent? How has the conversation shifted over time? What’s missing from the conversation?

Over the past couple months, my colleagues and I have been exploring the history of Domain of One’s Own, here at UMW and elsewhere. As part of that effort, Lee Skallerup Bessette curated a list of over 300 articles and blog posts about Domain of One’s Own. This list includes the blogs of current and former UMW faculty and staff, faculty and staff at institutions with similar programs, and even a few articles from the mainstream media. So in my emerging role as the office data wrangler, I wrote a few scripts that take Lee’s list of articles, scrape the web for the content of those articles, clean and transform that data, and then analyze it, looking for emergent patterns that we might not have otherwise found. This is the first in a series of four posts in which I’ll walk through some of the more important and interesting findings from that corpus analysis.

All the code behind the visualizations and stats in this post can be found in the project GitHub repository. Web scraping is done in Python. Statistical analysis and visualization is done in R using tools from the TidyVerse.

Who’s talking about Domain of One’s Own?

We make no claims that our list of articles is complete, but Lee spent a lot of time diving deep down rabbit holes to assemble what seems to me to be a fairly comprehensive and representative list of pieces about DoOO. So let’s see what’s included.

Here are the most prolific authors, by word count, in the corpus. All authors shown here have contributed at least 500 words to the corpus.

DoOO stats visualization: number of words per author

Not surprisingly, Jim Groom has written a lot about Domain of One’s Own! Let’s take him out of the mix temporarily, so we can get a better look at the rest of the list.

DoOO stats visualization: words per author, no Jim Groom

Now we can see that Tim Owens (another former DTLTer and Jim’s co-founder at ed-tech startup, Reclaim Hosting) and Audrey Watters (one of the most important critical voices in ed-tech and a guest at UMW later this spring, where she’ll speak and lead a design sprint on activist ed-tech) have said a lot about DoOO. Martha Burtis (director of the Digital Knowledge Center at UMW, former director of DTLT, and co-conspirator with Jim and Tim in the early days of DoOO and UMW Blogs) and Michael Feldstein (educational technologist and co-publisher of e-Literate) occupy the next tier. After that, a number of familiar voices follow in a “long tail” of diminishing word counts. For the most part, the authors outside of the top five have written a single piece or two short pieces, while the top five have each written multiple pieces and/or delivered a keynote address on DoOO, hence the tiered drop-offs.

It’s not particularly surprising to me to see three key figures from DTLT’s past in the top four, with the two who left DTLT to pursue their work at Reclaim Hosting full time occupying the top two spots. However, Jim’s dominance of the corpus (over 70% of the total words!) will require some care in the following analyses, so we don’t accidentally attribute trends in Jim’s writing to the community as a whole.

What are people saying about Domain of One’s Own?

Let’s take a look at the vocabulary people are using as they discuss DoOO. Here are the most common words in the corpus (stop words removed).

DoOO stats visualization: most common words

It’s not surprising that words like domain, web, students, faculty, learning, umw, digital and the like round out the top. It’s also not surprising that WordPress shows up, as it’s the most common app installed in DoOO hosting accounts. (It’s also the only app used as part of UMW Blogs, so it was the easiest way for our students and faculty to transition from UMW Blogs to UMW Domains.) It’s also probably not surprising, though worth noting, that reclaim is a common word in this corpus, used both as a proper name (Reclaim Hosting) and as a verb (“reclaim your domain!”). Let’s flag this word for when we explore changes over time…

This list is just a raw count, however, meaning that it is 70% based on Jim Groom’s blog posts. So does this just represent Jim’s way of describing DoOO, or is it a more general trend?

Here are the top words in Jim’s corpus.

DoOO stats visualization: Jim Groom's most common words

And here are the top words in the rest of the corpus.

DoOO stats visualization: Most common words in non-Jim_groom corpus

There are a few subtle differences. For example, Jim seems to talk about UMW more than others. And while Jim talks more about back-end technical topics (domain, web, hosting, etc.) with domain being the most common term, the rest of the corpus seems to emphasize the bureaucratic (university) and the pedagogical (students, education, learning), with students being the most common term. That’s not at all to say that Jim has nothing to say about pedagogy (see the prominence of DS106 in his corpus, the course he co-taught with Martha Burtis and others in which they first experimented with giving students domains at UMW). But he does seem to write about the technical aspects of building DoOO more than others, understandable as he was instrumental in building it at UMW, and doubly understandable as he, Tim, and the Reclaim Hosting team manage much of the back-end for the universities they work with. Also, keep in mind that this is a single-word analysis, not a topic model (that’s coming in Part 4).

I also find it interesting that the word reclaim shows up more prominently in Jim’s corpus, while the word create (the name of the DoOO-like program at an increasing number of schools, like Oklahoma University and Middlebury College) is more prominent in the rest of the corpus. But since I’m suspicious that this dynamic may have changed over time, let’s flag that for further investigation, too…

These kind of comparative studies can get tedious when looking at two sets of word rankings. So let’s use another visualization tool that makes the differences much more stark. The following graphic maps word frequency in two dimensions, with the Y axis representing the probability that a given word will occur in Jim’s posts and the X axis representing the probability that that word will occur in the rest of the corpus. The diagonal line represents equal probability. Words close to the line occur with similar frequency in Jim’s writing and the rest of the corpus. Words towards the upper left are more uniquely characteristic of Jim’s writing, while words towards the bottom right are more uniquely characteristic of the rest of the corpus. (Note this is a very high-resolution image, so you’ll want to click on it to open it full-size.)

DoOO stats visualization: comparing the word frequency in writings by Jim Groom and the rest of the corpus

From this graph, we can see that Jim is a pretty positive guy! Words like awesome, amazing, brilliant, and cool sit far to his side of the line. Others seem more concerned with university bureaucracy than Jim, with words like standards, bottlenecks, program, administrative, academia, and adoption sitting far to the non-Jim side of the line. Jim also talks more about DS106 than others (which makes sense) as well as (now former) UMW employees who have played a significant role in DS106 (Alan (Levine)) and DoOO (Tim (Owens)). There’s also more about pedagogy and education on the non-Jim side, and more about distributed content that is aggregating and syndicating (big ideas in open-source and “IndieWeb” publishing) on Jim’s side. (Note that which words pop up on the graph is somewhat random. In previous iterations of this graphic, words like Martha (Burtis), (Jeff) McClurken, punk, and indie show up on Jim’s side, further emphasizing both Jim’s aesthetic and the role that other UMW staffers like Martha and Jeff have played in the history of DoOO.)

Another word worth following up on is Woolf, which sits pretty far to the right of the line. The name, Domain of One’s Own, is a reference to Virginia Woolf’s A Room of One’s Own, and that connection with feminist history is important to a program like DoOO. Not only is DoOO meant to empower students in new ways, especially as writers ― or media creators more generally ― but DoOO was founded at Mary Washington, a historically womens’ college where more than two-thirds of the students are women.

So I looked up who uses the word Woolf in this corpus. There are five authors: Debra Schleef (12 times in her piece “Who’s Afraid of Domain of One’s Own”), Audrey Watters (6 times over several pieces), Martha Burtis (5 times in “Coding, Serendipity, and Domain of One’s Own”), Jim Groom (3 times over two pieces), and Jon Udell (1 time in his WIRED piece, “A Domain of One’s Own”).

So while it looks on this visualization like Jim uses it less than the rest of the corpus, that’s just because it’s an infrequent word. In fact, only three people use the term more than him, and 20 out of 27 uses of Woolf come from UMW folks, which seems fitting given the history of DoOO here. That said, there a notable duality to the way of One’s Own is used ― both connecting to feminist ideology and expressing an “indie” feel. But that duality should be unpacked at length and with great nuance, not as an aside in this post.

DoOO stats visualization: Comparing word frequency in writings by UMW authors and non-UMW authors

When we compare UMW authors to non-UMW authors, the results only change slightly (the UMW authors category is still dominated in raw word count by Jim Groom). But a couple interesting changes emerge. Largely due to the inclusion of Martha Burtis along with Jim Groom in the UMW corpus, the term DS106 becomes the most uniquely UMW term in the corpus. DTLT also rises in prominence, and the importance of syndication among UMW authors (a common faculty request at UMW when assigning domain work to their students) is marked as well. Institutional bureaucracy still stays prominent on the other side of the line. (Perhaps why I love working here so much?!)

This is just the beginning of what data analysis of this corpus can tell us about Domain of One’s Own and how it’s being used in various institutions. In the next post in this series, I’ll walk through two-word phrases, institutions mentioned, and how the usage of some terms change over time. Then in Part 3, I’ll unpack some sentiment analysis of text in this corpus, followed by a topic model of this corpus in Part 4. So stay tuned for more! And if you just can’t wait, take a look at the GitHub repository, where you can download data and code and play around with it yourself…

Update: If you’ve written something about Domain of One’s Own and would like to add it to our corpus, please email me at kshaffer@umw.edu. We’ll publish a follow-up study with the expanded corpus.

Featured image by Marcin Ignac (CC BY-NC-ND).

]]>
53787