A couple of the issues facing teachers using web-based writing technologies (which they might not be thinking about) are student data and student IP when using third-party apps. Who hasn't used Blogger? But who has read the click-thru agreement to see who owns the information students save on Blogger servers? Do you have a Facebook clause telling students they shouldn't be using their real names on your publicly viewable course website or their blogs? Raise your hand if you've ever had a student used their name for part of their Blogger blog. And what about telling them not to post other info that might come back to bite them in the @$$ when they apply for jobs after graduation? Have you thought about who owns the data you and your students generate on your hosted site?
These were some of the issues I discussed with one representative from DoIT and one from Legal Services yesterday morning. It's a conversation I've been wanting to have for a long time, but, heck, I'm just a TA, why has it come down to me? In part, it's because I'm always talking to folks looking for better technological solutions for the teaching I do. But mostly, this is the result of the Engage project I'm working on with Scot and Annette (they would have been there, too, but they had to teach during this time) which asks students to write publicly. Yet, other folks get paid for these sorts of things, and I don't. I've got a dissertation to write, ya know.
Anyway, the fact that many, many instructors on campuses across the U.S. are using third-party apps and hosting isn't news to anyone reading this blog or legal services on your campus.
From the legal side, they're aware of this use. 3rd-party apps are convenient, usually designed better or include design features not available thru the campus options. For me, they enable students to write in public, anonymously, and (simulate) technological and social experiences happening every day on the Web. But what are the risks, and what risks have instructors thought about? Could you be sued? Did you know that you probably are not protected/covered by the University if you are sued?
Basically, legal isn't aware of what exactly we're doing, and they are concerned. And the purpose of this meeting was to discuss what instructors are doing and thinking and what, if any, policies and education should be established to support instructors.
A couple posibilities (feel free to sugget others).
Legal, in conjnction with DoIT:
- reads click-through agreements of popular hosts, e.g., Blogger, WetPaint wikis, and Google groups, and generates a hierarchical list of hosts that make few or no IP claims on student work
- sets policies/best practices for protecting students data and identities
- creates a way to educate instructors about using third-party apps
As far as the third bullet goes, my suggestion is to train grad students to train everyone else. This was part of the mission of Technology Fellows in the English department. Each year a group of grad students was selected to learn more about teaching with technology and then disseminate this knowledge throughout the department to professors and TAs. It worked, somewhat. But the need to educate instructors on an institutional level might call for an interdisciplinary Tech Fellows program and revitalize a victim of budget cuts when couched in legal terms.
Recent Comments