It has been a wild few months and it feels like there are a lot of things happening at once.

I’m thrilled that at St. Norbert we have gotten our Domains project off of the ground and I’m talking about and working with domains more than ever – which is wonderful.

However, a few months ago after attending DigPed Lab, those of you who follow regularly will recall, I had some serious questions about how to design for privacy and security with DoOO.

I had some great collaboration around this from comments on the post to backchannel conversations about what all is out there. I would be remiss if I did not particularly give a shout out to Tim C from Muhlenberg College and Evelyn Helminen from Middlebury College who gave me lots of feedback and resources. And of course to Chris G who just keeps me thinking about privacy in edtech in general.

I’d had some visions of pulling together a group who is interested in this topic but I found that things just moved too quick for me and I was in need of a resource that I could give to students before I could pull the group together. So, still working on that – if you have a particular need for this please put a fire under me.

I’ve struggled with this topic because it is such a nuanced thing. I love DoOO because of the focus on student ownership and agency. Privacy can be addressed with blanket best-practices but that is not the conversation that I’m interests me.

I feel our domains project at SNC is particularly blessed in that we have our Tech Bar. We visited University of Mary Washington in building it and got a lot of tips from Martha Burtis and the students who work at the Digital Knowledge Center. I’m telling you all of this because I think it is important to contextualize this resource that I’ve built for students.

This first little resource around privacy and security with DoOO that I’ve built is directed at students and is really just meant to give them a taste of what is possible around naming, making pages private, securing sites, etc. I created a little infographic around this and at SNC I printed them up as large bookmarks. The SNC version clearly says that a student can visit the Tech Bar for more information.

I made a more generic version of the resource and slapped an open license on it in case it might be helpful for others with DoOO projects. I’m hoping to think about this more, collaborate with others, and have more thoughts on this as we move forward.

Download link

On a somewhat related note I do want to draw attention to our most recent DigCiz call for engagement which is a parallel project to an interactive presentation that we will give at EDUCAUSE Annual Conference.  The call for engagement and the presentation basically ask the question “What do we owe students when we collect their data?”. To participate in the call just blog or tweet (Nate Angell even started a hypothes.is annotation of the post). To participate in the presentation come to the EDUCAUSE Annual conference presentation or participate in the twitter chat. All details on the post.