<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Scholarly-Communication on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/scholarly-communication/</link>
    <description>Recent content in Scholarly-Communication on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 09 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/scholarly-communication/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Preprint Repositories: OSF Preprints vs OPS vs EPrints</title>
      <link>https://www.pistack.xyz/posts/2026-06-09-self-hosted-preprint-repositories-osf-ops-eprints/</link>
      <pubDate>Tue, 09 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-09-self-hosted-preprint-repositories-osf-ops-eprints/</guid>
      <description>&lt;p&gt;The traditional academic publishing pipeline is slow, expensive, and gated behind paywalls. Preprint servers have emerged as a powerful alternative — letting researchers share findings immediately, before formal peer review, at zero cost to readers. While mega-servers like arXiv, bioRxiv, and SSRN dominate the landscape, there are compelling reasons to run your own institutional or community preprint repository. In this guide, we compare three open-source, self-hosted preprint platforms: &lt;strong&gt;OSF Preprints&lt;/strong&gt;, &lt;strong&gt;Open Preprint Systems (OPS)&lt;/strong&gt;, and &lt;strong&gt;EPrints&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
