Glossary›Metadata and Cataloging›Metadata enrichment

Metadata enrichment

What is an example of metadata enrichment?

A video file arrives in the catalog with only a name, a size, a date, and an owner ID. Enrichment adds the project code from its folder path, the owner’s department from the company directory, and the production status from the project tracking system. The file can now be found by searching for the project, and finance can see storage by department, without anyone opening the file.

What is the difference between system metadata and enriched metadata?

System metadata is what the file system records automatically, such as path, name, size, owner, and dates. Enriched metadata is everything added on top. System metadata tells you a file exists. Enriched metadata tells you what it is for, which is what a decision needs.

What does “enriched” mean in practice?

It means a file is described by more than the file system recorded. A basic index knows a file’s name, size, owner, and dates. An enriched record adds details such as the project it belongs to, the camera or instrument that produced it, the study or order number it relates to, or its retention class. Those added fields are what let teams search and act by business meaning instead of by folder.

How does automated metadata enrichment work?

Rules and plugins add fields at index time, without anyone typing them:

• Rules can read a project code from a path and record it on every file under that path.
• Format-aware plugins can read a file’s header and record details such as resolution or instrument settings.
• Business system lookups can match a shared value, such as an order number, and copy related fields onto the file.

Because enrichment runs on every scan, the description stays current as files arrive.

Can files carry custom metadata the way objects do?

On some file systems, yes. Dell PowerScale, for example, can store custom key and value pairs on each file, such as project, status, or client, in the same way object storage does. When an indexer reads those values and writes new ones back, the file and the catalog describe the data the same way. Policies can then act on that business context, not only on age or size.

What is the difference between metadata tagging and metadata enrichment?

Tagging attaches a label to a file, such as “approved” or “archive,” usually by a person or a simple rule. Enrichment adds descriptive fields, such as project, owner, or format details, usually automatically and at scale. A tag records a decision about a file, and enrichment records facts about it. Both end up in the same catalog, and both can drive search and policies.

Can metadata come from places other than the file itself?

Yes, and often the richest metadata does. The applications and machines that create files usually record details about them somewhere else:

• Application databases, such as media asset management, lab information, or product lifecycle systems, which record the project, sample, or part a file belongs to.
• Sidecar files saved next to the main file, which hold settings, captions, or capture details.
• Logs and run records from instruments, render farms, vehicles, and simulations, which record when, where, and how data was produced.
• Business systems such as project tracking, ticketing, or customer systems.

Enrichment links these records to the right files through something they share, such as a path, a file name, or an ID, so the file carries the context its application already knew.

← Back to Metadata and Cataloging

Last updated: November 13, 2026.