Skip to content

Enterprise DAM

Manage all your digital assets in one platform built for complex organizations. Control metadata, rights, workflows and distribution across teams, markets and channels.

Extensions of QBank DAM

Extend QBank to match how your organization works. Add automation, templates, portals and custom functionality when you need it.

Connectors & integrations

Connect QBank to the tools your teams already use. From creative tools and CMS platforms to marketing and product systems.

QBank-menu-news
Share assets beyond your organization

Create branded portals where partners, distributors and teams can easily find and download the right assets.

No outdated files. No endless email threads.

QBank DAM for enterprise organizations

Built for complex organizations that need more than asset storage. QBank helps teams across departments, markets, and industries manage, control, and activate digital assets from one governed source.

QBank-manufacturing-menu-rounded-1
Made for manufacturing complexity

Support product communication, technical documentation, and partner access across global teams, product lines, and systems.

QBank-medtech-menu-rounded-600
Built for medtech compliance

Keep digital assets controlled, traceable, and accessible across regulated workflows, teams, and external audiences.

QBank-retail-menu-rounded-1
Designed for retail speed

Help teams manage and distribute approved campaign, product, and brand content across channels, markets, and seasons.

Built for real content workflows

Explore how QBank supports the workflows that matter most across teams, markets, and systems.

Use case - Manage product content across markets
Manage product content across markets

Give global and local teams one structured way to manage approved product content, adapt it for market needs, and keep it consistent across channels.

Use case - Ensure compliant asset versioning
Ensure compliant asset versioning

Keep approved assets under control with clear version history, structured approvals, and traceability across regulated teams and systems.

Use case - Distribute approved content across systems and channels
Distribute approved content across systems and channels

Distribute approved content across websites, platforms, and downstream environments from one controlled source.

Use case - Reduce duplicate assets and improve content reuse
Reduce duplicate assets and improve content reuse

Centralize approved assets, reduce unnecessary duplication, and make it easier to reuse content across teams, systems, and channels.

Use case - Automate content production
Automate content production

Automate repetitive production tasks and keep content work moving faster across teams and workflows.

The QBank Marketing Team24-11-20222 min read

Part 2. The Foundations of your Metadata Structure

A DAM can be as simple as an image repository or as complex as a mission-critical business solution. When having a lot of assets, having an advanced metadata structure is crucial.

This blog post is Part 2 of a three part blogpost series. We will guide you from laying the foundation of your metadata structure (Part 1 and 2) to introducing complex business rules and automation (Part 3)

Part 2. Define and lay your metadata foundation

To set up your metadata structure you have to first lay the foundation as a user and enterprise and also ensure you have flexibility to set it up in a way that benefits the unique needs of your business. This includes:

  • How you define assets and asset types
  • How you determine metadata and metadata structures
  • How you set-up and, over time, manage such metadata and structures. (You may want to have smart functions, e.g. AI, for the population of certain metadata etc.)

Here are the steps to do it:


01. Define your asset types

Define what different types of Digital Assets you have in your organization. The purpose of this is to define the metadata structure for each type of asset in that specific category.

A few examples the variety of assets an organization can have when it comes to images:

  • Marketing images (may include product photos, lifestyle photos, brand photos)
  • Operational product photos
  • Spare part photos
  • After-sales photos
  • Internal / external images
  • HR and personnel related photos

QBank's advanced metadata set up

02. Make sure your digital assets contains the right information

Once you have defined the different types of digital assets it is important to set rules to make sure that the different assets contain sufficient, good and correct information.

For example: 

A product photo should contain product ID, size, relationships to other assets, specific product USP, validity date of the product and the asset itself.

A product marketing image should always contain keywords, when it is suitable to use, campaign information and corporate values conveyed.

Employee photos should include first name, last name, consent form etc. 

Now that you have defined and have a vision for your metadata structure, you can start planning for automated and complex workflows. In part 3 of this blog series we will walk through how you set up and introduce business rules and automated workflows. Stay tuned by subscribing to our blogposts!

Take me to part 3 

---

Want to talk to someone about it right now? Book a meeting with one of our in-house digital asset management experts. 

 

RELATED ARTICLES