
Heading Link Sync
Update heading links and embeds when you edit a heading.
Match CSV notices to notes for review.
MIT · no telemetry · core features free

The directory takes these platforms from the plugin manifest. The automated tests run in the desktop app only.
Directory facts fetched from community.obsidian.md/users/theluckystrike.
Researchers who maintain reference notes with DOI properties and need to review manuscripts against a local notice list.
Load a notice CSV from your vault and map its paper DOI, notice type and date columns. Retraction Review Queue matches reference properties and finds manuscripts through direct links or simple Pandoc citations.
Read the supplied notice before changing your argument. The list can be old or incomplete, and a match does not establish that a paper is unreliable.
Play demoLoad a vault CSV and choose its paper DOI, notice type and date columns. Invalid quoted rows and field counts produce warnings. The file limit is 20 MB.

DOIs compare without case after trimming and removal of supported DOI prefixes. Reference properties need one DOI string. The plugin does not fall back to titles or authors.
Direct native links and simple bracketed Pandoc keys connect manuscripts to matched references. Duplicate citekeys produce a warning and exclude citation matches through that key.

Expand Supplied notice row to read the source fields, then open the note and mark it checked after review. Changing the notice type, date or note path changes its checked identity.

CSV matching and checked state are free; saved column maps and local JSON reports need Pro.
Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.
Save the three column positions for a CSV path. Loading that path with Pro uses its saved map. Recheck the map when the column order changes.

Create a new JSON report in the vault root with warnings, supplied fields and checked states. The report includes the computed result beyond the view limit. It stays a snapshot after later reviews.

needs
steps
Put your notice CSV in the vault and add a DOI string to each reference note.
Add a citekey property if you use Pandoc citations.
Run Open review queue from the command palette.
Load your CSV, verify the columns and select Match notes.
Read warnings and supplied notice rows, open notes and mark reviewed items checked.
If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.
Need a change for your team? I build custom Obsidian plugins and features.
No. You supply the local CSV. Load it again after changing its source rows, then run Match notes.
No supplied DOI matched under your current column map and reference properties. It doesn't prove that your papers are safe or the list is current.
The view shows the first 500 review items. A Pro report includes the complete computed result.
No. Checked state goes into plugin data. Report export creates a separate JSON file.
No requests occur before you select Sign in with GitHub; sign-in sends a client ID, scope and device codes to github.com. After sign-in, api.github.com receives token-authenticated sponsorship queries for tier and payment totals; successful checks cache seven days, failures retry after six hours. Refresh requests an earlier check; notes, paths and vault data stay local, with no telemetry.
Tell me what is broken in Retraction Review Queue, or what it should do next.
Retraction Review Queue 1.1.0, MIT license
MIT · no telemetry · core features free