Question
Closed · Answered

Can I preview proposed filenames before Buda renames a batch of product images?

Hovhannes Vktarget

I'd like to organize product images with messy filenames, using product, angle, and intended use in the names, and generate an asset index.

I'd prefer a table of old and proposed filenames first, with uncertain product identities flagged for review. After checking it, I'd authorize the renaming. Does anyone have a useful naming convention? I'd also want to keep a copy of the originals.

Report
Kelly
Team

Yes. Brief it as a two-step job: first a preview table, then rename only after you approve.

*Local demo / Diagram · Preview → review → rename*

Useful naming pattern

{product}-{angle}-{use}.ext

Examples: mug-front-pdp.jpg, mug-detail-ads.jpg.

Keep a short glossary for angle/use codes so the batch stays consistent.

Steps

  1. Put originals in Drive (or ask Buda to copy them into an originals/ folder first — keep that copy).
  2. Ask for a preview only:
For every image, propose a new name using product / angle / use. Output a table: old name → proposed name → confidence. Mark uncertain product matches as needs review. Do not rename anything yet.
  1. You review the table; fix uncertain rows.
  2. Then authorize:
Rename only the rows I approved. Write an asset index (old, new, product, angle, use). Leave originals/ untouched.

How to verify

  • Preview table exists before any file moves.
  • Uncertain rows are flagged, not guessed silently.
  • After rename, originals/ still has the untouched copies and the index lists every change.

Boundaries

  • Do not let “organize my folder” imply immediate renames — say preview first explicitly.
  • If many files look alike, require human confirmation on low-confidence rows before step 4.
Report

Your reply

Sign in to join the discussion. Reading is always open; you only need an account to post.

Sign in