Naming Fields Dictionary

RenamerX builds filenames from structured naming fields. This dictionary explains what those fields mean in practice and how they behave in the current product.

A useful way to read this page

Think of each field as answering one question:

• What is it?
• Who made it?
• What is it about?
• When is it from?
• What project or organization is it tied to?

Fields currently exposed in the template editor

Field-by-field guidance

dcTitle

Use dcTitle for the shortest human-readable description of the file.

Good uses:

• q1-report
• tax-summary
• client-contract

Avoid turning dcTitle into a sentence.

dcCreator

Use dcCreator for the person or entity primarily responsible for the file.

Examples:

• alice-chen
• acme
• finance-team

dcSubject

Use dcSubject for broad classification. In the RenamerX naming model, this field usually works best as a controlled value.

Examples:

• finance
• legal
• operations

In the underlying naming spec, subject is treated as a hard-governed category. If RenamerX cannot classify reliably, the broader system model allows a fallback such as Unclassified.

dcDate

Use dcDate for the most meaningful date related to the content, not just any available timestamp.

Good date sources:

• document date
• capture date
• issue date
• signing date

If a clear semantic date is unavailable, the broader system design allows fallback to file modification time.

dcType

Use dcType for what the thing is, at a stable conceptual level.

Examples:

• invoice
• report
• contract
• screenshot

dcType usually stays smaller and more stable than dcTitle.

dcIdentifier

Use dcIdentifier when the file has a meaningful unique ID.

Examples:

• INV-2026-0012
• PO-8841
• case-20319

This is one of the strongest fields for de-duplication and auditing.

extOrganization

Use extOrganization when the file belongs to or references a real organization.

Examples:

• acme
• northwind
• city-hospital

extProject

Use extProject when the work belongs to a project, initiative, or engagement.

Examples:

• redesign
• migration-2026
• launch-q3

extStatus

Use extStatus for workflow state.

Examples:

• draft
• final
• approved

Use a small controlled set. Status values become noisy very quickly if everyone invents their own labels.

extVersion

Use extVersion when the file truly has versions.

Examples:

• v1
• v2
• rev-a

Do not add version just because the file changed once. Use it when version history is meaningful.

Related but not usually in the filename

dcDescription

The broader RenamerX naming spec treats dcDescription as an important metadata field, but not a filename field. It is used for explanation, search, and review context.

In the current UI, you will see this most clearly in the file preview summary area rather than as part of the final filename.

extLocationName

The broader naming spec also defines extLocationName, but the current template editor does not expose it as one of the standard field chips.

For most users, it is simpler to design around the fields that are already available in the editor.

Real-world example

Imagine you are naming signed vendor agreements for long-term retrieval.

You might choose:

• dcDate for the signing date
• extOrganization for the vendor name
• dcTitle for the agreement subject
• dcType for the stable document type
• extVersion only if formal revisions matter

That can produce a filename such as:

2025-11-08_northwind_master-services-agreement_contract_v2

In that example:

• dcDate keeps the archive sortable.
• extOrganization tells you who the agreement is with.
• dcTitle explains the specific subject.
• dcType keeps the document class stable.
• extVersion appears only because revision history matters for that workflow.

Related pages

• Templates
• Controlled Vocabulary
• Date Formatting