Difference between revisions of "Best practices for university OA policies"

From Harvard Open Access Project
Jump to navigation Jump to search
Line 133: Line 133:
== Incentivizing deposits in the repository ==
== Incentivizing deposits in the repository ==
* '''Example'''
* '''Short headline in bold'''
** '''notes'''
** notes not in bold
== Talking about a policy ==
== Talking about a policy ==

Revision as of 15:48, 30 April 2012

  • This is a guide to best practices for university OA policies.
  • The doc is under way but far from complete. All the entries to date are tentative. Undecided questions are marked with three slashes (///).
  • To do list
    • Find and remove all cases of the three slashes (///).
    • Elaborate each entry with some rationale, including (as far as possible) links to literature and evidence.
    • Decide whether to make all or some of it public.
    • Decide whether the public version will stay here (the HOAP wiki) or move to another location and perhaps another format.
    • Decide how to indicate the growth and evolution of our recommendations. (I suggest version numbers and release dates.)
    • Decide who is authorized to revise this doc. (At the moment, it's just the HOAP principals.)
    • Before release, get other key partners to make their own suggestions and sign on to the result, e.g. SPARC, EOS, EIFL, MIT.
      • Make offer to COAPI, for courtesy; but don't expect sign-on since it (deliberately) wants to be hospitable to institutions with any kind of policy, strong or weak
    • Consider writing an executive summary of the guide, for rapid orientation or busy committees. Or consider making two editions, a short one for busy committees and a full-length version for everyone else.
    • Consider including a (dynamic) section on frequently asked questions and frequently heard objections and misunderstandings
    • Investigate tools for making nice printouts of wiki pages, or tools for translating wikis into other formats (e.g. PDF) for printing; as far as possible, built those tools into the best-practices guide
    • Eventually make a second guide for funder policies. It could be a separate doc, or it could be a new section of this doc ("Follow all the recommendations above but with these subtractions and additions based on the different circumstances of universities and funders").

Drafting a policy

  • Grant of rights to the institution
    • The policy should be worded so that the faculty vote adopting the policy thereby grants the university certain non-exclusive rights to their future publications. It should not merely ask/encourage/require faculty to retain certain rights when they sign future publishing contracts.
  • Deposit in the repository
    • The policy should require faculty to deposit a certain version of their future journal publications in the institutional repository.
    • The version to be deposited is the final version of the peer-reviewed manuscript, incorporating all revisions made during the peer-review process.
  • Deposit timing
    • Faculty should deposit their peer-reviewed manuscripts at the time of acceptance for publication.
    • If the policy respects an embargo decision (from the author or publisher), the deposit should still be made at the time of acceptance. But it will be a dark deposit until the embargo period runs.
  • Waiver option
    • The waiver option should apply only to the grant of rights to the institution (also called the license or the permission), not to the deposit requirement.
    • The policy should make clear that the institution will grant waivers no questions asked. Faculty needn't offer a justification that might be accepted or rejected. To prevent needless fear or confusion on this point, the policy should refer to "obtaining" rather than "requesting" a waiver.
    • A given waiver should apply to a given publication. The policy should not allow standing waivers; that would defeat the purpose of shifting the default to permission for OA. Faculty who wish to do so may obtain separate waivers for separate publications.
    • A waiver for a particular article means that the institution does not receive the policy's usual bundle of non-exclusive rights for that article. Hence, for that article the university will not have permission from the policy to make a copy OA. But the university may have permission from another source, such as the publisher, to make a copy OA. For example, if the publisher allows green OA six months after publication, then the university has OA permission from the publisher even if it doesn't have OA permission under the policy. If the university has a copy of the article as a dark deposit in the repository, then it may make the repository copy OA as soon as the publisher allows. Hence, the waiver provision of the policy should not promise that the university will not make a copy OA. The waiver provision needn't mention any of these complexities, provided it doesn't misrepresent what a waiver is or does.
  • Scope of coverage, by content category
    • The policy can require deposit for some kinds of content (e.g. manuscripts published in peer-reviewed journals) and encourage deposit of other kinds (e.g. conference presentations, books or book chapters, datasets, theses and dissertations).
  • Scope of coverage, by time
    • Neither the grant of rights nor the deposit requirement should be retroactive. But the policy might encourage deposit of works published prior to the adoption of the policy.
  • Licensing
    • Institutions with Harvard-style policies have the rights needed to put open licenses (such as CC-BY) on faculty works deposited under the policy. But they need not take advantage of those rights, or need not do so right away.
  • Transferring rights back to the author
    • The Harvard policy not only transfers rights to the institution, but allows the institution to transfer rights to others. Here's the key language: "More specifically, each Faculty member grants to [university name] a nonexclusive, irrevocable, worldwide license to exercise any and all rights under copyright relating to each of his or her scholarly articles...provided that the articles are not sold for a profit, and to authorize others to do the same."
    • The primary purpose of this language is to allow the institution to transfer rights back to the author. The effect is that authors retain (or regain) rights to their work, including rights that they transferred away in their publishing contracts.
    • ///Have I understood this correctly? Is it fair to say that authors retain/regain all rights to their work, or all rights except the right to allow commercial use?
  • Implementation
    • The policy should include a provision giving a certain committee or unit responsibility for implementing the policy.
    • All in all, the policy should be minimal and say only what it absolutely must say. The rest can be left to the committee or unit implementing the policy.
  • Separating the issues
    • A university with a green OA policy may (and we think, should) also launch a fund to help faculty pay publication fees at fee-based OA journals. But the green OA policy should make clear that it is separate from the journal fund. Otherwise faculty may think that the policy itself requires faculty to submit new work to OA journals (a common and harmful misunderstanding).
    • A university requiring green OA may also encourage gold OA. But it should be careful about doing both the same document. Where it has been tried, faculty too easily come to believe that the policy requires gold OA.
    • Some other recommendations on separating the issues are included below under Adopting a policy ("Educating faculty about the policy before the vote"). But certain explanations belong in the policy itself, to help deter misunderstandings.

Adopting a policy

  • Adopting authority
    • The policy should be adopted by the faculty, not the administration.
    • Campus entrepreneurs leading the campaign for a policy should be faculty. If the idea and initial momentum came from librarians or administrators, they should find faculty members willing to lead the effort.
  • Educating faculty about the policy before the vote
    • Make clear that the policy requires deposit in an OA repository, not submission to an OA journal. (It's about green OA, not gold OA.) It does not limit faculty freedom to submit work to the journals of their choice.
    • Make clear that the waiver option guarantees that faculty are free to decide for or against OA for every one of their publications. The policy merely shifts the default from non-deposit and non-OA to deposit and OA.
    • Make clear that "softening" the policy to opt-in is pointless. All institutions without opt-out policies already have opt-in policies.
    • Make clear that the waiver option also gives publishers the right to require a waiver as a condition of publication. Hence, publishers who decide that the costs exceed the benefits may protect themselves, at will, and may do so without refusing to publish faculty at institutions with OA policies. Hence, faculty who worry about protecting certain vulnerable publishers, such as society publishers, should understand that the policy already gives those publishers the means to protect themselves, if they see the need to do so. Faculty needn't paternalize those publishers by voting down the policy, and they needn't decide on the publisher's behalf that publishing authors without waivers would harm. However, faculty should explain to the publishers they wish to protect that the waiver option provides all the protection they need. Many publishers do not understand that.
    • Also see the recommendations on Talking about a policy.

Implementing a policy

  • Individualized writing
    • Under US copyright law (17 USC 205.e) a "nonexclusive license...prevails over a conflicting transfer of copyright ownership if the license is evidenced by a written instrument signed by the owner of the rights licensed or such owner's duly authorized agent." Hence, universities implementing the kind of policy recommended here --granting non-exclusive rights to the institution-- should ask authors to sign a "written instrument" affirming the policy. When authors sign such a statement, the grant of rights embodied in the policy will prevail over a later publishing contract inconsistent with the policy.
    • This provision doesn't say that in the absence of a written instrument, the nonexclusive license will not prevail over a later contract inconsistent with the policy. A university may take the position that the nonexclusive license in the policy will prevail in any case, and probably never have to test its position in court. But to be safe, it's best to get a written affirmation of the grant of rights (or license) as specified by 17 USC 205.e.
    • At Harvard, articles enter the repository by two paths: a faculty member may deposit articles directly or an assistant may deposit an article on behalf of a faculty member. In the former case, one dialog box in the deposit process asks the faculty member to affirm the grant of rights (the license) in the policy. In the latter case, Harvard asks the faculty member to sign an assistance authorization form containing an affirmation of the grant of rights. When new faculty are hired, they are asked to sign a form affirming the grant of rights as well. These forms count as a written instrument for the purpose of 17 USC 205.e.
  • Facilitating deposits
    • If the budget permits, the institution should train student workers to make deposits on behalf of faculty.
    • The repository should make traffic data available to authors. Evidence suggests that this encourages deposits.
    • The repository should publicize the "most viewed" or "most downloadaded" articles, and the "most viewed" departments, e.g. on the repository front page or in a regular column in the school newspaper.
  • Facilitating waivers
    • The institution should create a web form through which faculty can obtain waivers. This not only streamlines bookkeeping, but proves to faculty that the process is easy and automatic. Harvard can share code for such a web form (true?///).
    • Some publishers may require faculty to obtain a waiver as a condition of publication. Institutions should not try to prevent this. Accommodating these publisher policies proves that publishers have the means to protect themselves, if they choose to use them; and that fact makes it unnecessary for faculty to protect or "paternalize" their favorite publishers (e.g. society publishers) by refusing to vote for a policy. On the other hand, the institution may want to talk with publishers who take this position, to see whether they can work out an accommodation. For example, it is better for the institutional to provide OA under an embargo than for the author to obtain a waiver.
  • Author addenda
    • ///sense in which they are not necessary; sense in which they are desirable anyway; how to talk about this without creating fear or intimidation; stressing that no negotiation with publishers needed; risks of transferring away all rights without obtaining a waiver
  • Multiple deposits
    • If a faculty member deposits a paper in a non-institutional repository (e.g. arXiv, PubMed Central, SSRN), the repository should harvest a copy. To avoid diluting the traffic numbers at the several repositories, all should comply with the (evolving) PIRUS standards for sharing traffic data.
    • If a faculty member is subject to two OA policies (e.g. one from the institution and one from the funder), the institution should offer to make the deposit required by the funder. For example, most faculty at Harvard Medical School are subject to the NIH policy; if they deposit in the HMS repository, then HMS will insure that a copy is deposited in PubMed Central. If faculty think that an institutional policy will double their administrative burden, they will vote against it; the institution should make clear that a local policy will actually reduce their burden.
  • Dark deposits
    • If a deposit is dark (not yet OA), at least the metadata should be OA.
    • If the repository software will support it, dark deposits should be set to open up automatically at the future date determined by the author decision or embargo period.
    • If an author deposited a manuscript and obtained a waiver, then the institution does not have permission to make it OA under the policy. But the repository should make the manuscript OA if it can obtain permission from another source, such as a standing policy of the publisher's to allow OA after a certain embargo period.
  • Repository indexing
    • The repository should be configured to support crawling by search engines.
    • Repository managers should check to see whether the contents are discoverable through major search engines, and follow-up any indexing failures.
  • Repository withdrawals
    • If a publisher sends a reasonable take-down request to the repository, the repository should always comply. (///But should the article be removed or merely go dark?)
    • If the author wishes to withdraw an article already on deposit (e.g. because it is mistaken, embarrassing, superseded by a newer version, etc.), then ///??
  • Content beyond the policy
    • The institution should welcome the deposit of types of scholarly content, above and beyond the type covered by the policy. For example, if the policy focuses on peer-reviewed manuscripts of journal articles, the repository should welcome deposit of other categories of scholarship as well, such as electronic theses and dissertations, books or book chapters, datasets, and digitized work from other media for which it has permission to provide OA. If the policy covers peer-reviewed manuscripts published after a certain date, it should welcome the deposit of peer-reviewed manuscripts completed or published before that date.
    • If the policy only gives the institution permission to make certain kinds of content OA, the repository should welcome dark deposits where it doesn't have permission for OA, and in those cases it should provide OA to the metadata.
  • Treaties with publishers
    • Some publishers may request certain dispensations, for example, that manuscripts published in their journals include a complete citation and link to the published edition. If the institution is comfortable acceding to the request, then it may ask something in return, for example, that the faculty will never need to obtain waivers to publish in the publisher's journals. These agreements may contain any provisions consistent with the policy and agreeable to both sides. (At Harvard they are called "treaties".)
  • Learning the denominator
    • An institution can easily tell how many articles are on deposit in its repository. But it cannot easily tell how many articles ought to be on deposit. If it wants to calculate the deposit rate (number deposited divided by number that ought to be deposited), then it must find a way to ascertain the denominator. This is a critical piece of information in measuring the effectiveness of the policy and its implementation.
    • Some institutions ask faculty to submit an annual list of their publications. If so, the information should be shared with the repository managers. The raw list of publications is less helpful than one broken down by categories, such as books, journal articles, and so on. If the policy only covers journal articles (for example), then the relevant denominator is the number of journal articles.

Incentivizing deposits in the repository

  • Short headline in bold
    • notes not in bold

Talking about a policy

  • "Compliance"
    • Harvard-style policies have three components: permission, waivers, and deposits. On the first component (permissions), compliance reaches 100% as soon as the policy is adopted. On the second component (waivers), campus leaders should acknowledge that faculty who obtain waivers are still complying with the policy. They are not violating the letter or spirit of the policy. The policy deliberately accommodates those who need or want waivers. The third component (deposits) often requires education, assistance, and incentives. But even though the deposit rate generally starts low and grows slowly, and occupies most of the attention of those charged with implementing a policy, it doesn't follow that the deposit rate is the only component of the compliance rate.
  • "Mandate"
    • If the word "mandate" suggests commands or coercion incompatible with academic freedom, then avoid the word "mandate". The policy recommended here is not implemented through commands or coercion. First, it is self-imposed by faculty vote. Second, it contains a waiver option and merely shifts the default. It would be a mistake to let the understandable desire to avoid the ugly implications of the word "mandate" lead faculty to defeat a policy that was not a mandate in the ugly sense. The kind of policy recommended here preserves faculty freedom to choose for or against OA for every publication.
    • ///quote from parts of PS short book; we may still want to emphasize that this kind of policy is stronger than a mere request or encouragement.
  • "Opt-out" and "opt-in"
    • A waiver option creates an "opt-out" policy. In that sense in "shifts the default" from lack of permission for OA to permission for OA. After a rights-retention policy is adopted, faculty who don't lift a finger are granting the institution permission to make their future work OA; if they want a different outcome, they must lift a finger and obtain a waiver. The fact that the policy merely shifts the default, and still allows an opt-out or waiver, means that it is not a "mandate" in at least one common sense of the term. The word "mandate" may suggest a kind of requirement deliberately omitted from the policy. (On the other side, the policy is considerably stronger than a mere request or encouragement, and English has few words other than "mandate" to describe such a policy.) The waiver option or opt-out means that faculty remain free to choose for or against OA for each of their publications. The default shift means that most faculty most of the time will choose for OA.
    • Some institutions adopt what they call "opt-in" policies. But in effect the institution already had an opt-in policy and didn't need to adopt a policy to give the faculty the right to opt in to OA. In that sense, the opposite of an "opt-out" policy is not an "opt-in" policy, but a no-waiver policy (which is stronger) or a non-policy (which is weaker).
  • "Waiver"
    • The university should make works in the repository OA whenever it has permission to do so. The policy is one source of permission. When a faculty member obtains a waiver for a given article, then the university does not have OA permission from the policy for that article. But if the university has permission from another source, such as the publisher, then it doesn't need permission from the policy. A waiver of the license or permission under the university policy doesn't waive the license or permission that the university may have from the publisher. Hence, no one should talk about waivers as if they flatly block OA permission for a given work. They only block OA permission from the policy, not from other sources such as the publisher.