<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jayesh Thar</title>
    <description>The latest articles on DEV Community by Jayesh Thar (@jayeshthar).</description>
    <link>https://dev.to/jayeshthar</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2612257%2Fdeda7b23-7599-4a36-9554-f0cc771405bc.png</url>
      <title>DEV Community: Jayesh Thar</title>
      <link>https://dev.to/jayeshthar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jayeshthar"/>
    <language>en</language>
    <item>
      <title>Researcher Campus: An AI Pipeline That Replaces 5 Research Tools with One Workflow</title>
      <dc:creator>Jayesh Thar</dc:creator>
      <pubDate>Thu, 17 Sep 2026 19:15:32 +0000</pubDate>
      <link>https://dev.to/jayeshthar/researcher-campus-an-ai-pipeline-that-replaces-5-research-tools-with-one-workflow-4c5o</link>
      <guid>https://dev.to/jayeshthar/researcher-campus-an-ai-pipeline-that-replaces-5-research-tools-with-one-workflow-4c5o</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/mlh-hackathon"&gt;MLH x DEV Writing Challenge&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Researcher Campus&lt;/strong&gt; — a full-stack, AI-powered academic research pipeline that replaces 5+ disconnected research tools (novelty checkers, citation managers, compliance checklists, drafting tools) with a single 7-stage workflow: novelty check → gap analysis → manuscript drafting → compliance audit.&lt;/p&gt;

&lt;p&gt;The core problem: researchers waste hours jumping between tools to check if their idea is novel, find literature gaps, draft a proposal, and then manually verify it meets submission standards. Researcher Campus automates that entire chain.&lt;/p&gt;

&lt;p&gt;Key pieces:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A &lt;strong&gt;real-time novelty-detection engine&lt;/strong&gt; that queries 5 academic APIs simultaneously (Crossref, arXiv, OpenAlex, Semantic Scholar, Europe PMC) and compares results using 768-dimension vector embeddings, with a TF-IDF fallback for offline/degraded scenarios&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;5-tier Gemini fallback chain&lt;/strong&gt; with auto-failover, so proposal generation doesn't break if one model tier is rate-limited or down&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;4-guard compliance auditor&lt;/strong&gt; checking citations, anonymity, formatting, and tone before submission&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;🔗 Live: &lt;a href="https://researcher-campus.vercel.app/" rel="noopener noreferrer"&gt;researcher-campus.vercel.app&lt;/a&gt;&lt;br&gt;
💻 Code: &lt;a href="https://github.com/jayesh-thar/Researcher-Campus" rel="noopener noreferrer"&gt;github.com/jayesh-thar/Researcher-Campus&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8l3cfcw2km14s9pnv2nl.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8l3cfcw2km14s9pnv2nl.png" alt=" " width="800" height="972"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Tech Stack
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Backend:&lt;/strong&gt; 31 REST endpoints, JWT auth, AES-256-GCM encryption, ~7,000 req/sec sustained with 0 errors under load&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Infra:&lt;/strong&gt; Docker on AWS ECS Fargate, provisioned via Terraform, GitHub Actions CI/CD&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data:&lt;/strong&gt; MongoDB + an RDS-based audit-logging layer&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quality:&lt;/strong&gt; 21 automated tests, 0 TypeScript errors&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Hackathon Experience
&lt;/h2&gt;

&lt;p&gt;I didn't build this at a live hackathon — Researcher Campus started as a personal problem I kept running into: jumping between five different tools just to check if a research idea was novel. After digging into how existing tools approached this, I decided to build the whole pipeline myself, solo, working online at my own pace.&lt;/p&gt;

&lt;p&gt;The hardest part wasn't the code — it was the &lt;em&gt;design&lt;/em&gt;. Figuring out how to structure a 7-stage pipeline (novelty check → gap analysis → drafting → compliance audit) that actually made sense end-to-end took a long time to get right. I went through several rounds of redesigning the flow before it clicked — moving stages around, rethinking what should run in parallel versus sequentially, and figuring out where the compliance checks actually needed to sit in the pipeline.&lt;/p&gt;

&lt;p&gt;That one design problem taught me more about system architecture than writing the actual features did.&lt;/p&gt;

</description>
      <category>mlhacks</category>
      <category>ai</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
