Some checks failed
CI / Linting (Biome) (push) Failing after 40s
CI / Tests (push) Successful in 5m54s
CI / Type Check (adzuna-extractor) (push) Successful in 1m8s
CI / Type Check (gradcracker-extractor) (push) Successful in 1m11s
CI / Type Check (hiringcafe-extractor) (push) Successful in 1m8s
CI / Type Check (orchestrator) (push) Successful in 1m23s
CI / Type Check (startupjobs-extractor) (push) Successful in 1m6s
CI / Type Check (ukvisajobs-extractor) (push) Successful in 1m7s
CI / Documentation (push) Successful in 1m54s
Adds Arc.dev, BC T-Net, Eluta, iCIMS tenants, QAJobsBoard, and SmartRecruiters manifests with registry/settings/UI wiring; registers full extractor list in smoke-extractors and documents supplementary board access paths. Aligns Careerjet v4 with the url query parameter and fixes strict typing in QAJobsBoard. Co-authored-by: Cursor <cursoragent@cursor.com>
45 lines
2.1 KiB
Markdown
45 lines
2.1 KiB
Markdown
---
|
|
id: eluta
|
|
title: Eluta Extractor
|
|
description: Canadian job discovery via Eluta.ca public RSS feeds.
|
|
sidebar_position: 15
|
|
---
|
|
|
|
## What it is
|
|
|
|
Original site: [eluta.ca](https://www.eluta.ca)
|
|
|
|
The extractor lives in `extractors/eluta/manifest.ts`. It requests one or more public RSS URLs of the form `https://www.eluta.ca/rss?location=...`, parses items (title, employer, location, link, description), filters by pipeline search terms, and merges feeds while de-duplicating by `guid` / URL.
|
|
|
|
## Why it exists
|
|
|
|
Eluta surfaces Canadian roles indexed directly from employer career sites, often with less aggregator noise than generic job search. RSS provides a stable, low-auth integration compared to scraping HTML.
|
|
|
|
## How to use it
|
|
|
|
1. Choose **location strings** Eluta accepts in the RSS `location` query parameter (for example `Toronto, ON`, `Vancouver, BC`). Very broad values such as a whole country may return empty feeds; prefer metros or provinces.
|
|
2. In **Settings**, set **Eluta RSS locations** (`elutaRssLocations`) as a JSON array or comma/newline-separated list, or set `ELUTA_RSS_LOCATIONS` in the environment (for example `Toronto, ON|Montreal, QC`).
|
|
3. Optionally set **Eluta max jobs per term** (`elutaMaxJobsPerTerm`, default `100`).
|
|
4. Set your search geography to **Canada** — Eluta is **Canada-only** and is skipped automatically when the resolved pipeline country is not Canada.
|
|
5. Enable **Eluta** in pipeline sources and run the pipeline.
|
|
|
|
## Common problems
|
|
|
|
### Eluta is skipped for my run
|
|
|
|
- Search geography is not Canada (city/country/Indeed country resolution). Align geography to Canada or disable Eluta for non-Canada profiles.
|
|
|
|
### Empty feeds
|
|
|
|
- The `location` string may be too broad or spelled differently than Eluta expects. Try a major city plus province (e.g. `Calgary, AB`).
|
|
|
|
### RSS HTTP errors
|
|
|
|
- Eluta may block unusual clients; the extractor sends a conventional User-Agent. Retry later or reduce the number of location feeds per run.
|
|
|
|
## Related pages
|
|
|
|
- [Extractors Overview](/docs/next/extractors/overview)
|
|
- [Add an Extractor](/docs/next/workflows/add-an-extractor)
|
|
- [Settings](/docs/next/features/settings)
|