diagnose_institutional_access
Diagnose why institutional fulltext access fails or succeeds by testing direct, EZproxy, and OpenURL paths for a given DOI.
Instructions
Diagnose why institutional fulltext access succeeds or fails for an article.
Runs up to three probes and reports each path's outcome:
Direct fetch (Phase 1, IP-aware) — follows
https://doi.org/<doi>and classifies whether the publisher served fulltext, a paywall, or a login page. Works automatically when your network IP is on the publisher's institutional allow-list (campus / VPN).EZproxy fetch (Phase 2, BYO-cookie) — rewrites the publisher hostname to your library's EZproxy host and replays your exported browser session cookie. Configured via env vars:
EZPROXY_HOST(e.g.ezproxy.lib.ntu.edu.tw)EZPROXY_COOKIE_FILE(path to browser-exported cookies.json)EZPROXY_ENABLED=1
OpenURL handoff — generated for you to open manually in a browser when the automated paths fail.
Args: pmid: PubMed ID (used to enrich the OpenURL). doi: DOI (required for the direct + EZproxy probes). try_direct: Run the Phase 1 direct probe (default True). try_ezproxy: Run the Phase 2 EZproxy probe (default True).
Returns: Markdown report listing every probe's status, classification, and advice on the next action to take.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pmid | No | ||
| doi | No | ||
| try_direct | No | ||
| try_ezproxy | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |