Skip to main content

Catalogue Administration

The global Skill Catalogue is the shared taxonomy every tenant draws on when tagging talent and defining slot requirements. It currently spans 1,153 skills, 369 certifications, and 1,217 cert↔skill correlations across 6 industries. As an administrator you curate this catalogue: remediate backfill entries, manage skills and certifications, approve or reject submissions, maintain cert↔skill relationships, and review staged external import runs.

Govern the catalogue​

The catalogue admin screen is organized into tabs.

  1. Navigate to Admin → Catalogue.
  2. Use the tab bar to switch between:
    • Remediation Queue — resolve backfill entries that did not cleanly match an existing skill or certification.
    • Normalization — run fuzzy, AI-assisted reconciliation of provisional skills against the canonical catalogue: preview matches (a dry run), auto-link high-confidence ones, then promote or merge the rest from the review queue.
    • Skills — browse and manage the skill taxonomy.
    • Certifications — browse and manage certifications.
    • Submissions — approve, map, or reject pending skill and certification submissions.
    • Relationships — maintain cert↔skill correlations.
📷 ScreenshotThe Skill Catalogue with its remediation, normalization, skills, certifications, submissions, and relationships tabs/admin/catalogue

Review submissions​

When talent or company users propose a new skill or certification, it lands in the Submissions queue for an administrator to triage.

  1. On Admin → Catalogue, open the Submissions tab.
  2. For each pending submission, choose an action:
    • Approve — promote it into the canonical catalogue.
    • Map existing — point it at an existing skill or certification (search and select).
    • Reject — decline it, optionally with a reason.
Map instead of approving near-duplicates

If a submission is just a different name for something that already exists, use Map existing (or add it as an alias) rather than approving a duplicate entry. This keeps the taxonomy clean.

Review external import runs​

External skill and certification feeds are staged as import runs so you can reconcile them against the catalogue before anything is promoted.

  1. From Admin → Catalogue, click Import Runs (/admin/catalogue/imports).
  2. The list shows each run's source, type (Skills / Certifications / Mixed), status (processing, completed, failed), and counts: total, matched, unmatched, pending, promoted. Filter by status or Refresh.
  3. Click Review to open a run at /admin/catalogue/imports/:importRunId.
  4. The detail page shows match stats (exact, fuzzy with a confidence %, unmatched) and a record table. For each pending record choose: Map existing, Add alias (skills only), Create new, Reject, or Ignore.
  5. Records promoted as Create new flow into the Submissions queue for final approval.
📷 ScreenshotReviewing staged records in a catalogue import run/admin/catalogue/imports/:importRunId

The catalogue pipeline​

Behind the admin UI, the catalogue is built and curated by a set of scripts run from the api-server package (pnpm --filter @workspace/api-server catalogue:*). The write-capable commands (catalogue:approve, the backfills, and catalogue:seed-mappings) apply their changes when you run them; prefix a command with DRY_RUN=true to preview it without writing.

  1. Seed — catalogue:seed-v2 loads the per-industry catalogue modules, normalizes and dedupes them, and upserts skills, certifications, and cert→skill correlations with source='catalogue_v2' and reviewStatus='unreviewed'. On a slug conflict it preserves curator edits and unions the industries tags.
  2. Preflight — catalogue:preflight is a read-only quality check that detects duplicate names, slug collisions, empty slugs, and other issues before any approval happens.
  3. Approve — catalogue:approve idempotently promotes records whose review status is unreviewed, needs_edit, or null to approved, deliberately skipping anything already submitted, rejected, merged, or approved. It is safe to re-run.
  4. Backfill & mappings — catalogue:backfill-skills, catalogue:backfill-certs, and catalogue:seed-mappings populate skills, certifications, and cert↔skill correlations from existing data.
  5. Quality — catalogue:quality reports on the overall health of the catalogue.
📷 ScreenshotThe catalogue admin entry point for reviewing and approving submissions/admin/catalogue
Always preflight before approving

Run catalogue:preflight and resolve any reported duplicates or slug collisions before running catalogue:approve. Approving over unresolved duplicates promotes them all, leaving the taxonomy to be cleaned up afterward.