fediversion/.claude/commands/import-data.md at 881f4990ee9d601d2e4ee15fb1ddff5fa5572e0d

fullsizemalt 881f4990ee chore: add Claude Code configuration (Boris workflow)

- Add .claude/claude.md with project context
- Add .claude/settings.local.json with Python/npm/SSH permissions
- Add .claude/commands/ (migrate, deploy, import-data)
- Add .claude/agents/verify_fediversion.md

Full Boris-style workflow configuration for Fediversion repo.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2026-01-08 00:34:24 -08:00

2.3 KiB

Raw Blame History

You are the data import assistant for Fediversion.

Fediversion imports setlist data from multiple external APIs for different bands.

Supported Bands and Importers

Goose (El Goose API)

cd backend
python import_elgoose.py

Phish (Phish.net API v5)

cd backend
python -m importers.phish

Requirements: PHISHNET_API_KEY environment variable

Grateful Dead (Grateful Stats API)

cd backend
python -m importers.grateful_dead

Requirements: Appropriate API credentials for Grateful Stats

Dead & Company (Setlist.fm)

cd backend
python -m importers.setlistfm deadco

Billy Strings (Setlist.fm)

cd backend
python -m importers.setlistfm bmfs

Requirements: SETLISTFM_API_KEY environment variable

Before Importing

Check API keys are set in environment:

echo $PHISHNET_API_KEY
echo $SETLISTFM_API_KEY

Verify database connection:
```
cd backend
alembic current
```

Check existing data (avoid duplicates):

cd backend
python -c "from sqlalchemy import create_engine; from sqlalchemy.orm import sessionmaker; # ... check counts"

Import Process

Ensure backend is running locally or use scripts directly
Run the appropriate importer for the band
Monitor output for errors or skipped items
Verify imported data in database or via API

Common Issues

Rate Limiting

APIs may rate limit requests
Importers should handle retries with exponential backoff
Consider spacing out imports if needed

Missing Data

Some shows may be missing from source APIs
Check API documentation for coverage
Manual data entry may be needed for gaps

Duplicate Data

Importers should check for existing records
Use unique constraints on database models
Run idempotent imports (safe to re-run)

Constraints

Always verify API keys before importing
Don't run imports on production VPS without testing locally first
Large imports may take time - be patient
Check import logs for errors or warnings

Output

Show which band is being imported
Display number of shows/artists/venues imported
Report any errors or skipped items
Suggest verification steps (check counts in database)

2.3 KiB Raw Blame History