JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for JISC-REPOSITORIES Archives


JISC-REPOSITORIES Archives

JISC-REPOSITORIES Archives


JISC-REPOSITORIES@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

JISC-REPOSITORIES Home

JISC-REPOSITORIES Home

JISC-REPOSITORIES  January 2011

JISC-REPOSITORIES January 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Rights Reductio Ad Absurdum

From:

Stevan Harnad <[log in to unmask]>

Reply-To:

Stevan Harnad <[log in to unmask]>

Date:

Thu, 6 Jan 2011 08:47:38 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (290 lines)

On Thu, Jan 6, 2011 at 6:22 AM, FrederickFriend <[log in to unmask]> wrote:

> Like David I agree with Stevan apart from his criticism of SHERPA-RoMEO.
>
> In one sense the Elsevier wording comes as no surprise, in that when many
> publishers have said that they allow "green" self-archiving it has always
> been with a sometimes unspoken "caveat" that they will review their policy
> if repository deposit happens on a large scale. The more recent element is
> the inclusion of "institutional repositories with mandates for systematic
> postings", which I assume to be Elsevier's response to the growing number of
> institutional mandates. I agree with Stevan that authors should not hold
> back from repository deposit if they do not know whether or not the wording
> applies to them. They should hold onto their rights as authors.
>
> Despite ambiguities around the words "mandates for systematic postings",
> Elsevier are more open than some other publishers about their wishes on
> repository deposit. There are rumours than another major publisher is taking
> action to block repository deposit without publicising the fact on
> SHERPA-RoMEO. I encourage all repository managers to share any information
> they have about how publisher policies are being applied in practice.

It will come as no surprise that I disagree -- profoundly -- with my
three friends David Prosser, Charles Oppenheim and Fred Friend, on the
precise practical question on which they are demurring, as if it were
rather an ethical or legal imperative (which it most decidedly is
not):

Here are, I think, are the relevant objective data:

(1) It has been possible for researchers to self-archive their
unrefereed and refereed drafts for at least two decades. Proof:
Computer scientists and physicists have been doing it successfully for
two decades.

(2) Despite this, over 85% of authors in fields other than computer
science and physics have *not* been self-archiving throughout the past
two decades, despite the demonstrations of its possibility,
feasibility and benefits, and despite the invention of a name to
describe the result ("open access," OA) and a movement to facilitate
it.

(3) In the past decade, 85% of researchers have continued to fail to
self-archive, despite the fact that the majority of journals -- and
virtually all the top journals -- have given their green light to
self-archive.

(4) One of the (many) reasons why researchers do not self-archive is
profound confusions, generating unfounded worries, about rights:
http://www.eprints.org/openaccess/self-faq/#10.Copyright

(5) The source of the confusions is partly in authors' own fuzzy
notions about copyright and consequences, compounded by conflicting
(and equally confused) advice and "expert judgments" from permissions
officers and lawyers who are mostly just opining themselves.

(6) The model on which most of the faulty advice is given to authors
is course-packs in which teachers distribute multiple paper copies of
the copyrighted work of *others* for teaching purposes: This has
nothing whatsoever to do with authors giving away their *own* work
online for research purposes.

(7) But for the majority of journals (including virtually all the top
journals) the above has been mooted by the fact that they have given
their authors the green light to give away their own work online for
research purposes.

(8) All that is needed in order to inform the author community about
which journals have given their authors the green light to give away
their own work online for research purposes is to specify WHICH
journals have given their green light to depositing WHAT, WHERE and
WHEN.

(9) WHICH means: specifying the journal.

(10) WHAT means: specifying what may be deposited: the only relevant
distinction here is whether the green light is for the unrefereed
draft ("PALE-GREEN") or the refereed draft ("GREEN"); the default for
GREEN is the author's final, revised, refereed, accepted draft;
anything beyond that (such as the publisher's proprietary PDF) is an
extra, and can be left to authors to ferret out for themselves, if
they so desire, by consulting the journal's policy details; the cause
of dispelling the unfounded worry about self-archiving itself is fully
served by indicating whether the journal is PALE-GREEN or GREEN.
Otherwise the journal is GRAY (meaning it does not give its green
light to self-archiving either the unrefereed or the refereed draft).

(11) WHERE, by default, means the author's institutional repository.
Just as some journals do not endorse self-archiving the publisher's
PDF, some do not endorse self-archiving institution-externally, in a
third-party repository. The distinction is vacuous, since an article
that is accessible free for all anywhere on the web is accessible free
for all everywhere on the web, and its metadata can be harvested by
innumerable central indices and search engines.

(12) WHEN is not vacuous, but a journal that does not give its green
light to self-archiving the author's final, revised, refereed,
accepted draft immediately upon publication is either just a
PALE-GREEN publisher or a GRAY publisher.

(13) So all that authors who are afraid to self-archive need to know
is whether their journal is GREEN, PALE-GREEN, or GRAY -- and, if the
latter two, the length of the embargo on the self-archiving of the
refereed draft.

(14) Instead, SHERPA-Romeo offers authors a needless profusion of
colour-codes (green, blue, yellow, white) accompanied by an endless,
confusing and completely unnecessary welter of conditions and
restrictions, no doubt a source of abiding interest to beleaguered
permissions librarians, accustomed only to puzzling over usage rights
for incoming third-party content rather than outgoing own-content --
and perhaps also to cataloguers accustomed to cataloguing all metadata
without having to ask themselves why -- but for authors merely a
reinforcement of the antecedent state of confusion and indecision that
has already kept 85% of them from self-archiving for two decades now:
the very confusion and indecision that a clear, relevant journal
self-archiving policy index was meant to dispel.

So, no, the purpose of a journal self-archiving policy index is *not*
to catalogue every nuance of every publisher's copyright policy: It is
only to inform authors whether or not their journal has given its
green light to self-archive the unrefereed or refereed draft of their
article, in their institutional repository, immediately upon
publication (and if not, when).

Whatever further verbiage the publisher may choose to append to this
basic information -- including hocus-pocus about the distinction
between an "institutional website" versus an "institutional
repository," "spontaneous self-archiving" versus "mandated
self-archiving," and authors' blue-eyed uncles -- can be left to
authors to look up if they wish. The journal self-archiving policy
index's work will be done having provided the PALE-GREEN/GREEN data
and the embargo-length.

And, no, all the faithful echoing of all the minutiae of each
publisher's copyright conditions -- apart from the essential ones
above -- is *not* the solemn ethical duty of a journal self-archiving
policy index to provide, come what may. Nor is it a legal, ethical or
scholarly failing to fail to echo it (let alone to keep warning
authors that even these hedged and hobbled conditions risk being
rescinded if they comply! )
http://www.eprints.org/openaccess/self-faq/#32.Poisoned

On the contrary, winnowing the substantive wheat from the irrelevant
and often incoherent chaff would provide an invaluable service to
authors who are undecided and uncertain about self-archiving -- in a
way that simply reproducing the whole mess certainly will not.

Perhaps we need two SHERPA/Romeos: one for authors who want to know
whether or not they have their journal's green light to provide OA by
self-archiving (Oa), and one for permissions librarians and others who
may be concerned to know every nuance of every journal's copyright
policy, for whatever reason (Ob). SHERPA/Romeo is trying to do both,
with the result that it is hardly doing Oa at all, perhaps even
undoing it.

One last observation (a conjecture): It may be that the reason why
SHERPA/Romeo has become so top-heavy on permission-librarian minutiae
is that at some institutions the "self"-archiving is not being done by
authors at all, but by librarians, on their behalf. If so, perhaps
this is a mixed blessing: It does spare the authors having to do a few
keystrokes, but at the cost of a great deal of OA's target content not
getting "self"-archived at all, because deposit is being decided by
third parties, according to third-party criteria, instead of what good
sense and good practice would dictate.

This is a moot point whilst self-archiving mandates are still rare:
Without a mandate, librarian intervention and mediation seems to be
the only way to eke out more OA content.

But proxy-archiving and imploring by librarians is not the scaleable,
sustainable solution for OA: green self-archiving mandates are. And
for mandates it's all the more important to dispel the pettifoggery
and get to the essentials: GREEN, PALE-GREEN and embargo length.
That's all.

Stevan Harnad


> -----Original Message----- From: David Prosser
> Sent: Thursday, January 06, 2011 10:30 AM
> To: [log in to unmask]
> Subject: Re: Rights Reductio Ad Absurdum
>
> Of course, I agree with almost everything Stevan says.  The exception being
> the rather snide comments regarding SHERPA-RoMEO.
>
> RoMEO is not 'enshrining' or 'canonising' anything.  It is reporting.  And
> if an author signs a copyright agreement with Elsevier then they are are
> agreeing to the terms reported.  We may all agree that these terms are ' (1)
> arbitrary, (2) incoherent, and (3) unenforceable', but it's not for RoMEO to
> make that call.  It is a database of 'permissions that are normally given as
> part of each publisher's copyright transfer agreement' not 'permission that
> we think sensible leaving out the one's we don't like'.  That may reduce its
> advocacy power and do nothing to dispel the confusion being created by
> publishers with arbitrary, incoherent, and (possibly) unenforceable clauses
> in their policies, but it does have the advantage of being honest.
>
> David

On 2011-01-06, at 6:05 AM, CHARLES OPPENHEIM wrote:

> I totally agree with David's point.  I would compare it to a Yellow Pages Telephone
> Directory - it faithfully reports what it is aware of, and makes no judgement about
> the quality of the service provided.  It is still incredibly useful as a resource, but it
> is up to authors to decide who they wish to publish with, not Romeo.

> Charles

> Professor Charles Oppenheim

>
> On 6 Jan 2011, at 03:00, Stevan Harnad wrote:
>
>> ** Cross-posted **
>>
>> The following query came up on the UKCORR mailing list:
>>
>>> I was surprised to read the paragraph below under author's rights
>>>  (http://www.elsevier.com/wps/find/authorsview.authors/copyright##rights)
>>>
>>>> "the right to post a revised personal version of the text of the
>>>> final journal article (to reflect changes made in the peer review
>>>> process) on your personal or institutional web site or server for
>>>> scholarly purposes, incorporating the complete citation and with a
>>>> link to the Digital Object Identifier (DOI) of the article (but not
>>>> in subject-oriented or centralized repositories or institutional
>>>> repositories with mandates for systematic postings unless there is
>>>> a specific agreement with the publisher- see
>>>> http://www.elsevier.com/fundingbody agreements for further
>>>> information]);"
>>
>> You can't blame Elsevier's Perplexed Permissions Personnel for trying:
>> After all, if researchers -- clueless and cowed about copyright --
>> have already lost nearly two decades of research access and impact for
>> no reason at all, making it clear that only if/(when they are required
>> (mandated) by their institutions and funders will they dare to do what
>> is manifestly in their own best interests and already fully within
>> their reach, then it's only natural that those who perceive their own
>> interests to be in conflict with those of research and researchers
>> will attempt to see whether they cannot capitalize on researchers'
>> guileless gullibility, yet again.
>>
>> In three words, the above "restrictions" on the green light to make
>> author's final drafts OA are (1) arbitrary, (2) incoherent, and (3)
>> unenforceable. They are the rough equivalent of saying: You have "the
>> right to post a revised personal version of the text of the final
>> journal article (to reflect changes made in the peer review process)
>> on your personal or institutional web site or server for scholarly
>> purposes -- but not if you are required to do so by your institution
>> or funder."
>>
>> They might as well have added "or if you have a blue-eyed uncle who
>> prefers tea to toast on alternate Tuesdays."
>>
>> My own inclination is to say that if researchers prove to be stupid
>> enough to fall for that, then they deserve everything that is coming
>> to them (or rather, withheld from them).
>>
>> But even I, seasoned cynic that the last 20 years have made me, don't
>> believe that researchers are quite that stupid -- though I wouldn't
>> put it past SHERPA/Romeo to go ahead and solemnly enshrine this latest
>> bit of double-talk in one of its slavish lists of "General Conditions"
>> on a publisher's otherwise "green" self-archiving policy, thereby
>> helpfully furnishing an effective pseudo-official megaphone for every
>> such piece of optimistic gibberish, no matter how absurd.
>>
>> My advice to authors (if, unlike what the sensible computer scientists
>> and physicists have been doing all along -- namely, self-archiving
>> without first seeking anyone's blessing for two decades -- they only
>> durst self-archive if their publishers have first given them their
>> green light to do so) is that they take their publishers at their word
>> when they do give them their green light to do so, and ignore any
>> SHERPA/Romeo tommy-rot they may try to append to that green light to
>> make it seem as if there is any rational line that can be drawn
>> between "yes, you may make your refereed final draft OA" and "no, you
>> may not make your refereed final draft OA."
>>
>> For those who are interested in knowing what is actually happening,
>> worldwide, insofar as OA self-archiving is concerned, I recommend
>> reading Peter Suber's stirring 2010 Summary of real progress rather
>> than the sort of pseudo-legalistic smoke-screening periodically
>> emitted by Permissions Department Pundits (whether or not not they are
>> canonized by SHERPA-Romeo):
>> http://www.earlham.edu/%7Epeters/fos/newsletter/01-02-11.htm#2010
>>
>> Dixit,
>>
>> Your Weary and Wizened Archivangelist
>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
November 2005
October 2005


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager