ProjectsCROP Frontend
McHale Media Drops
Location: Updated: 2025-11-07
McHale Media Drops
Location: data/manufacturers/mchale/media
Updated: 2025-11-07
Files
| File | Description |
|---|---|
storage-manifest.json | Condensed manifest consumed by the front-end when resolving preview + 360° assets. Keys match the McHale vendor codes used by the catalog. |
storage-media-catalog.json | Full export from Google Cloud Storage containing per-asset metadata, checksums, and counts. Useful for audits and tooling. |
storage-all-media-urls.txt | Plain-text URL list for quick diffing or to seed downstream syncing jobs. |
Refresh workflow
- Ensure you have access to the McHale bucket (
gs://crop_parts/McHale). - Run the extraction script to pull the latest inventory:
bun scripts/extract-mchale-media-urls.ts \ --bucket gs://crop_parts/McHale \ --out data/manufacturers/mchale/media/storage-all-media-urls.txt - Generate the JSON artifacts for the app layer:
The script reads the URL list, groups assets by part, and writes bothbun scripts/generate-mchale-storage-urls.tsstorage-manifest.jsonandstorage-media-catalog.json. - Commit the refreshed files and mention the timestamp in your PR description.
Consumers
lib/utils/image-url-builder.tsbuilds fallback URLs but prefers entries from this manifest when present.lib/search-service/adapters.tsmerges API media data with local manifests to guarantee every part has at least one image/360 reference.
Please avoid storing environment secrets in these files; they ship to the client in certain views.
Search API: Add Package Data Fields
Document Version: 1.1 Created: 2025-11-24 Updated: 2025-11-24 Status: ✅ Implemented - Pending Deployment Related Frontend Work: PartSpecs component for part...
administration dashboard for managing parts, vendors, and analytics
Internal administration dashboard for managing parts, vendors, and analytics. Built with Next.js and Clerk authentication.