Renaming Files with Patterns

Standardize filenames in Indexly with rename-file patterns, dry-run previews, optional database path sync, and direct handoff into profile-based organization.
Categories:
Tags:

Overview

The rename-file command in Indexly introduces a powerful way to rename files using customizable naming patterns. Use it when file names need to become consistent before indexing, analysis, comparison, or profile-based organization.

It now also supports:

  • Business-rule intelligent renaming
  • Optional profile-based organization
  • Rename and classify in a single workflow

Who This Is For

  • Users preparing messy downloads, exported CSVs, reports, or document batches for analysis
  • Operators who want predictable file names before running Organizer
  • Developers or analysts who need database paths updated after applied renames

Key Features

  • Pattern-based renaming with {date}, {title}, {counter}, and {prefix}
  • Business-rule keyword detection with --business-naming
  • Optional direct classification via --organize
  • Flexible date formatting
  • Collision-safe counters
  • Dry-run preview
  • Optional database sync for search and metadata paths

New: Business Naming Mode

Enable structured business renaming:

indexly rename-file . \
  --business-naming \
  --pattern "{prefix}-{date}-{title}" \
  --dry-run

Sample Output 

⚠️ No business keyword found in 20260208-another-example-txt-file.txt.
Select category [invoice/tax/receipt/payroll/contract] (invoice): tax
Choose prefix for 'tax' [mwst/vat/steuer/ust/tax] (mwst): vat

[Dry-run] Would rename:
  ... → vat-20260208-another-example-txt-file.txt

How It Works

  1. Detects business keywords.
  2. Assigns category.
  3. Selects or prompts for prefix.
  4. Applies pattern safely. If {prefix} is not in the pattern, the detected prefix is prepended automatically.
  5. Prevents collisions automatically.

Available Placeholders (Extended)

Placeholder Meaning
{date} File date
{title} Slugified filename
{counter} Collision-safe index
{prefix} Business category prefix

When {counter} is omitted, Indexly adds a numeric suffix only when needed to avoid an existing or planned destination filename collision. Existing leading date prefixes in YYYY-MM-DD, YYYYMMDD, and YYMMDD form are recognized, so files that already match the active pattern are skipped instead of being dated a second time.

Rename Options

rename-file supports these rename-specific flags directly:

indexly rename-file ./incoming \
  --pattern "{date}-{title}-{counter}" \
  --date-format "%Y-%m-%d" \
  --counter-format "03d" \
  --dry-run
Flag Behavior
--pattern Filename pattern using {date}, {title}, {counter}, and {prefix}.
--date-format Date format for {date}. Defaults to %Y%m%d.
--counter-format Python integer format for {counter} such as 03d.
--recursive Rename files below the target directory recursively.
--dry-run Preview filesystem renames without moving files.
--update-db After applied renames, update Indexly DB paths for metadata, tags, and search index rows.
--db Database path to update when --update-db is used.

--update-db is opt-in. Without it, rename-file only changes filenames on disk. When --db is omitted, Indexly uses its configured default database.

Rename + Organize in One Command

Bridge renaming directly into profile-based organization:

indexly rename-file . \
  --business-naming \
  --pattern "{prefix}-{date}-{title}" \
  --organize \
  --profile business \
  --classify \
  --apply

Result

Files are:

  1. Renamed using business rules
  2. Classified into Business structure
  3. Logged and hashed
  4. Moved safely

When --organize is used, the organizer receives the rename plan directly. In dry-run mode it previews organization from the planned filenames; in apply mode it organizes the files after successful filesystem renames.

This makes organizing highly intuitive — especially with --classify.

For details on profiles and classification, see Profile-Based Organization.

Prepare CSVs And Analysis Inputs

Renaming is useful before data analysis when exported files have inconsistent names, duplicated date prefixes, or unclear report titles.

Example:

indexly rename-file ./exports \
  --pattern "{date}-{title}" \
  --recursive \
  --dry-run

After reviewing the plan, apply the rename and analyze the prepared CSV:

indexly rename-file ./exports --pattern "{date}-{title}" --recursive
indexly analyze-csv ./exports/20260516-sales-report.csv --auto-clean --show-summary

For the analysis path, see Cleaning CSV Data and Data Analysis Overview.

Business Workflow Example (Practical Scenario)

You receive a folder of mixed files:

INV-00012.txt
receipt_2026.txt
steuer_report.pdf
contract_signed.docx

Run:

indexly rename-file ./incoming \
  --business-naming \
  --pattern "{prefix}-{date}-{title}" \
  --organize \
  --profile business \
  --classify \
  --dry-run

In one preview, you will see:

  • Standardized filenames
  • Assigned categories
  • Destination folders
  • No file overwritten

Remove --dry-run to execute.

Everything Else Still Works

All original pattern-based renaming remains unchanged.

You may still:

indexly rename-file --pattern "{date}-{title}" .

Business mode is optional and additive.

In Summary

The enhanced rename-file now allows you to:

  • Standardize filenames
  • Detect business document types
  • Apply structured prefixes
  • Organize automatically into profiles
  • Maintain full audit logs
  • Perform everything safely via dry-run

Renaming is no longer isolated. It is now part of a structured organization pipeline.

Next Steps