Scholarship of the XXIst century will include a lot of research on teaching, learning, and citizen science. MOOCs offer fantastic opportunities in this area. The XXIst century should also probably include scholarship of its own labor practices, or at least some concerted effort to stay afloat of developments in the profession. Asymmetric information can hurt badly in negociations. For this reason, it could be helpful to gather all Coursera Framework Agreements that have landed on the internet (so far) in one place. Those agreements bind the university administration and Coursera, and package within them the actual contract to be signed later by the instructor (and guests), both with the administration and with Coursera. On top, any user of Coursera requires an account which is bound by its own Terms of Service .
By simply googling around (mostly for Coursera Framework Agreement), I was able to find the following eight contracts:
- U Colorado
- U Kentucky
- University of Michigan
- University of Roma (Sapienza)
- University of Stony Brook
- UC Santa Cruz
- University of North Carolina
- University of Toronto
- bonus, found later: University of Maryland
Not all of those are signed, some are just preliminary and might not match the final version. Some of those were originally obtained through Freedom of Information requests, while others were obviously misplaced. Some seem to have been removed from the web since, so I put them back here. The more interesting aspects here are the subtle variations between these contracts.
Should you have one that you want to share, feel free to send it to me.
I also include the following Course Development Agreement for UNC. This contract is packaged within the Framework Agreement, and one is signed for each course at UNC, according to the CFA. It is relatively short, but refers to external guidelines located on the Coursera Partner Portal (i.e. online, inaccessible without an account with different permissions than a regular student account).
It includes the rollout policy for a particular course: 1.d.i and 1.d.ii dictate that the content should be uploaded one month ahead of the course start for the first week of content, and two weeks ahead for the second week, but "[these] will not apply to the University Courses beginning in the Fall of 2013 if the achievement of these requirements is not practical or not feasible". UNC joined Coursera on February 2013.
The CDA also includes the following:
- Course reusability: Ensuring that the content can be easily reused in subsequent offerings of the course for which the instructor might not be involved. This includes:
a. Avoiding references to particular dates in lecture videos (e.g., "The homework will be due next Monday, March 4" or "It’s a beautiful summer day today");
b. After the first offering of the course, systematically editing/removing references to dates and episodes that are specific to the first offering of the course (e.g., an announcement about correcting a typo on the final exam, or about extending due dates because of Hurricane Sandy), as well as references to activities for which instructor involvement is necessary (e.g., "We hope to see you at the next live Google+ Hangout").
—Coursera Development Agreement, to be signed by Coursera instructors at UNC (emphasis mine)
I have read through quite a lot of this, so if you have any question feel free to ask!
|||As indicated by Jonathan Mayer, since this is what gave him sufficient credentials to potentially dump the Coursera database of 9M students' names and emails.|