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.
The engagement
Cleaning a media library takes more than comparing filenames. Similar assets may not be interchangeable, and one may already be used in a PIM. The project needed to make those dependencies visible before a cleanup decision.
We developed a duplicate manager that automatically groups candidate assets from a local DAM inventory. Groups are enriched with Bynder data and PIM references. The interface supports survivor selection, metadata reconciliation and dismissing groups that are not duplicates.
The workflow separates automated detection from approved actions. Inventory freshness checks gate sensitive operations, with specific safeguards for assets referenced by the PIM. Human review and action logging govern cleanup.
Takeaway
A takeaway for your project
We combined automated candidate grouping with a review of metadata and dependencies before cleanup.
Technologies
- Bynder
- PIM
- React
- TypeScript
- Node.js
- MariaDB
Your next step
Are your duplicate assets already used elsewhere?
Describe the duplicates you encounter and the systems using those assets so we can define detection, retention and cleanup rules.
Discuss your project