Back to Reports Workspace

Tools

A practical map of the review, coverage, and reporting tools in the Media Monitor. These tools all read from the same monitor data, but each answers a different analyst question.

Open Report Builder

Reporting

Reports Workspace

Analyst review desk

Creates a report, loads a candidate article pool for that report window, and lets analysts move individual articles from the unassigned queue into the current report with group-level shortcuts when useful.

Manual workflow: reports are created by analysts, not automatically.
Candidate pool: defaults to excluding articles already used in other finalized reports.
Queue states: supports unassigned, in_report, held, and discarded.
Review modes: story-grouped by default, with date and publisher layout options.
Export: supports category + URL export for current Report Mule workflows.

Open Workspace

Coverage Report

Printable brief builder

Generates a ReportMule-style brief for a selected client, workflow, and publication date range using that workflow's configured categories, successfully scraped articles, and client-specific context summaries.

Category filter: loads the active categories for the selected client and workflow.
Quality filter: requires kept = true, scrape_failed = false, and usable raw_text.
Publisher filter: resolves the article domain within its selected client, workflow, and category. Category-specific tiers override workflow-wide tiers; only Mozilla Client Coverage can use the legacy registry as fallback.
Summary logic: uses stored workflow matches, configured client terms, and extracted text to find relevant context.
Copy logic: each category has a one-click URL copy button for analyst handoff.

Open Report

Report Compare

Analyst-report coverage comparison

Takes a pasted list of report URLs and compares them against monitor results for the selected date range. It is useful for seeing what the monitor found, what analysts already had, and what the monitor may have missed.

URL parsing: extracts URLs from pasted text and normalizes query strings, fragments, trailing slashes, and common www variants.
Monitor matching: compares pasted URLs against both url and normalized_url from Supabase.
Additions: surfaces kept monitor articles that were not in the pasted analyst list.
Publisher review: groups additions by verified, discovery, watchlist, and failed-scrape handling so analysts can review trust level quickly.

Open Compare

Coverage QA

Syndication Check

Duplicate and syndication discovery

Finds articles that are likely the same story republished across multiple outlets. It is read-only and does not hide, merge, or delete anything automatically.

Text fingerprinting: converts extracted full text into normalized word shingles.
Candidate search: uses MinHash-style signatures and banding to avoid comparing every article to every other article.
Similarity score: checks candidate pairs with Jaccard overlap and groups matches using union-find clustering.
Review clue: displays shared phrases so the analyst can confirm whether the cluster is truly syndicated.

Open Syndication

Feed Coverage Audit

Google News RSS query QA

Compares a combined Google News RSS search against individual site-specific searches. This helps detect whether a broad batch feed is missing stories that appear when a publisher is queried directly.

Input: accepts up to 25 domains, with quick samples for high-volume and PCMag-style publisher groups.
Comparison: calls the feed-audit API to fetch combined and individual Google News RSS result sets.
Risk signal: flags individual feeds that hit the 100-entry cap or have titles absent from the combined feed.
Outcome: provides sample missing titles so feed batches can be split or tuned.

Open Feed Audit

Source Health

Configured feed visibility

Shows configured RSS/search feeds alongside recent monitor outcomes. It answers whether a source is active, quiet, generating useful kept articles, or producing scrape failures.

Configured feeds: reads scoped Supabase feed routes plus the legacy data/feeds.csv fallback and groups rows by source label and type.
Recent activity: pulls recent articles from Supabase and maps them back through found_in_feeds.
Status: separates active, quiet, partial, and failure-prone sources for quick triage.
Source admin: includes separate Supabase-scoped tools for adding feeds and managing publisher tiers with reviewer metadata.
Security: scoped feed routes and publisher tiers require the server-side Supabase service role and the configured PIN. The legacy Mozilla registry remains read-only fallback data during transition.

Open Sources

Pipeline Audit Log

Curation and domain-review inspection

Displays processed articles with the keep/discard outcome and the AI curation reason. It is the place to investigate why an article was kept, discarded, flagged, or repeatedly sourced from a noisy domain.

Status review: filters all processed articles by kept or discarded status.
Reason review: shows the model's curation reason and scrape/error details where available.
Domain review: identifies domains with repeated discarded articles and no recent kept articles.
Block workflow: offers review-before-block controls so noisy domains are not removed blindly.

Open Audit Log

Operations

OpenAI Usage

Estimated model spend monitor

Tracks app-side OpenAI calls from the last 24 hours. Costs are estimates from captured token counts and a local model rate table; reconcile against OpenAI billing for final accounting.

$0.0000estimated cost

0tokens

0calls

0summaries

0failed

Loading OpenAI usage...

Time	Status	Feature	Model	Tokens	Est. Cost	Article	Details
Loading...

ScrapingBee Usage

Paid fallback budget monitor

Tracks ScrapingBee fallback attempts from the last 24 hours. The pipeline cap is 2,500 estimated credits per rolling 24-hour period; when exhausted, eligible URLs are logged as budget-skipped instead of being sent.

0credits used

2500credits left

0API attempts

0successful

0skipped

Loading ScrapingBee usage...

Open Full Usage Page

Time	Status	Workflow	Category	Mode	Credits	Article	Details
Loading...

Legacy Mozilla Coverage Dashboard

Mozilla source monitoring utility

The live dashboard shows kept Mozilla and Firefox coverage, review state, keyword snippets, source metadata, full text, and copy actions for handoff.

Data source: queries kept articles from Supabase for a selected time window.
Filters: narrows by category, review status, and blocklist domain.
Review state: updates the reviewed field in Supabase from the card action.
Copy actions: copies either title-plus-URL pairs or URLs only for the current filtered view.

Open Live Dashboard

Run Monitor

Manual pipeline trigger

Starts a monitor run without waiting for the scheduled GitHub Actions cadence. It is protected by a PIN and calls the Cloudflare Pages Function that dispatches the GitHub workflow.

Trigger: sends a POST request to /api/run-monitor.
Security: requires a configured PIN and GITHUB_WORKFLOW_TOKEN stored server-side with Actions write access.
Use case: good after feed changes, verified-publisher additions, or urgent coverage checks.

Open Live Dashboard

Blocklist Manager

Noise control

Lets analysts block domains that repeatedly produce irrelevant results. Blocked domains are hidden in the dashboard and excluded during future ingestion.

Dashboard filter: hides articles whose article URL domain appears in the blocklist.
Ingestion filter: the pipeline reads the same blocklist so future runs can skip blocked domains.
Manual action: blocks can be added from cards, from the manager modal, or from audit/domain review workflows.

Open Live Dashboard

Add New RSS/Search Feed

Source onboarding

Adds a new RSS or alert feed to the ingestion list without automatically treating the publisher as verified. This is the right tool for new Google Alerts, Talkwalker Alerts, or other feed-based inputs.

Inputs: client, workflow, optional category, route priority, source type, label, RSS/feed URL, optional publisher domain, failed-scrape visibility, routing note, and PIN.
Stored fields: creates or reuses a shared feed_sources row and creates or updates its scoped feed_source_routes assignment in Supabase.
Publisher verification: remains a separate client/workflow-scoped action so a partial save cannot misrepresent source trust.

Open Sources

Manage Scoped Publisher Tier

Client/workflow publisher governance

Assigns a publisher domain to the Verified, Discovery, or Watchlist tier for one client/workflow and optional category without changing ingestion. The same domain can carry different tiers in different scopes.

Required input: client, workflow, canonical publisher domain, tier, and PIN.
Optional input: category, publisher name, review note, reviewer source, and review date.
Scope effect: category-specific tiers override workflow-wide tiers. Mozilla Client Coverage alone can fall back to the legacy registry when no scoped tier exists.

Open Sources View Tier Lists

Reference

Legacy Mozilla Publisher Tier Lists

Mozilla verified, discovery, and watchlist registry

Shows the three manually assigned Mozilla Client Coverage lists retained as compatibility fallback data. Active multi-client report filters and confidence labels prefer scoped Supabase tiers.

Verified: reviewed sources that can support final reports when the article itself is relevant.
Discovery: useful sources that should stay visible while analysts continue learning their value.
Watchlist: sources to monitor cautiously because they may be noisy, indirect, or special-purpose.

Open Tier Lists

Glossary and Monitor Logic

Plain-English workflow explanation

Explains terms like caught, not caught, filtered before review, scrape alert, trusted source, discovery, watchlist, and unclassified. It also walks through how a link moves from feed ingestion into the dashboards.

Glossary: defines the words used on the compare and reporting pages.
Pipeline logic: explains the sequence from feed discovery to scraping, filtering, AI review, and storage.
Analyst actions: separates source assignment from article relevance decisions.

Open Glossary

Suggested Workflow

Start in the Reports Workspace to choose the active report and review candidate coverage.
Use Source Health when a feed appears too quiet, noisy, or scrape-heavy.
Run Feed Coverage Audit when a publisher batch feed may be missing stories from high-volume sites.
Use Syndication Check to identify repeated same-story clusters before copying or reporting links.
Use Report Compare when checking monitor results against an analyst-supplied or third-party report.
For Mozilla Client Coverage, generate the Coverage Report with the Verified tier when you need a clean, printable brief from trusted publishers only.

AI grouping for the report should be added server-side, not inside the browser. The safe design is to pre-cluster similar articles with the syndication logic, send compact metadata/snippets to the model, and store or render strict JSON story groups.