<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Research Tools on Po-Wei Chen, MD — Physiatrist &amp; Builder</title><link>https://drpwchen.com/en/tags/research-tools/</link><description>Recent content in Research Tools on Po-Wei Chen, MD — Physiatrist &amp; Builder</description><image><title>Po-Wei Chen, MD — Physiatrist &amp; Builder</title><url>https://drpwchen.com/og-default.png</url><link>https://drpwchen.com/og-default.png</link></image><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 14 Jul 2026 08:15:00 +0800</lastBuildDate><atom:link href="https://drpwchen.com/en/tags/research-tools/index.xml" rel="self" type="application/rss+xml"/><item><title>The last piece of The Paper Trilogy: paper-fetch. Give it a DOI, and it fetches the full text itself</title><link>https://drpwchen.com/en/posts/paper-fetch/</link><pubDate>Tue, 14 Jul 2026 08:15:00 +0800</pubDate><guid>https://drpwchen.com/en/posts/paper-fetch/</guid><description>To let AI read papers for you, you first need the full text. And what usually gets you stuck isn&amp;#39;t the AI—it&amp;#39;s permissions, publishers, and the library. paper-fetch uses a step-by-step route from open access, to official publisher APIs, to your own hospital library to turn a DOI into a full-text PDF, without taking any piracy routes.</description></item></channel></rss>