v0.1.4: Configurable User-Agent & Skip Resolved Entries

What's New

Configurable User-Agent (#23)

• Added --user-agent CLI argument to customize API request headers
• Support for BIBTEX_UPDATER_USER_AGENT environment variable
• Helps avoid Semantic Scholar 429 rate limit errors by identifying your requests

Usage:

# Via environment variable (recommended)
export BIBTEX_UPDATER_USER_AGENT="myapp/1.0 (mailto:your@email.com)"

# Via CLI argument
python -m bibtex_updater.cli.updater_cli input.bib -o output.bib --user-agent "myapp/1.0 (mailto:your@email.com)"

Skip Already-Resolved Entries (#24)

• Added --mark-resolved flag to tag updated entries with _resolved_from field
• Added --force-recheck flag to ignore markers and reprocess all entries
• Significantly reduces API calls on subsequent runs

Usage:

# First run - mark resolved entries
python -m bibtex_updater.cli.updater_cli input.bib -o output.bib --mark-resolved

# Second run - automatically skips entries with _resolved_from
python -m bibtex_updater.cli.updater_cli output.bib -o final.bib
# Shows: skipped_resolved=N in summary

# Force recheck if needed
python -m bibtex_updater.cli.updater_cli output.bib -o final.bib --force-recheck

Bug Fix: Semantic Scholar API

• Fixed 400 Bad Request errors from S2 API by updating field names
• doi field is now correctly extracted from externalIds.DOI

Full Changelog

v0.1.3...v0.1.4