Metadata schema

A metadata schema is the agreed set of attributes an organization will record, with allowed values for each. A taxonomy is the structure those values sit in. Designing this before enrichment starts is what makes a catalog queryable later, and it is the step most often skipped.

Key takeaways

A metadata schema is the agreed set of attributes an organization records about its files.
Deciding it before enrichment begins keeps values consistent across teams.
A useful file schema mixes system fields with business fields such as project and retention class.

Why does a metadata schema matter?

It makes metadata comparable. If one team writes a project name as Show X and another as SHOWX_2024, a search for either misses half the files. A schema fixes the field names and the allowed values, so searches, reports, and policies work the same way across every team and storage system.

What is an example of a file metadata schema?

A small schema often starts with five fields, each with a short list of allowed values:

Project: chosen from the official project list.
Department: one value per cost center.
Retention class: such as legal record, project record, or temporary.
Sensitivity: public, internal, confidential, or restricted.
Status: active, delivered, or archived.

Because each field only accepts known values, a rule written against the schema works the same way everywhere.

Which fields should a file metadata schema include?

Start with the fields every decision needs, such as project, cost center, retention class, and sensitivity signal, and add a field only when a named decision depends on it. System metadata already supplies attributes such as path, size, owner, and dates, so the schema covers what the storage system does not record. Each field needs a short list of allowed values, because open text entries cannot be queried reliably across a data estate. A schema of a few well-defined fields is more useful than a long list nobody keeps current.

Who decides the metadata schema?

Usually a data steward or a governance group, with input from the teams that create the data and the storage team that applies it. The schema should start with the few fields that drive real decisions, and grow only when a new decision needs a new field.

What is the difference between a metadata catalog and a metadata schema?

A metadata schema is the plan: the list of fields every file should carry, such as project, department, and retention class, and the values each field may take. A metadata catalog is the system that holds the actual records for every file and lets people search them. The schema decides what the catalog records, and the catalog is where the schema is applied, file by file.

What is the difference between a file naming convention and a metadata schema?

A naming convention puts information into the file name itself, such as a project code, a date, and a version number. It is easy to start and needs no tools, but it only works when everyone follows it, it breaks when files are renamed, and a name can only hold so much. A metadata schema keeps the same information in separate fields that sit beside the file, so it can hold more, be applied by rule, and be corrected without renaming anything. Many organizations use both: the naming convention becomes one of the sources that fills the schema.

How does Diskover help?

Diskover fills many schema fields automatically at index time through enrichment rules and plugins, so the same description is applied across every storage system.

Explore the enriched metadata catalog

Book a demo