<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" 
   xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" 
   xmlns:html="http://www.w3.org/1999/html" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
<channel>
   <title>Mast Kalandar</title>
   <link>http://www.imsc.res.in/~kapil/blog</link>
   <description>bandar's colander of random jamun aur aam</description>
   <language>en</language>
   <copyright>Copyright 2008 Kapil Hari Paranjape</copyright>
   <ttl>60</ttl>
   <pubDate>Sun, 13 Jul 2008 01:38 GMT</pubDate>
   <managingEditor>kapil@imsc.res.in</managingEditor>
   <generator>PyBlosxom http://pyblosxom.sourceforge.net/ 1.3.2 2/13/2006</generator>
<item>
   <title>Balaram on Institutional Archives</title>
   <guid isPermaLink="false">publishing/balaram_on_open_archives-2008-07-13-07-08</guid>
   <link>http://www.imsc.res.in/~kapil/blog/publishing/balaram_on_open_archives-2008-07-13-07-08.html</link>
   <description><![CDATA[

  <p>Subbiah Arunachalam forwarded a <a href=
  "http://www.scidev.net/en/features/q-a-open-archives-the-alternative-to-open-access.html">
  link</a> to an interview of Professor P. Balaram regarding Open
  Archives. (Balaram is currently the director of the Indian
  Institute of Science, Bangalore so he is in a position to
  influence national policy in such matters).</p>

  <p>I broadly agreed with his views and I posted a comment which I
  am reproducing here. Primarily, there <em>are</em> differences
  between different disciplines. The quotes below are from the
  interview.</p>

  <blockquote>
    <p>If I publish a paper in <em>Nature</em>, for example, it can
    be made freely available in my institute's repository after six
    months. Some journals let archived papers be made available
    immediately.</p>
  </blockquote>

  <p>... and again later ...</p>

  <blockquote>
    <p>But many publishers have no problem with the open archives
    approach, even if some still require a delay.</p>
  </blockquote>

  <p>In our discussions with Elsevier we were assured that the
  policy of <em>that</em> publisher is to allow authors to use
  institutional repositories at any time (but see the caveats
  below).</p>

  <blockquote>
    <p>One issue that is yet to be resolved, however, is copyright.
    I argue that we should be permitted to put in the repository
    the full text article as it appears in a journal.</p>
  </blockquote>

  <p>There is a difference between "full text" and "as it appears
  in the journal". If the journal has put in any effort at all into
  re-formatting your text/images in order to get it to conform with
  their journal standard, then the copyright for <em>that</em>
  re-formatting work (usually a combination of manual labour and
  software) belongs to the journal.</p>

  <p>For example, Elsevier insists that you do <em>not</em> put the
  PDF (or other) image file of the <em>exact</em> form of the
  journal publication in your institute repository.</p>

  <p>I personally find this quite acceptable since papers in the
  Mathematical Sciences are perfectly readable in the form in which
  the authors <em>submit</em> them to the journal. However,
  re-creating a distributable PDF or other online form of one's
  paper may be far more difficult in other disciplines --- I have
  no idea.</p>

  <blockquote>
    <p>For this, countries such as India should have a law
    specifying that the copyright for articles published with
    publicly-funded research always vests with the authors and
    their institutions.</p>
  </blockquote>

  <p>One need not wait for copyright law to change. The directors
  of each of the research institutes can insist that every paper
  sent for publication should be made available in the form of a
  research report with the institute library. By extension, the
  electronic form of this report would be in the institutional
  repository. One way to ensure compliance is to only allow reports
  that are available in the institute library to be used for
  evaluation (for promotions and the like).</p>

  <p>The scientists would then refrain from giving up <em>all</em>
  copyright to their publishers. In my (limited) experience,
  publishers will not object to authors retaining the right to make
  copies as long as such copies are not independently sold.</p>

  <p>Unfortunately, scientists as "the silent compliant mob" does
  not fit with my experience. In all matters which relate to
  science administration (and publications are at the centre of
  that), scientists are by-and-large "status quo"-ists. It will
  need a strong push from those at the top of the ladder to change
  the status quo. Professor P. Balaram is certainly one of those 
  at "the top of the ladder" so I would like to see more action to match
  his words!</p>

  <p><em>Update</em>: Fixed the URL thanks to Abhishek Dasgupta. Also
  clarified the last sentence.</p>

]]></description>
   <category domain="http://www.imsc.res.in/~kapil/blog"></category>
   <pubDate>Sun, 13 Jul 2008 01:38 GMT</pubDate>
</item>
<item>
   <title>IMSc eprint server</title>
   <guid isPermaLink="false">publishing/eprint-server-2008-05-20-11-02</guid>
   <link>http://www.imsc.res.in/~kapil/blog/publishing/eprint-server-2008-05-20-11-02.html</link>
   <description><![CDATA[

  <p>As <a href=
  "publishing/open-access-2007-11-26-11-30.html">documented</a>
  earlier, we needed an institutional repository for IMSc. This
  seemed like a good time to review the Debian package for
  <a href="http://eprints.org">e-prints</a>
  created by David Tarrant for which he has been <a href=
  "http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=171968#29">looking</a>
  <a href=
  "http://lists.debian.org/debian-mentors/2007/08/msg00618.html">for</a>
  a <a href=
  "http://lists.debian.org/debian-science/2007/09/msg00001.html">sponsor</a>.</p>

  <p>Nutan and Kinjal also worked on this package for incorporation
  into the IMSc systems. We ended up re-doing their work and David
  Tarrant's for a number of reasons which I may write about later.
  Let me instead document how we got the e-print server
  working.</p>

  <p>First of all we created a <a href=
  "http://linux-vserver.org">vserver</a> using the stock Debian
  kernel and utilities. On this vserver Ravi installed the Debian
  package created by Tarrant and got it to co-operate with the rest
  of the system.</p>

  <p>The first problem was that we were unable to deposit anything
  into the archive! It turned out that the way in which the
  software checks for free space uses system calls which are
  disabled under a vserver. For the moment we are thus forced to
  set <code>enable_df=0</code> and run without these checks.</p>

  <p>The second problem was that all our web services are run
  through a common front-end server. The e-prints server was to be
  run as one of the back-end servers and it did seem that
  configuring it as such was going to be hard. In the end, it
  turned out to be rather easy. The only settings we required were
  as follows.</p>

  <p>In the file <code>$ARCHIVETOP/cfg/cfg.d/10_core.pl</code> we
  put the host entry as <code>www.imsc.res.in</code>; in
  <code>20_baseurls.pl</code> in the same directory we put the base
  path as <code>eprints</code>. This allowed us to map
  <code>www.imsc.res.in/eprints</code> to the internal server using
  apache2's reverse proxy rules.</p>

  <p>Unfortunately, this was not quite enough since the base path
  was not used in
  <code>$ARCHIVETOP/cfg/lang/en/static/index.xpage</code>. But we
  only need to configure that file and the <code>branding.pl</code>
  file and we were off!</p>

  <p>That left the task of registering the server with the <a href=
  "http://www.openarchives.org">OAI</a>. This brought up another
  problem. We had used the HTTPS protocol on the front-end since
  the site requires password-based logins. It turns out that the
  OAI's <a href=
  "http://www.openarchives.org/Register/ValidateSite">registration
  page</a> does not accept HTTPS URLs!</p>

  <p>So we will need some more fine tuning at a later stage. For
  now, people are submitting some doucments and one that picks up
  we can be motivated to work some more!</p>

]]></description>
   <category domain="http://www.imsc.res.in/~kapil/blog"></category>
   <pubDate>Tue, 20 May 2008 05:32 GMT</pubDate>
</item>
<item>
   <title>Publication and Promotion Norms</title>
   <guid isPermaLink="false">publishing/why-norms-2007-11-28-08-51</guid>
   <link>http://www.imsc.res.in/~kapil/blog/publishing/why-norms-2007-11-28-08-51.html</link>
   <description><![CDATA[

  <p>Many people wondered why the <a href=
  "open-access-2007-11-26-11-30">open access guidelines</a>
  mention evaluation and promotion guidelines. Here is my
  answer.</p>

  <p>The "encouragement" given to IMSc members to publish in some
  kind of open access or low-cost format will be toothless if we do
  not clearly indicate that location of publication will
  <em>not</em> be the dominant factor in the decision making
  process.</p>

  <p>Most (high cost) journals see their major selling point in
  today's world is that that they provide citation and impact
  factors[1]. We have to take the down the value of these factors
  by a couple of notches.</p>

]]></description>
   <category domain="http://www.imsc.res.in/~kapil/blog"></category>
   <pubDate>Wed, 28 Nov 2007 03:21 GMT</pubDate>
</item>
<item>
   <title>Why IMSc eprints?</title>
   <guid isPermaLink="false">publishing/why-eprints-2007-11-27-15-38</guid>
   <link>http://www.imsc.res.in/~kapil/blog/publishing/why-eprints-2007-11-27-15-38.html</link>
   <description><![CDATA[

  <p>Many people asked why the <a href=
  "open-access-2007-11-26-11-30">open access guidelines</a>
  <em>require</em> the availability of the publication from the
  IMSc web site.</p>

  <ol class="decimal">
    <li>
      <p>The publications of the IMSc form the recognisable core of
      its output and this is recorded by our annual report.</p>
    </li>

    <li>
      <p>This output (which may be considered as an appendix to the
      annual report) should be available to anyone who requests any
      part of it.<a href="#fn1" class="footnoteRef" id="fnref1"
      name="fnref1"><sup>1</sup></a></p>
    </li>

    <li>
      <p>Since the work being talked about is being published in
      other fora we cannot really claim that the work is
      "secret".</p>
    </li>

    <li>
      <p>We need to ensure long-term availability of the work from
      a location that can be identified with the IMSc.
      Traditionally it could have been the IMSc library alone;
      nowadays the IMSc web site would be equally important.</p>
    </li>

    <li>
      <p>None of this precludes the publication of the work in any
      other form or medium so that no freedom of the author(s) is
      being encroached upon.</p>
    </li>
  </ol>

  <p>So what is being asked for is:</p>

  <ol class="lower-alpha">
    <li>
      <p>Every publication of the IMSc should be available in
      definitive form from a URL of the form</p>
      <pre>
<code>http://www.imsc.res.in/eprints/....
</code>
</pre>
    </li>

    <li>
      <p>The author(s) of such a publication will give IMSc a
      license in perpetuity to make this data available freely (as
      in mufta or without cost).</p>
    </li>
  </ol>

  <div class="footnotes">
    <hr>

    <ol>
      <li id="fn1">
        <p>Under the Right To Information Act this may even be a
        legal requirement but I am not a lawyer! <a href="#fnref1"
        class="footnoteBackLink" title=
        "Jump back to footnote 1">&#8617;</a></p>
      </li>
    </ol>
  </div>

]]></description>
   <category domain="http://www.imsc.res.in/~kapil/blog"></category>
   <pubDate>Tue, 27 Nov 2007 10:08 GMT</pubDate>
</item>
<item>
   <title>Open Access</title>
   <guid isPermaLink="false">publishing/open-access-2007-11-26-11-30</guid>
   <link>http://www.imsc.res.in/~kapil/blog/publishing/open-access-2007-11-26-11-30.html</link>
   <description><![CDATA[

  <p>The IMSc maths group came up with the following admirable
  resolutions.</p>

  <ol class="decimal">
    <li>
      <p>IMSc requires its members to make available their work
      (when it reaches definitive form) on the IMSc website; this
      website will remain open access.</p>
    </li>

    <li>
      <p>IMSc encourages its members to post their work in
      definitive form on an open access web space of high
      visibility (eg. the arXiv). This is because the world at
      large may not be aware of the IMSc website.</p>
    </li>

    <li>
      <p>IMSc encourages its members to publish their work in open
      access/ low-cost journals.</p>
    </li>

    <li>
      <p>IMSc encourages its members to help in the creation, edit-
      ing and refereeing of open access/ low-cost journals.</p>
    </li>

    <li>
      <p>IMSc emphasizes content over location when evaluating
      publications for purposes of hiring/promotions.</p>
    </li>
  </ol>

  <p>Let us see how well we can follow them!</p>

]]></description>
   <category domain="http://www.imsc.res.in/~kapil/blog"></category>
   <pubDate>Mon, 26 Nov 2007 06:00 GMT</pubDate>
</item>
</channel>
</rss>
