Files
jobboard/app/templates/settings/sources.html
T
WolfandClaude Opus 5.5 e52857dea5 Split the All tag into two company overrides: All countries and All roles (WP L)
Fetching has two filters, and a company now overrides each on its own.
All countries (companies.all_countries) is the old All roles tag: its big
boards are read with the agents' wide reach. All roles (companies.all_roles,
new meaning) drops the agents' fetch terms and any later role filter.

- Migration 24 copies the old tag to all_countries and keeps all_roles for
  those companies, and moves a board's {"terms": false} to its company.
- The runner no longer reads {"terms": false}; the plan leaves the terms out
  for a company set to All roles.
- POST /api/companies/{key}/all-countries and /all-roles, each queueing a
  pull when turned on; CompanyOut carries both.
- Two toggles replace All on the Companies row, the reader and the Roles
  strip; the reach line states countries and role types in plain words;
  the filter select gets both options.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-30 12:50:45 +02:00

174 lines
9.3 KiB
HTML

{% extends "settings/_layout.html" %}
{% block title %}Sources — roledesk{% endblock %}
{# One page, three sections: the `search` plugin's job board queries, the
`ats` plugin's company boards, and the runs that read both, with the
message log as their last block. One is shown at a time, the one the URL
fragment names (`#runs`) or contains (`#messages`), or Job boards without
one; sources.js hides the rest and the rail picks one. Hidden rather than
separate pages, because each section keeps the element ids it had as a
page of its own and its script (sources.js, companies.js, jobs.js,
messages.js) is unchanged: it finds its root or does nothing. The ids are
`SECTIONS` in app/web/pages.py, which the rail links to. #}
{% block content %}
<h1>Sources</h1>
<p class="lede">Sources are where roles come from: queries on job boards that span companies, and the boards of the companies you follow. Each section is one plugin; the runs read them all.</p>
{# The Job boards form is a `<template>` because only one edits at a time, so
its ids stay unique: sources.js puts it in place of a row on Edit, and on
top of the list on New, as agents.js does for the Search agents cards. #}
<section class="card" id="job-boards" data-section>
<h2>Job boards</h2>
<p class="lede">A query on Jobindex, Adzuna or Platsbanken finds roles at any company. Switching one off closes its roles until you switch it back on.</p>
<div class="agents-head">
<p id="searches-count" class="count" role="status"></p>
<button type="button" id="s-add">New job board</button>
</div>
<p id="searches-answer" class="count" role="status"></p>
<div id="searches-list" class="srows"></div>
</section>
<template id="search-form-template">
<form id="search-form" class="agent-form source-form" autocomplete="off">
<h3 id="search-form-title">New job board</h3>
<div class="form-row">
<label>Board
<select id="s-provider">
<option value="jobindex">Jobindex (Denmark)</option>
<option value="adzuna">Adzuna (UK and EU)</option>
<option value="platsbanken">Platsbanken (Sweden)</option>
</select></label>
<label>Name <input type="text" id="s-name" required placeholder="Copenhagen backend"></label>
</div>
<label>Query
<input type="text" id="s-q" required spellcheck="false">
<span class="hint" data-provider="jobindex">Jobindex syntax: words are OR, <code>"a b"</code> is a phrase, <code>+word</code> is required.</span>
<span class="hint" data-provider="adzuna" hidden>Every word must appear.</span>
<span class="hint" data-provider="platsbanken" hidden>Free text; every word counts towards the match.</span></label>
<div class="form-row">
<label data-provider="jobindex">Area
<select id="s-area">
{% for value, label in areas %}<option value="{{ value }}"{% if value == 1 %} selected{% endif %}>{{ label }}</option>{% endfor %}
</select></label>
<label data-provider="adzuna" hidden>Country
<select id="s-country">
{% for value, label in countries %}<option value="{{ value }}">{{ label }}</option>{% endfor %}
</select></label>
<label data-provider="adzuna" hidden>Place <input type="text" id="s-where" placeholder="Berlin"></label>
<label data-provider="platsbanken" hidden>Region
<select id="s-region">
<option value="">All of Sweden</option>
{% for value, label in regions %}<option value="{{ value }}">{{ label }}</option>{% endfor %}
</select></label>
<label>Pages
<input type="number" id="s-pages" min="1" max="10" value="10">
<span class="hint">per pull, up to 10</span></label>
</div>
<p id="adzuna-key" class="note" hidden>No Adzuna key is set. Get a free one at developer.adzuna.com and set <code>ADZUNA_APP_ID</code> and <code>ADZUNA_APP_KEY</code> before starting the app.</p>
<div class="agent-actions">
<button type="button" id="s-try" class="secondary">Try it</button>
<button type="submit">Save</button>
<button type="button" id="s-cancel" class="secondary">Cancel</button>
</div>
<p id="search-status" class="count" role="status"></p>
<ol id="search-sample" class="sample"></ol>
</form>
</template>
<section class="card" id="company-boards" data-section>
<h2>Company boards</h2>
<p class="lede">Every company roledesk has seen, and how many of its roles are open. Switching a board off stops reading it and closes its roles; hiding a company keeps reading it but leaves its roles out of the list and unscored, and favourite or like lifts one instead, in Best match.</p>
<form id="board-form" class="agent-form source-form" autocomplete="off">
<h3>Follow a company</h3>
<div class="form-row">
<label>Host
{# The hosts plugins.ats reads (HOST_OPTIONS in app/web/pages.py).
companies.js copies these options into each row's Set board
control, so the page has one list of hosts. #}
<select id="b-host">
{% for value, label in hosts %}<option value="{{ value }}">{{ label }}</option>{% endfor %}
</select></label>
<label>Slug
<input type="text" id="b-slug" required placeholder="acme" spellcheck="false">
<span class="hint">The part after the host in the careers URL: boards.greenhouse.io/<strong>acme</strong>.</span></label>
<label>Company <input type="text" id="b-name" required placeholder="Acme"></label>
</div>
<div class="agent-actions"><button type="submit">Follow</button></div>
<p id="board-status" class="count" role="status"></p>
</form>
<form class="filters" autocomplete="off" onsubmit="return false">
<input type="search" id="c-q" placeholder="Filter by name, board or country code" aria-label="Filter companies">
<select id="c-filter" aria-label="Filter">
<option value="">Any</option>
<option value="favourite">Favourite</option>
<option value="liked">Liked</option>
<option value="hidden">Hidden</option>
<option value="all_countries">All countries</option>
<option value="all_roles">All roles</option>
<option value="on">On</option>
<option value="off">Off</option>
<option value="unreadable">Not readable yet</option>
</select>
{# Liked and hidden are per search agent: this picks whose the list shows
and whose the buttons set. companies.js fills it from /api/agents. #}
<label class="inline">Liked and hidden for <select id="c-agent" aria-label="Search agent"></select></label>
</form>
<p id="c-no-agent" class="note" hidden>Liking a company needs a search agent. Add one under <a href="/settings/agents">Search agents</a>.</p>
<p id="companies-count" class="count" role="status"></p>
<div id="companies-list" class="crows"></div>
</section>
<section class="card" id="runs" data-section>
<div class="row-between">
<h2>Runs</h2>
<button type="button" id="pull-now" class="secondary">Run the pull now</button>
</div>
<p class="lede">On the schedule below the pull reads every board, embed and score rank every role, extract fills in what the best postings say, score runs again with what it filled, and summarise writes the summaries.</p>
{# The two stages that ask a model, switched here rather than in config.yaml
(`GET /api/stages`); jobs.js draws the rows into #stages-list. #}
<h3 id="stages">What the model reads</h3>
<p class="lede">Extract and summarise ask a model, which costs tokens on the API. Turning one on starts nothing: the next pull runs it, and Run the pull now does so at once. How deep each reads is set per search agent, under <a href="/settings/agents">Search agents</a>.</p>
<div id="stages-list" class="srows"></div>
<p id="stages-answer" class="count" role="status"></p>
<h3>What is running</h3>
{# The element is the queue's own, served by its own router — see
pipeline/web/static/jobs.js; base.html loads its script. `idle="show"`
keeps it under the heading and has it say "Nothing running." when the
queue is idle, since a heading with nothing under it reads as something
that failed to load. #}
<desk-jobs idle="show"></desk-jobs>
{# The element and its script are the scheduler's own, served by its own
router — see pipeline/web/static/schedules.js. The cadence is picked
(every 6h, daily at 06:00, weekly mon 07:00). `add="off"`, because the
pull is the only schedule and it is declared in app/jobs/cascade.py. #}
<h3>Schedule</h3>
<script type="module" src="/_jobs/schedules.js"></script>
<desk-schedules add="off"></desk-schedules>
{# The message log, the queue's own through `/api/notices`. `#messages` is
where the old Messages paths and the toasts' "all messages" link land. #}
<div id="messages">
<div class="row-between">
<h3>Problems</h3>
<button type="button" id="clear-all" class="secondary">Clear all</button>
</div>
<p class="lede">What the server said that nobody has cleared, newest first. A message goes when you clear it, or a fortnight after it was last said.</p>
<div id="notices"><span class="muted">loading…</span></div>
</div>
</section>
{% endblock %}
{% block scripts %}
<script src="{{ asset('sources.js') }}"></script>
<script src="{{ asset('companies.js') }}"></script>
<script src="{{ asset('jobs.js') }}"></script>
<script src="{{ asset('messages.js') }}"></script>
{% endblock %}