Custom Bynder search and indexing workspace

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.

Bynder search workspace with criteria, filters and a gallery of fictional assets. — Interface screenshotSearch, filters and asset selection. The displayed library contains fictional examples only.

Batch indexing of fictional assets using campaign, market and rights fields. — Interface screenshotPreparing changes across a selection with the fields contributors need. Read-only demonstration.

Before-and-after review of proposed changes to fictional metadata. — Interface screenshotReviewing current and proposed values. Counts and changes come from the demonstration dataset; no Bynder writes were performed.

The engagement

In a large library, finding the right assets and repeating classification tasks takes up contributors’ working time. We developed a dedicated search and indexing workspace around an industrial group’s recurring tasks. Bynder remains the repository for assets and metadata.

Search and metadata filters help contributors build a working selection and move on to indexing the selected assets. Saved selections and field lists let them resume recurring tasks without rebuilding the same setup each session.

Batch editing brings together the fields to complete and the conditional rules needed for classification. Contributors can reuse an existing asset’s indexing and prepare batch duplication. These functions are designed to reduce repetitive entry and apply consistent rules across a selection.

Proposed changes are presented for review and confirmation before they are applied. Change history lets contributors trace updated values and prepare a correction or rollback. Available functions depend on user access and the scope enabled for the workspace.

For this implementation, Arthur Dumont reports asset search and display around 10× faster in day-to-day use than the standard Bynder portal. This is a project-specific estimate from his operational experience; a timed, like-for-like benchmark has not been conducted. The gain depends on queries, volumes and environment and is not a guarantee for another deployment.

Takeaway