Skip to main content

International industrial group

Bynder DAM health check and taxonomy overhaul

Engagement scope : DAM assessment and target taxonomy delivered

Establishing the real state of a DAM inherited from an earlier migration, then rebuilding a taxonomy the business can actually maintain.

Project visuals

Interface screenshots, reconstructed deliverable extracts and workflow illustrations are labelled. All visuals use fictional content and metadata, with client branding removed. Select an image to view it full size.

Taxonomy health report extract · reconstructed extract with fictional data.
Reconstructed deliverable extractExtract reconstructed using the original HTML report’s presentation. French report with entirely fictional fields, options, volumes and fill rates; client identity and data have been removed.

The engagement

An international industrial group's Bynder DAM had inherited an earlier migration and accumulated a taxonomy that had become hard to maintain: several dozen metaproperties, over a thousand options of which a share had never been used, residual fields from the previous platform, and entirely empty fields. Among the fields marked mandatory, only a minority were actually populated. The goal was to establish the facts before committing to anything.

We queried the API to measure, field by field and option by option, actual fill rates and real usage. The diagnosis was delivered as a self-contained HTML report with actionable exports, then worked through in workshops with the business teams: every field kept, merged or dropped on the basis of measured usage rather than opinion.

We delivered the consolidated target taxonomy: arbitrated metaproperties and options, conditional display rules so contributors only see relevant fields, a reindexing table for the values to carry over, and a documented list of dropped fields with the rationale. The client has a model it can defend to its business units and an explicit migration path.

Takeaway

A takeaway for your project

We tied each taxonomy decision to measured field usage, then documented the values to carry over in preparation for reindexing.

Technologies

  • Bynder
  • API REST
  • Python

Your next step

Has your taxonomy become difficult to maintain?

Describe the classification and contribution issues in your DAM. We can measure field usage and work with your teams on the decisions needed for an overhaul.

Discuss your project

Continue exploring