Prompt
I'm building a searchable media library for logos, templates, and videos. How should I structure it?
Latest observation
A good searchable media library works best when you separate what the asset is, where it can be used, and how it can be found.
1) Start with a clear asset model
Use one consistent structure for all media types, with type-specific fields added as needed.
Core fields for every asset
- ID: unique identifier
- Title / Name
- Asset type: logo, template, video, image, audio, etc.
- Description
- Tags / keywords
- Category / collection
- Status: draft, approved, archived
- Owner / author
- Created at / updated at
- Version
- File format
- File size / duration / dimensions
- Preview / thumbnail URL
- Source URL / storage reference
- Rights / license / usage restrictions
Type-specific fields
Logos
- Brand
- Color variants
- Background compatibility
- Orientation
- Vector/raster format
Templates
- App/platform
- Dimensions / aspect ratio
- Editable fields
- Required software
- Use case
- Layout type
Videos
- Duration
- Resolution
- Frame rate
- Aspect ratio
- Captions/subtitles available
- Transcript
- Scene/topic tags
2) Use a hierarchical taxonomy plus tags
Don’t rely on tags alone.
Recommended structure
- Primary category
- Brand assets
- Marketing templates
- Social media
- Product videos
- Training content
- Subcategory
- Logos → monochrome, icon-only, wordmark
- Templates → presentation, flyer, post, ad
- Videos → promo, demo, testimonial, tutorial
- Tags
- flexible descriptors like “minimal,” “dark mode,” “holiday,” “horizontal,” “2025”
This gives you both:
- structured filtering via categories
- freeform discovery via tags
3) Design for search first
If the library is searchable, indexing matters as much as storage.
Index these fields
- title
- description
- tags
- category/subcategory
- brand/product name
- transcript text for videos
- OCR text for templates/images if applicable
- file metadata
- creator/owner
- related campaign names
Search features worth adding
- Full-text search
- Faceted filters
- Sort by relevance, newest, popular, most used
- Synonyms and aliases
- Fuzzy matching
- Autocomplete
- “Search within collection” / “search within brand”
Example filters
- Type
- Brand
- Status
- Format
- Orientation
- Size/aspect ratio
- Color
- Language
- Usage rights
- Campaign
- Date added
4) Organize with collections and relationships
People usually browse by project or brand, not just by tag.
Useful grouping concepts
- Collection: curated set of related assets
- Campaign
- Brand
- Project
- Series
- Variant family
Relationships to support
- logo has variants
- template belongs to a campaign
- video is related to a landing page or product
- asset is derived from another asset
- asset replaces an older version
This helps with reuse and version control.
5) Plan for versions and approvals
Media libraries get messy without governance.
Add workflow states
- Draft
- In review
- Approved
- Deprecated
- Archived
Versioning
- Keep version history
- Store who changed what
- Mark one version as current
- Preserve old versions for rollback
6) Store derivatives and previews separately
For usability, don’t make users download originals just to identify assets.
Recommended files per asset
- Original/master
- Preview/thumbnail
- Web-optimized derivative
- Optional alternate formats
Examples:
- logos: SVG master + PNG previews
- videos: MP4 web preview + poster frame + transcript
- templates: thumbnail + preview images + editable source file
7) Recommended database structure
A practical setup is:
Tables/collections
- assets
- asset_versions
- tags
- asset_tags
- categories
- collections
- asset_collections
- users
- usage_rights / licenses
- asset_relationships
This avoids stuffing everything into one table and makes search/filtering cleaner.
8) Example asset record
{
"id": "asset_12345",
"title": "Acme Logo Horizontal Dark",
"type": "logo",
"description": "Primary horizontal logo for dark backgrounds.",
"brand": "Acme",
"category": "Brand Assets",
"subcategory": "Logos",
"tags": ["horizontal", "dark mode", "svg", "primary"],
"status": "approved",
"version": "3.0",
"format": ["SVG", "PNG"],
"dimensions": {
"width": 2400,
"height": 800
},
"thumbnail_url": "https://cdn.example.com/thumbs/asset_12345.png",
"file_url": "https://cdn.example.com/assets/asset_12345.svg",
"owner": "design_team",
"created_at": "2026-01-12T10:22:00Z",
"updated_at": "2026-01-18T14:05:00Z",
"license": "internal_use_only"
}
9) Suggested UX structure
For the user interface:
- Left sidebar for facets/filters
- Search bar at top with autocomplete
- Grid/list toggle
- Asset cards showing thumbnail, title, type, tags, status
- Quick actions: preview, download, copy link, add to collection
- Detail drawer with metadata and related assets
10) Best-practice rule of thumb
If users ask:
- “What is this?” → title, type, description
- “Can I use it?” → rights, status, owner, version
- “Can I find similar items?” → tags, taxonomy, transcript/OCR, relationships
- “Can I reuse it?” → collections, variants, editable source, formats
If you want, I can also give you:
- a database schema,
- a search/filter design, or
- a metadata standard for logos, templates, and videos.