Dublin Core Metadata

RenamerX uses a metadata-first naming model inspired by Dublin Core. It gives the app a stable semantic vocabulary for describing files before it builds a filename.

What Dublin Core is

Dublin Core is a widely used metadata standard for describing resources. It is commonly used in archives, libraries, repositories, and digital asset systems.

Dublin Core starts from meaning and then moves toward structure.

Examples of Dublin Core fields include:

• title
• creator
• subject
• date
• type
• identifier

Why RenamerX uses it

AI-generated filenames are more reliable when the system first extracts structured metadata fields instead of trying to guess the final filename directly.

That gives RenamerX a clearer pipeline:

1. Extract semantic fields.
2. Validate and normalize them.
3. Assemble the filename using a template.

The Dublin Core fields most visible in RenamerX

The current template editor prominently uses these Dublin Core-aligned fields:

• dcTitle
• dcCreator
• dcSubject
• dcDate
• dcType
• dcIdentifier

These are the fields most useful for naming because they are concise and generally stable.

RenamerX also uses extension fields

Not every practical naming need fits pure Dublin Core, so RenamerX also uses extension fields such as:

• extOrganization
• extProject
• extStatus
• extVersion

This combination works well in real work environments where files belong to teams, projects, workflows, and release states.

What this means for users

You do not need to be a metadata specialist to use RenamerX well. The practical takeaway is simpler:

• Think in fields, not in freeform filenames.
• Separate extraction from formatting.
• Use templates to turn structured fields into consistent output.

A helpful mental model

If you are unsure which field to use, ask:

• Is this the title?
• Is this the subject?
• Is this the creator?
• Is this the date?
• Is this a project or organization extension field instead?

That question is usually enough to choose the right naming component.