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

Help for LIS-ELIB Archives


LIS-ELIB Archives

LIS-ELIB Archives


LIS-ELIB@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

LIS-ELIB Home

LIS-ELIB Home

LIS-ELIB  November 2006

LIS-ELIB November 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

The Patchwork Mandate (fwd)

From:

Stevan Harnad <[log in to unmask]>

Reply-To:

Stevan Harnad <[log in to unmask]>

Date:

Sat, 11 Nov 2006 12:23:48 +0000

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (215 lines)

        ** Apologies for Cross-Posting  **

Below is yet another brilliant and timely stroke from the Archivangelist
of the Antipodes (who is rapidly gaining worldwide moral hegemony!):

Arthur Sale is so right: Where the university's senior management are
momentarily immovable, the right target is a promising individual
department or two: The focussed outcome of a departmental mandate can be
even faster and more dramatic than a university-wide one, serving as
an irresistible stepping stone toward a university-wide mandate. 

And there is supporting evidence: The outcome of the Tasmania CS and
Southampton ECS departmental mandates, there to prove it works (and both
of them leading to university-wide mandates thereafter):

    http://www.eprints.org/signup/fulllist.php

---------- Forwarded message ----------
Date: Sat, 11 Nov 2006 15:15:25 +1100
From: Arthur Sale <[log in to unmask]>
To: [log in to unmask]
Subject: The Patchwork Mandate

Over the last few months this list has been inundated by people looking for
policies to adopt for their institutional repositories, and frustrated by
their management's inability to see that a mandate is required. I haven't
been very helpful to the enquirers, because all of the encouragement type
policies are known to be quite inadequate. However, I have done some
thinking and have now put together a short paper (4 pages) on an option for
repository managers wanting to fill their repositories under unhelpful
conditions - The Patchwork Mandate.

I encourage you to download the working paper from
http://eprints.utas.edu.au/410/, as it has nice typesetting and
readability [and hyperlinks] in a pdf file. You can even show it to your
senior managers. However, if you can't or don't want to, I have pasted
the text below.

Arthur Sale
Professor of Computing (Research)
University of Tasmania

- > PASTED PAPER BEGINS

The Patchwork Mandate
Technical Report
Arthur Sale, 11 November 2006

Policies for Repository Managers

This document is written mainly for repository managers who are at a loss 
as to what policies they (or their universities or research institutions)
ought to deploy. I make no bones about stating that there are only two
"pure" policies:

*        requiring (mandating) researchers to deposit, and 
*        voluntary (spontaneous) participation.

The institutional mandate

The obvious and no-risk solution is for the institution to require
researchers to deposit their publications in the institutional repository.
There is ample evidence that this is acceptable to over 95% of researchers,
both in pre-implementation surveys and in post-implementation evidence. One
Australian university is leading the world in collecting 70% of its annual
research output and the fraction is rising. This is not surprising, since
the researcher's world is hemmed in with the requirements to teach, to ask
for student evaluations, to write and mark examinations, to supervise PhD
students, to publish research, to report to granting bodies, etc. However
because of the age of senior executives (Rectors, Vice-Chancellors,
Presidents or the Research Vice-Presidents, Pro Vice-Chancellors, etc) it
may be difficult to convince them that they have been carried into a new era
of scholarly dissemination while they weren't looking, and that their
attitudes are horribly obsolescent.

An institutional-wide requirement to deposit in the IR is the logical and
inevitable end-point. In fact it is exactly what is needed. Once such a
policy is in place the IR manager's approaches to researchers and heads of
centers and all the plethora of feel-good activities actually work. People
who are required to deposit their publications are grateful for advice. The
occasional chase-up call is not resented. Just about everything that the
university can put in place (for example publicity for deposits, awards for
the best author or paper, assistance with self-archiving, download
statistics, etc) will begin to work as it resonates with every academic in
fulfilling their duty.

A mandatory policy will approach a capture rate of 100% of current research
publications, but over a couple of years. Figures of 60-90% can be expected
in a short time. See
http://www.firstmonday.org/issues/issue11_10/sale/index.html for some data
on how mandates actually work. 

Voluntary participation

The 'everything else' policies are not worth talking about for long. In the
absence of mandates, every encouragement policy known to Man fails to
convince more than 15% to 20% of researchers to invest the 5 minutes of time
needed to deposit their publications. The percentage does not grow with
time. When you look at this closely, all these encouragement policies
(awards to top authors, regular articles in the house magazine, great
feedback, personal approaches, download statistics, seminars, explanation of
the OA advantages, etc) fail. This is a global experience, but I have plenty
of Australian examples. The reason is easy to grasp: these activities appeal
to the converted and the practicing self-archivers, not the skeptics or the
lazy. In other words they simply pass over the heads of over 80% of the
potential contributors without engagement with the little grey cells.

I must emphasize that such policies are known to achieve no greater deposit
rate of current research than 30% and more usually around 15%. The evidence
can be produced and is absolutely clear. At such deposit rates, one wonders
why it is worth bothering having a repository or undertaking the
proselytizing activities, except simply to have a repository in place (a
yes/no tick).

It is also useless to look at growth rates of documents in the repository
without taking their publication and deposit dates into account. The
evidence shows that many 'converted' depositors busy themselves with
mounting all their old papers. This is not to be discouraged and makes
repository managers think they are achieving something, but it is not a
significant performance indicator. The only important performance indicator
is 'How much of your institution's annual research output appears in your
repository by (say) 6 months after year end?'

The Patchwork Mandate

So, many repository managers find themselves between a rock and a hard
place. They can't convince the senior executives to bring in a mandate, and
they know that voluntary deposition does not work. Fortunately there may be
a middle way or even a transitional way ahead. I call it the patchwork
mandate for reasons that will become obvious. Unfortunately we don't have
any evidence yet that this policy works on an institutional scale, though
there are significant pointers to indicate that it will.

So what is the patchwork mandate? Simply this:

1        Knowing that you have been unable to convince the senior
executives, you nevertheless personally commit to having a mandate across
your institution.

2        You aim to pursue a strategy that will achieve an institutional
mandate in the long term. It is highly recommended that you register your
intention to do this in ROARMAP so as to encourage other repository managers
caught in the same dilemma.

3        Since you can't get an institutional mandate, you work towards
getting departmental (school/faculty) mandates one by one. Each departmental
mandate will rapidly trend towards 100% and needs little activism to
maintain this level. 

Let's look at this a bit more closely. We have solid evidence that
departmental mandates work, and much faster than university-wide mandates. A
year or so suffices to achieve a substantial acquisition rate of current
research. This is because there are fewer people involved, and the
researchers tend to trust their leaders more. It is also easier to achieve
conversion at the departmental level. Two documented examples are ECS at
Southampton University and the School of Computing at the University of
Tasmania (mine). Again see
http://www.firstmonday.org/issues/issue11_10/sale/index.html.

What is a departmental mandate? A decision by the Head of Department (or a
Research Director or a democratic staff meeting) that all peer-reviewed
articles in the department must be deposited in the IR as a postprint, at
the time of acceptance. See
http://www.eprints.org/openaccess/policysignup/sign.php for a draft policy
you can adapt. Its effect is immediate, and most members of the department
comply quite easily. The 'enforcement' of the policy (if any is needed) is
in the hands of the responsible person of the department, and all it needs
is to watch what people claim they have published and ask "have you archived
that yet?" That is enough - no punitive action is required.

How do you achieve this? Well what you don't do is try a scatter-gun
approach across the institution. Nor only does it waste effort, but it puts
people's back up. You analyze all your departments and research centers. You
decide which senior people in them might be amenable to persuasion. A high
research profile is a good indicator, as is a discipline where online access
is already widespread. Another pointer is an area where a funding body
mandate is going to affect many people. You know your institution better
than I do, so choose your own criteria.

Then you concentrate on the leader of a department and possibly people
around him or her to firstly deposit their own current research, show them
what they can get out of it (for example download statistics), and then
persuade them that their whole department should deposit. Give them the
words to use. Suggest implementation. Provide support. Run seminars. Provide
monthly deposit data summaries. But all of this strictly targeted at the
selected department. Once you have a mandate from that department, keep up
your support, publicize successes across the institution, and move on to the
next target. Of course you might tackle a few targets at the same time, but
not too many. Successful departmental mandates are what you are after..

You will end up with an odd collection of mandated departments, and the rest
being voluntary. Hence the term patchwork mandate, like a calico or
tortoiseshell cat. You won't achieve 100% deposit rates yet, but you may
begin to escape from the 20% ceiling of voluntary deposit.

When you as repository manager have (say) 40-50% of the departments with
departmental mandates, go back and argue with your senior executives. If
they still don't agree to bring in an institutional mandate, tell them that
you are going to tackle the remaining more difficult departments, and that
they (the executives) are now looking like very silly neo-Luddites. Carry
out your promise if you do say that.

Conclusion

I think that the patchwork mandate strategy will probably work. We are
trialing it in Australia. It won't achieve 100% content instantly, but it is
a clear way to work towards that. You can even explain it to your senior
executives and they probably won't stop you. They may even encourage you to
try it. 

Just remember that voluntary persuasion of individuals is known not to work
beyond a pitiful participation level. Self-archiving needs to be made part
of the routine academic duty, and this requires a policy endorsement by
someone.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
April 2024
January 2024
December 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
February 2023
January 2023
December 2022
February 2022
December 2021
October 2021
September 2021
August 2021
May 2021
September 2020
October 2019
March 2019
February 2019
August 2018
February 2018
December 2017
October 2017
September 2017
August 2017
June 2017
April 2017
March 2017
February 2017
January 2017
November 2016
August 2016
July 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
September 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
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996


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