ADVERTISEMENT



Google       

Home -> Law Blog Directory -> Legal Commentary Blogs -> Prawfs

OR PHONE (866) 635-1838 for Bankruptcy Help, (866) 635-6190 for Divorce,
(866) 635-2689 for Personal Injury or (866) 635-9402 for Criminal Defense

Find a Local Lawyer

Bankruptcy (866) 635-1838
Divorce (866) 635-6190
Personal Injury (866) 635-2689
Criminal Defense (866) 635-9402

Bookmark

Legal Commentary

: Prawfs

Co-authorship & Tenure Regs

By Dan Markel, Ethan Leib, Rick Garnett, Matt Bodie, Paul Horwitz , Steve Vladeck, and Orly Lobel

ADVERTISEMENTS

Hastings has what I take to be an antiquated regulation about co-authorship in its tenure standards:

"Co-authored works will be considered to the extent that the candidate's contribution can be separately evaluated."

I can only guess that this kind of thinking came out of an age where casebook authors assigned one another separate chapters that could be sent out for review individually.  But this regulation is clearly out of date, in my humble opinion.  Thankfully, we're about to revisit the issue and I would be very curious about what modern standards look like on the question of co-authorship.  And if you were writing tenure standards anew, how would you  handle the issue? 

Full post as published by Prawfs on August 27, 2008 (boomark / email).

Bloggers, promote your law blog by nominating your blog for inclusion in USLaw.com's Law Blog Directory and RSS Reader. Benefits described.
Related Searches

























































































































US Law
#1 Online Legal Resource













Your Blog Subscriptions
Subscribe to blogs

10,000+ Law Job Listings
Lawyer . Police . Paralegal . Etc
Earn a law-related degree
Are you the author of this blog? Adding USLaw.com to your Blogroll increases relevance. You qualify to display a USLaw Network badge.
Suggest changes to this blog's description or nominate another for inclusion. Register for updates.


Practice Area
Zip Code:

Contact a Lawyer Now!






0.0203 secs (new cache)