Metadata
Structured data that describes, explains, and makes it easier to find and manage other data or content.
Also known as: Data about data, Meta-information
Category: Methods
Tags: knowledge-management, organizations, information-management, data
Explanation
Metadata is often described as 'data about data' - it is information that describes the characteristics, context, and attributes of other information or content. Rather than being the content itself, metadata provides the scaffolding that makes content discoverable, understandable, and manageable.
There are three main types of metadata. **Descriptive metadata** helps identify and discover resources - think titles, authors, keywords, and summaries. **Structural metadata** describes how content is organized and relates to other content, such as chapter ordering in a book or relationships between database tables. **Administrative metadata** supports the management of resources, including creation dates, file types, access permissions, and preservation information.
In Personal Knowledge Management (PKM), metadata plays a central role. Tags, creation dates, authors, source links, status indicators, and custom properties are all forms of metadata that make notes and documents easier to find, filter, and connect. Tools like Obsidian use YAML frontmatter to store metadata directly within notes, while Notion provides structured property fields for database entries. These metadata schemas allow users to build powerful views, filters, and queries across their knowledge bases.
Metadata is essential for effective search and retrieval. Without it, finding specific information in a large knowledge base becomes a matter of remembering exact words or browsing through folders. With well-structured metadata, you can filter by topic, date, status, source type, or any other dimension that matters to your workflow.
One important consideration is the balance between too much and too little metadata. Over-engineering metadata schemas creates friction - if adding a note requires filling in ten fields, you will resist capturing information. Under-investing in metadata leads to a disorganized collection that becomes harder to navigate over time. The best approach is to start with a minimal set of metadata fields and expand only when you have a clear need. Let your metadata schema evolve alongside your knowledge practice.
Related Concepts
← Back to all concepts