Thursday, February 2, 2017

DMCA Takedown Request of Open Source Calculus Book, ha!

Many of you may know that I work at Whitman College and David Guichard, author of the widely used open-source calculus textbook aptly named "Single Variable Calculus", is in my department (in the office right next door).

Not surprisingly, many of us in the dept here use this textbook. Hence, a pdf copy of the textbook sits on one of our dept webservers (https://www.whitman.edu/mathematics/calculus/calculus.pdf). 

A couple of days ago Whitman's tech support folks received a DMCA takedown request from Cengage (a commercial textbook operation) for this pdf file. Lest there be any doubt, Cengage does not own the rights to this text. Indeed, on page 2 of the pdf one can view clearly the creative commons license governing the use of this text. Fortunately, our tech services folks have a good sense of humor and told Cengage to "eff off!"

I'd love to post the actual takedown notice, but (surprise!) the fine print at the bottom of the notice prohibits that. It's too bad that these copyright trolling outfits aren't liable for the time and energy consumed by false claims of infringement.

I'd be interested in knowing if other authors of open-source texts have run into this issue.

3 comments:

  1. I've seen something like that (I work for the fed govt so my math writings are in the public domain). I wonder if you can do this: as a matter of *satire*, is post the DMCA notice and claim (as a joke) *you* wrote that, and that they have to takedown the takedown notice?

    ReplyDelete
  2. Luckily I have not had to deal with this yet. However, you mention it is too bad that there is nothing that can be done? As far as I know, there IS something that can be done. From what I've seen on legal blogs (for example http://blogs.lawyers.com/attorney/intellectual-property/consequences-of-filing-a-false-dmca-takedown-request-10363/, but IANAL), DMCA takedown requests are done under penalty of purjury. So Cengage could face civil or even criminal penalties for sending this clearly false takedown notice. I'm not saying this is worth pursuing, but if the problem persists, maybe?

    ReplyDelete
  3. I've never had this.

    But isn't it the case that this is all automated, that you got a document from a bot?

    ReplyDelete