| .github/workflows | ||
| addons | ||
| scripts | ||
| src/zotero_scraper | ||
| tests | ||
| .gitignore | ||
| LICENSE | ||
| main.py | ||
| pyproject.toml | ||
| README.md | ||
| requirements-dev.txt | ||
| requirements.txt | ||
Zotero Addons Scraper
This is a script repository for scraping Zotero add-ons, intended for use with Zotero Addons.
Switch to
addon-scrapersource in Zotero Addons to use this repository.
Workflows
This repository utilizes GitHub Actions workflow for automation. including the following steps:
- Retrieve Zotero add-on information specified in addons folder
- Parse add-on information into JSON data
- Publish the JSON data to the
publishbranch and the latest release - Validate changed addon tag metadata in CI
Contributing
Adding a new add-on entry {owner}@{repo} in the addons folder.
Optionally, add tags by writing JSON content to the file:
{"tags": ["reader"]}
Available tags:
| Tag | Description |
|---|---|
ai |
AI-powered features (summarization, chat, translation via LLM) |
metadata |
Metadata retrieval, citation counts, impact factor, formatting |
reader |
PDF reading experience, annotation, highlighting |
notes |
Note-taking, markdown export, knowledge management |
attachment |
File management, attachment organization, OCR |
interface |
UI enhancements, themes, column customization |
integration |
Integration with external services (Notion, Obsidian, Word, etc.) |
utility |
Zotero system tools (automation, deduplication, plugin management) |
Tag validation in CI
pull_requestonaddons/**: validates changed addon files against the allowed tag taxonomypushtomaster: validates changed addon files before the scraper publishes data- Each addon config must declare at least one tag, use only allowed tag values, avoid duplicates, and keep tags in canonical order
Usage
forkthis repository- Enable actions and scheduled workflow in
Actionspage of forked repository