<html>
<body>
Hi Kevin,<br><br>
That is the part of the submission license I was referring to, but our
wording doesn't include the<br>
indemnification at the end. <br><br>
<font face="Courier New, Courier">You might want to consider some
usability tests of the license<br>
since we're finding that these submission licenses can scare off <br>
contributions from faculty who don't really know what their rights<br>
are, or whether they have copyright or not. A topic for much future<br>
discussion, no doubt.<br><br>
MacKenzie<br><br>
</font>At 11:23 AM 10/29/2004 -0500, Petsche, Kevin F wrote:<br>
<blockquote type=cite class=cite cite><font face="arial" size=2>MacKenzie,<br>
</font><br>
<font face="arial" size=2>Your post to the General DSpace listserv on
June 4 (see it below my signature file) of this year addresses the exact
issue with which we are addressing right now. You say that the
default submission license deals with the situation where a person is
submitting items for the author or creator. <br>
</font><br>
<font face="arial" size=2>We changed the default license so that it
reflects our campus (i.e. IUPUI) and I just want to be sure that the
language you are referring to is:<br>
</font><br>
<pre><font face="Courier New, Courier" size=2>If the submission contains
material for which you do not hold copyright, you represent that you have
obtained the permission of the copyright owner to grant to IUPUI the
rights required by this license, and that such third-party owned material
is clearly identified and acknowledged within the text or content of the
submission. You agree to hold IUPUI harmless in the event of any
violation.
</font></pre><font face="Courier New, Courier"></font><br>
<font face="arial" size=2>Thanks in advance for your confirmation of this
(and/or clarification),<br><br>
</font><br>
<font face="arial" size=2 color="#000080">Kevin Petsche<br>
Electronic Journals Collection Manager<br>
IUPUI University Library<br>
UL1115K<br>
755 W. Michigan Street<br>
Indianapolis, IN 46202-5196<br>
317.278.2330 (Office)<br>
317.278.0368 (Fax)<br>
kpetsche@iupui.edu<br>
</font><font face="arial" size=2> <br>
</font><br>
<pre><font face="Courier New, Courier" size=2>Hi
Merle,</font></pre><font face="Courier New, Courier"></font><br>
<pre><font face="Courier New, Courier" size=2>At MIT we do not produce a
paper copy of the submission license (signed or
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>otherwise) -- I
think that would be extremely impractical for the volume of
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>submissions we get.
The default license does cover the case where the
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>submitter is not the
author, requiring that they (the submitter) have the
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>authority to approve
the license on behalf of the author (whether the
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>submitter is a
department's admin assistant submitting a paper on behalf of
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>a faculty member, or
whether the submitter is a faculty member submitting a
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>paper she
co-authored with others,
etc.)</font></pre><font face="Courier New, Courier"></font><br>
<pre><font face="Courier New, Courier" size=2>We have a verbal agreement
with new Communities when they join, but do not
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>require them to sign
a legal MOU (as does, for example, the CDL
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>eScholarship
repository). Some institutions will definitely want to
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>consider a legal
agreement with Communities, but we felt it was too much
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>here, and would
frighten off potential Communities
unnecessarily.</font></pre><font face="Courier New, Courier"><br><br>
</font><pre><font face="Courier New, Courier" size=2>We're also in the
process of adding support to DSpace for (optional)
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>Creative Commons
licenses (US version) which would cover the end-user
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>rights to use the
content -- yet another twist on the copyright and
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>licensing
maze!</font></pre><font face="Courier New, Courier"></font><br>
<pre><font face="Courier New, Courier" size=2>This is murky legal
territory, and there is risk involved, but we hope to
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>use this opportunity
to educate ourselves and our faculty about what our
</font></pre><font face="Courier New, Courier"><br>
</font><pre><font face="Courier New, Courier" size=2>options really
are.</font></pre><font face="Courier New, Courier"></font>____________<br>
Dspace-general mailing list<br>
Dspace-general@mit.edu<br>
<a href="http://mailman.mit.edu/mailman/listinfo/dspace-general" eudora="autourl">http://mailman.mit.edu/mailman/listinfo/dspace-general</a></blockquote>
<x-sigsep><p></x-sigsep>
MacKenzie Smith<br>
Associate Director for Technology<br>
MIT Libraries<br>
Building 14S-308<br>
77 Massachusetts Avenue<br>
Cambridge, MA 02139<br>
(617)253-8184<br>
kenzie@mit.edu</body>
</html>