<commit_before><head>
  <title>Shareyourpaper.org Permissions</title>

  <link rel="stylesheet" href="/static/oabutton_rebrand.css"> <!-- gets the new css (still also uses the old css, just overwrites where necessary) -->
  <meta name="description" content="Sharing should be simple. We make sure that deposit into your repository means only dragging and dropping a paper by automatically doing all the hard work for depositors." />
</head>


<style>
  #topnav {
    display: none;
  }
  #footer {
    display: none;
  }

  h2{
    color:#428BCA;
    text-align: left;
  }

  .btn-demo-white{
    color:#428BCA !important;
  }


  .footer{
    color: #428BCA !important;
    padding: 0;
  }
  .footer a{
    color: #428BCA;
  }
  .footer a:hover{
    color:#608891;
  }
  .footer p{
    padding:0;
    margin:0;
  }

  .p {
    line-height: 1.5;
  }

  .li {
    line-height: 1.5;
  }

</style>


<!-- header -->
<div class="blue-bg">
  <div class="center-col header">
    <div><span><strong><a href="/permissions">Shareyourpaper.org Permissions</a></strong> by <a href="https://openaccessbutton.org" style="color:white">Open Access Button</a></span></div>
    <div>
      <!-- <a class="btn btn-demo-white notonsmallphones" href="/permissions/about">About</a> -->
    </div>
  </div>
</div>


<div class="container-fluid">
  <div class="row">
    <div class="col-md-6 col-md-offset-3">
      <h1 style="text-align:left;margin-top:35px;margin-bottom:25px;font-size:4em;">
        About
      </h1>
      <p>
        <!-- TODO: add a couple of sentances here  -->
        Jump to:
      </p>
        <ul>
          <li><a href="#howitworks" class="blue">How it works</a></li>
          <li><a href="#contributing" class="blue">Contributing</a></li>
          <li><a href="#api" class="blue">API Docs</a></li>
          <li><a href="#schema" class="blue">Schema</a></li>
          <li><a href="#data" class="blue">Data Download</a></li>
          <li><a href="#code" class="blue">Code</a></li>
          <li><a href="#roadmap" class="blue">Roadmap</a></li>
          <li><a href="#disclaimer" class="blue">Disclaimer</a></li>
          <li><a href="#contact" class="blue">Contact</a></li>
        </ul>

      <h1 id="howitworks">How it works</h1>
      <p>
        Information on how it works can be found <a href="/permissions#howitworks">here on the homepage</a>, and more specifics, e.g the schema can be found on this page. If you’d like to know more, <a href="mailto:<EMAIL>">send us a question</a> and we’ll happily get back to you asap.
      </p>

      <h1 id="contributing">Contributing</h1>
      <!-- TODO: I don't like this section generally -->
      <p>
        Thanks so much for making it this far! There are three major ways we need the community to help, but before you do please <a href="https://docs.google.com/forms/d/e/1FAIpQLSfHEYlQYogYhdS7nXajM68cd2pMbKwJSahcr-NP9vVL-dzzYA/viewform">let us know who you are</a>:
      </p>
        <ul>
          <li>Contribute individual policies: If you find we don’t have a policy you know, you can <a href="https://docs.google.com/forms/d/e/1FAIpQLSd0_nEfBN142m-oW7t1AzVJVhh09LeYMEJsooNLIOFYpA6Byw/viewform?usp=sf_link">contribute it here</a>.</li>
          <!-- TODO: the below needs revision -->
          <li>Review policies: When new policies are submitted, they need to be reviewed by one other person for verification. But, policies also change, so we ensure all policies are archived when submitted and automatically monitor important policies for changes, with others are manually reviewed by the community regularly. We’d like your support, so there is a feed of policies that need review, and a way to review them here: Coming Soon.</li>
          <li>Contribute in bulk: If you have a list of policies locally you think we could use, we’d love to work with you to include them. <a href="mailto:<EMAIL>">Get in touch</a>.</li>
        </ul>
      <p>
        We’ll accept contributions from anyone; however, we’ll ask you to <a href="https://docs.google.com/forms/d/e/1FAIpQLSfHEYlQYogYhdS7nXajM68cd2pMbKwJSahcr-NP9vVL-dzzYA/viewform">identify who you are</a> and source your information. We recommend contributing only if you are intimately familiar with what you’re contributing to, e.g. you’re a trained scholarly communications practitioner (or trained by one) or a journal editor / publisher.
        <br>
        <br>
        Your contribution will be licensed openly, CC-0, and attributed to you. At any point, you can get your contribution back by downloading the data.
      </p>

      <h1 id="api">API Docs</h1>
      <!-- TODO: - I know this is a draft but maybe finding a way to tidy up a little how API docs are displayed?  -->
      <p>
        Our free REST JSON API provides programmatic access to Shareyourpaper.org Permissions.
        <br>
        <br>
        The API gives responses as shown in the Schema, however, most fields should be straightforward to understand without it.
        <br>
        <br>
        You don’t need to authenticate to use the API, but if you’re going to rely on it we recommend joining the mailing list to get updates.
        <br>
        <br><commit_msg>adding more info to about from old blog<commit_after><head>
  <title>Shareyourpaper.org Permissions</title>

  <link rel="stylesheet" href="/static/oabutton_rebrand.css"> <!-- gets the new css (still also uses the old css, just overwrites where necessary) -->
  <meta name="description" content="Sharing should be simple. We make sure that deposit into your repository means only dragging and dropping a paper by automatically doing all the hard work for depositors." />
</head>


<style>
  #topnav {
    display: none;
  }
  #footer {
    display: none;
  }

  h2{
    color:#428BCA;
    text-align: left;
  }

  .btn-demo-white{
    color:#428BCA !important;
  }


  .footer{
    color: #428BCA !important;
    padding: 0;
  }
  .footer a{
    color: #428BCA;
  }
  .footer a:hover{
    color:#608891;
  }
  .footer p{
    padding:0;
    margin:0;
  }

  .p {
    line-height: 1.5;
  }

  .li {
    line-height: 1.5;
  }

</style>


<!-- header -->
<div class="blue-bg">
  <div class="center-col header">
    <div><span><strong><a href="/permissions">Shareyourpaper.org Permissions</a></strong> by <a href="https://openaccessbutton.org" style="color:white">Open Access Button</a></span></div>
    <div>
      <!-- <a class="btn btn-demo-white notonsmallphones" href="/permissions/about">About</a> -->
    </div>
  </div>
</div>


<div class="container-fluid">
  <div class="row">
    <div class="col-md-6 col-md-offset-3">
      <h1 style="text-align:left;margin-top:35px;margin-bottom:25px;font-size:4em;">
        About
      </h1>
      <p>
        To learn more about Shareyourpaper.org Permissions jump to:
      </p>
        <ul>
          <li><a href="#background" class="blue">What is permissions checking</a></li>
          <li><a href="#howitworks" class="blue">How it works</a></li>
          <li><a href="#contributing" class="blue">Contributing</a></li>
          <li><a href="#thanks" class="blue">Thanks</a></li>
          <li><a href="#api" class="blue">API Docs</a></li>
          <li><a href="#schema" class="blue">Schema</a></li>
          <li><a href="#data" class="blue">Data Download</a></li>
          <li><a href="#code" class="blue">Code</a></li>
          <li><a href="#roadmap" class="blue">Roadmap</a></li>
          <li><a href="#disclaimer" class="blue">Disclaimer</a></li>
          <li><a href="#contact" class="blue">Contact</a></li>
        </ul>

        <h1 id="background">What is permissions checking</h1>
        <p>
          It’s understanding what version of your work you can deposit, where, how, and when. Depending on when you published, with which publisher, which journal, and at which institution in which country, the answer can be quite different. Figuring this out is known as permissions checking, and it’s one of the biggest hurdles when self-archiving. While we don’t talk about it much as a community, getting it right and making it easy stands between us and a transformation in how self-archiving is done. For authors and librarians alike (and the tools they use), permissions checking is a complex and slow task, and there isn’t enough tooling to help digest the myriad policies into clear answers.
        </p>

      <h1 id="howitworks">How it works</h1>
      <p>
        Information on how it works can be found <a href="/permissions#howitworks">here on the homepage</a>, and more specifics, e.g the schema can be found on this page. If you’d like to know more, <a href="mailto:<EMAIL>">send us a question</a> and we’ll happily get back to you asap.
      </p>

      <h1 id="contributing">Contributing</h1>
      <!-- TODO: I don't like this section generally -->
      <p>
        Thanks so much for making it this far! There are three major ways we need the community to help, but before you do please <a href="https://docs.google.com/forms/d/e/1FAIpQLSfHEYlQYogYhdS7nXajM68cd2pMbKwJSahcr-NP9vVL-dzzYA/viewform">let us know who you are</a>:
      </p>
        <ul>
          <li>Contribute individual policies: If you find we don’t have a policy you know, you can <a href="https://docs.google.com/forms/d/e/1FAIpQLSd0_nEfBN142m-oW7t1AzVJVhh09LeYMEJsooNLIOFYpA6Byw/viewform?usp=sf_link">contribute it here</a>.</li>
          <!-- TODO: the below needs revision -->
          <li>Review policies: When new policies are submitted, they need to be reviewed by one other person for verification. But, policies also change, so we ensure all policies are archived when submitted and automatically monitor important policies for changes, with others are manually reviewed by the community regularly. We’d like your support, so there is a feed of policies that need review, and a way to review them here: Coming Soon.</li>
          <li>Contribute in bulk: If you have a list of policies locally you think we could use, we’d love to work with you to include them. <a href="mailto:<EMAIL>">Get in touch</a>.</li>
        </ul>
      <p>
        We’ll accept contributions from anyone; however, we’ll ask you to <a href="https://docs.google.com/forms/d/e/1FAIpQLSfHEYlQYogYhdS7nXajM68cd2pMbKwJSahcr-NP9vVL-dzzYA/viewform">identify who you are</a> and source your information. We recommend contributing only if you are intimately familiar with what you’re contributing to, e.g. you’re a trained scholarly communications practitioner (or trained by one) or a journal editor / publisher.
        <br>
        <br>
        Your contribution will be licensed openly, CC-0, and attributed to you. At any point, you can get your contribution back by downloading the data.
      </p>

      <h1 id="thanks">Thanks</h1>
      <ul>
        <li><NAME> and <NAME> at the University of Pennsylvania Libraries, whose work on the University of Pennsylvania’s Publisher Policy Database and structured permissions workflow served as essential sources and templates for this work. Their constant review and consultation were also essential.</li>
        <li><NAME>, who provided substantial review, also generously gave his time to talk us through properly utilizing universities policies, and his careful documentation of them enabled their inclusion.</li>
        <li><NAME>, <NAME>, <NAME>, <NAME>, <NAME>, <NAME>, <NAME>, <NAME>, and <NAME>, who provided substantial review and ideas at an early stage.</li>
        <li><NAME>, <NAME>, and <NAME>, who provided review of at an early stage.</li>
        <li><NAME>, who manages the Open Access Button Request System. We'd also like the thank alumni of the team. Notably, <NAME> and <NAME>, who taught us how to perform permissions checking.</li>
        <li>The work of SHERPA/RoMEO and ROARMAP, who continue to contribute immensely to this area.</li>
      </ul>
      <h1 id="api">API Docs</h1>
      <!-- TODO: - I know this is a draft but maybe finding a way to tidy up a little how API docs are displayed?  -->
      <p>
        Our free REST JSON API provides programmatic access to Shareyourpaper.org Permissions.
        <br>
        <br>
        The API gives responses as shown in the Schema, however, most fields should be straightforward to understand without it.
        <br>
        <br>
        You don’t need to authenticate to use the API, but if you’re going to rely on it we recommend joining the mailing list to get updates.
        <br>
        <br>
{'fraction_non_alphanumeric': 0.12416619786225187, 'fraction_numerical': 0.01060837418628948, 'mean_word_length': 3.115079365079365, 'pattern_counts': {'":': 0, '<': 290, '<?xml version=': 0, '>': 290, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3424780', 'n_tokens_mistral': 3896, 'n_tokens_neox': 3755, 'n_words': 1382}