AESG CATALOG AUDITOR

YouTube scan · clearance audit · master dashboard · Drive sync
Google: not connectedSync: neverStorage: …

Master Dashboard

Risk Level

Clearance Status

Where You Can Post

Alerts

Fix First — Highest Risk, Not Yet Cleared

TitleSourceRiskStatusWhat to do

Catalog

TitleTypeRiskClearancePlatformsDate

Scan YouTube Channel

Reads every upload on the channel through the YouTube Data API v3 (free quota), then audits each video's title, description, tracklist, tags and YouTube's own flags (licensed-content / claim flag, synthetic-media disclosure, privacy). This is a metadata audit. It cannot hear the audio or see Content ID claim details, so it flags likely risk and you confirm the clearance status on each item. Your clearance edits are kept on every rescan.

Drive Sync + Master Catalog

Shared audit catalog: My Drive / AESG / aesg_audit_catalog.json — read and written by this tool and the Iconic Remix Series tool, so every scan and every remix lands in one place.
Colab master catalog: My Drive / AESG / master_catalog.json — merged with the button below or the Colab bridge cell.
Not synced yet.
Master push safety: before touching master_catalog.json the tool saves a timestamped backup copy next to it. It adds an aesg_audit block to matching items (matched by video ID or title) and appends new items for the rest. I have not seen your master_catalog.json structure, so check the result after the first push.

Colab Bridge

Run this in your master catalog Colab notebook as a new cell. It does the same merge as the push button, from inside Colab. Click to copy.

Merge cell

Run order suggestion: Sonic Blueprint → Bulk Processor → Merge/Dedup → this cell. Re-running is safe: it overwrites the aesg_audit block on each item and keeps a backup.

Setup

Saved in this browser's persistent storage. Names in the last field are treated as yours, not third-party.

One-time Google setup (all free)

  1. Go to console.cloud.google.com and create a project named "AESG Tools".
  2. APIs & Services → Library: enable YouTube Data API v3 and Google Drive API.
  3. APIs & Services → OAuth consent screen: choose External, fill the basics, and add your own Google account under Test users.
  4. Credentials → Create credentials → OAuth client ID → Web application. Under Authorized JavaScript origins add http://localhost:8080 (and https://iconicbyaesgp.com if you host these files there). Paste the Client ID above.
  5. Optional: Credentials → API key, restricted to YouTube Data API v3, for scans without signing in (works from a double-clicked file, public videos only).
  6. Serve the files: open a terminal in the folder holding both HTML files and run python -m http.server 8080, then open http://localhost:8080/AESG-Catalog-Auditor.html. Google sign-in does not work from a double-clicked file.
  7. Click Connect Google, accept the "unverified app" screen (it's your own app), then scan and sync.
The Drive permission requested is full Drive access, because Colab created master_catalog.json and Google's narrower scope can't see files another app created. This page only reads and writes inside the AESG folder. You sign in once per session; your data stays saved in this browser and in Drive between sessions.
COPIED