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  October 2008

JISC-REPOSITORIES October 2008

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Explaining and Justifying a Mandate

From:

Stevan Harnad <[log in to unmask]>

Reply-To:

Stevan Harnad <[log in to unmask]>

Date:

Sun, 12 Oct 2008 11:54:09 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (129 lines)

Apologies for cross-posting, but this brilliant list from Andrew Adams
deserves wide circulation! Some references and suggested addenda
below:

On Sun, Oct 12, 2008 at 8:54 AM, Andrew A. Adams
<[log in to unmask]> wrote:

> After about four years (which pales besides the length of service to OA of
> many on this list) of seriously pushing my University (University of Reading
> in the UK) they're finally going ahead with instituting an IR. The main
> driver for this seems to be the REF and the need to potentially track all the
> output of our researchers. At this stage our PVC(Research) is still somewhat
> unsure of the nature of the non-technical elements of an IR, i.e. about the
> language of and necessity for a deposit mandate. I therefore need to make a
> decisive pitch for a mandate. Ideally it needs to start with the "elevator
> pitch" and then provide solid foundations for the claims in the elevator
> pitch, and so I'm hoping the combined brain trust on this list can help me to
> identify these precise details (facts, figures and published references)
> which are the most accurate and compelling in putting the mandate case
> forward. Here is the skeleton of my pitch.
>
> -- An IR without a mandate is like serving soup with only a fork: you'll get
> something, but it's not really worth the trouble.

Cite Arthur Sale's published studies on this, as well as Alma Swan's surveys:

http://eprints.utas.edu.au/view/authors/Sale,_AHJ.html
http://www.keyperspectives.co.uk/openaccessarchive/index.html

> -- The principle purpose of an IR is to provide access to our research output
> for those who do not have a subscription to the physical and/or online
> publisher production.

Cite Ulrich's for the total serial output, and the ARL holdings stats
for the fraction affordable to any university.

http://www.ulrichsweb.com/ulrichsweb/
http://fisher.lib.virginia.edu/cgi-local/arlbin/arl.cgi?task=setupstats

> -- Consequence: basic meta-data plus full text are the primary goal.
> Sophisticated meta-data is a secondary element and should NEVER be allowed to
> delay deposit.

Bravo! Spot-on!

> -- Because our research outputs are readable by all, they are more likely to be
> cited.

Cite the many studies in the Bibliography of Findings on the Open
Access Impact Advantage:

http://opcit.eprints.org/oacitation-biblio.html

>  -- Consequence: relative and absolute improvements in citation rates for high
> quality work.

As above.

> -- Finding the output is not the big problem - syntactic search through Google
> Scholar, OAIster and others provide 95% of findability, but it's only useful
> to find the article if you can then read the article not just the meta-data.
>
> -- Consequence: scalable deposit requires one of the authors to deposit the
> full text and basic meta-data. More sophisticated meta-data may be added by a
> librarian or similar, but must not delay the availability of the item.

Bravo! Spot-on!

> -- No academic or university has ever been sued for making their peer reviewed
> journal output available in an IR.
>
> -- Consequence: the default should be open access to the full text. In case
> of doubt about a publisher's intent, open access should be set. Only where
> embargoes are clear should they be set. In the case of an embargo, the
> "Request an e-print" button provides a simple one-click email to the author
> to request a copy. Doubts about a publisher's rules should never prevent
> deposit, only access settings.

Bravo! (But allow the possibility of Closed Access as the default
option for the faint-hearted, rather than putting consensus on mandate
adoption at risk by making the mandate stronger than necessary.)

>  - Consequence: Since author(s) as well as the university benefit and there
> is no risk, direct availability, and the ability to edit one's deposits
> should be granted to authors, with no editor to get in the way. Editing can
> be done afterwards, once the basic meta-data and full text are available.

Bravo! Spot-on!

> It is the text, data and diagrams that are important, not the layout.
>
>  - Consequence: the author's submitted final draft is what needs depositing,
> not a "publisher's PDF". PDF and HTML formats are preferred over proprietary
> formats such as Word. Simple tools to produce PDFs should be made available
> to staff or even embedded in the repository system.

Bravo! Spot-on!

> Carrots are better than sticks in encouraging deposit.
>
>  - Consequence: all university procedures which involve publications should
> draw their information from the repository, particularly promotion and
> incentive procedures.

Bravo! Spot-on!

I suggest also adding something about the growing potential of
metrics, not only for REF, but for internal and external auditing
purposes. The IRs can generate IRstats with increasing rich, diverse
and revealing metrics (citations, downloads, co-citations, book
citations, citation/download growth decay metrics, endogamy/exogamy,
hubs/authorities, and mann many more).

http://trac.eprints.org/projects/irstats
http://www.citebase.org/

Congratulations on an invaluable set of rationales for OA mandates.
Please add it to your IR as a FAQ for others!

Best wishes,

Stevan


> Dr Andrew A Adams, School of Systems Engineering
> The University of Reading, Reading, RG6 6AY, UK
> Tel:44-118-378-6997 E-mail:[log in to unmask]
> http://www.rdg.ac.uk/~sis00aaa/

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