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  July 2009

JISC-REPOSITORIES July 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Eprint request button - data on effectiveness

From:

Stevan Harnad <[log in to unmask]>

Reply-To:

Stevan Harnad <[log in to unmask]>

Date:

Tue, 28 Jul 2009 17:00:08 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (148 lines)

On Tue, Jul 28, 2009 at 1:43 PM, Klaus Graf<[log in to unmask]> wrote:

>> From: Michael White  michael.white -- stir.ac.uk
>>
>> ... I think/hope that as academics get more accustomed to using this
>> facility, response rates will improve (and possibly already are).
>
> I do not think that using the request button is a valid OA strategy.
> My own experience was that I received few response when requesting an
> article. The St. Gallen IR manager said that requesters can obtain
> much more positive results when mailing to the scholar directly.

(1) Michael White reported that the response rates for the request
button are about 50% fulfillment, 5% refusal and 45% no response.

(2) He also said that some of the no-responses may have been (2a)
elapsed email addresses, (2b) temporary absence, (2c) embargoed
theses, and (2d) author unfamiliarity with purpose and use of the
email eprint request Button.

(3) He also noted that the response rates may well improve with time.
(I would add that that's virtually certain: It is still exceedingly
early days for the Button, and time -- as well as the growing clamor
for access [and impact] -- is on the Button's side.)

(4) It is harder to imagine why and how the long and complicated
alternative procedure -- of a user discovering an article that has not
been deposited by the author, finding the author's email address, and
sending him an email eprint request, to which the author must respond
by sending an email and attaching the eprint -- would "obtain much
more positive results" than the author depositing the article in his
IR, once, and letting the IR's Button send the email requests for the
requesters to the author with no need for look-up, and only one click
needed from the author to fulfill the request.

(5) The email eprint request Button does not provide OA; it only
provides "Almost OA." But that's infinitely better than no OA. And the
Button (and the Immediate-Deposit/Optional-Access -- ID/OA -- Mandate,
for which the Button was designed) make it possible for institutions
and funders to adopt Green OA mandates that neither need to allow
exemptions from immediate deposit nor do they need to allow publishers
to dictate whether or when the deposit is made.
http://openaccess.eprints.org/index.php?/archives/71-guid.html

(If publishers have a say, it is only about whether and when the
deposit is made OA, not about whether or when the deposit is made at
all. Since 63% of journals are already Green on immediate OA, the
ID/OA Button means that institution or funder can reach
uncontroversial consensus on 100% deposit, yielding at least 63%
immediate OA and 37% Almost-OA, whereas the alternative is not
arriving at a consensus on mandating OA at all, or adopting a weaker
mandate that only provides OA after an embargo period, or only at the
publisher's behest, or allows author opt-out. And the most important
thing is not only that the ID/OA provides more access and is easier to
agree to adopt, but it will also quite naturally drive embargoes into
their well-deserved graves, as the mandates and their resulting OA --
and the demand for it -- grow.)
http://openaccess.eprints.org/index.php?/archives/494-guid.html

> The Oppenheim/Harnad "preprint &
> corrigenda" strategy "of tiding over a publisher's OA embargo: Make the
> unrefereed preprint OA before submitting to the journal, and if upon
> acceptance the journal seeks to embargo OA to the refereed postprint,
> instead update the OA preprint with a corrigenda file.
> http://bit.ly/vi3JQ " is a valid OA strategy because the eprint is PUBLIC.

What makes a strategy "valid" is that it works, increasing access,
Open Access, and Open Access mandates.

Both the "preprint&corrigenda" strategy and the "ID/OA-mandate&Button"
strategy can increase access, OA, and OA mandates, but the
ID/OA-mandate&Button strategy is universal: it scales up to cover all
of OA's target content, whereas the preprint&corrigenda strategy is
not universal, for it does not and cannot cover those disciplines (and
individual authors) that have good (and bad) reasons not to want to
make their unrefereed preprints public.

> If an article is published then the author hasn't any right under OA
> aspects to choose which requester has enough "dignity" to receive an
> eprint. I cannot accept the arbitrariness of such a decision under OA
> circumstances.

Relax. The reason neophyte self-archivers are not fulfilling Button
requests is because they are either not getting them or don't yet
understand them, not because they are making value judgments about who
does and does not merit the privilege of accessing their work!

They'll learn: If necessary, they'll learn under the pressure of the
impact-weighting of publications in performance evaluation. But my
hunch is that they already know they want the user-access and
user-impact (from the eager way they do vanity searches in the
biobliography of every work they pick up in their research field, to
check whether their own work has been cited). So all they really need
to learn now is how the Button works, and why.
http://openaccess.eprints.org/index.php?/archives/274-guid.html

Stevan Harnad

>On November 22, 2008 Arthur Sale wrote in this list:
>
> "For example if you had asked for a thesis, the following could have happened:
>
> a.  The research might have a totally banned commercial reason for
> non-disclosure (I have just had a PhD student graduate, and the
> company that sponsors him insists on a two year total embargo so they
> can exploit the research. This is not peer reviewed and published
> research.
>
> b.  You might be asking during the exam period / summer holidays (you
> will know your northern summer is 6 months out of sync with ours,
> ditto academic year).
>
> c.  The graduate may have left the University and the email address on
> record might be defunct.
>
> ˇ         Fourthly, the author may still be ignorant or worried about
> their rights under Australian copyright law (unfounded, but real)."
>
> If I need an eprint NOW I cannot wait until the Australian summer is over.
>
> My recents findings on Zurich's ZORA
> http://archiv.twoday.net/stories/5815961/ are supporting evidence for
> the following:
>
> (1) Scholars generally prefer to deposit publisher's PDF even the
> closed access is therefore permanent.
>
> (2) If the rate of permanent closed access items in an IR is high the
> probability that after years an author's mail adress is still working
> is low.
>
> For German law there is very strong evidence that the request button
> is clear not lawful. (It's another question if a publisher can or will
> enforce the interdiction. Most IR managers are fearful men - it would
> be enough if a publisher would send a polite mail as expression of his
> discontent with the request button and on the next day the IR manager
> will deactivate the button ...)
>
> If depositing needs a few keystrokes and only few scholars are
> depositing without mandate - why should they react spontaneously on a
> eprint request via button?
>
> Nobody says that ILL is an OA strategy but it is doing more and better
> for the research communication than this unfortunate button.
>
> Klaus Graf
>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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