Polimake

How to find useful photos in a library of thousands

Illustrative scenario

A method for searching, filtering, and verifying photography at scale without relying on filenames or blindly trusting visual similarity.

Finding a photo is not the same as finding a usable photo

A brand has 18,000 images from events, campaigns, and shoots. Marketing searches team collaborating in an office and receives hundreds of results. Some are blurred, some belong to another client, and several lack consent for advertising.

Visual search reduces the universe. Filters and the asset record determine whether a result is fit for use.

Define a specific need

Before entering a query, specify:

  • channel and format: landscape web cover, vertical story, or slide;
  • scene and action: three people reviewing a prototype, not “innovation”;
  • tone: documentary, approachable, technical, or institutional;
  • restrictions: client, territory, date, people, or product;
  • minimum quality and rights expiry.

Example: three-person team reviewing a physical prototype, landscape frame, natural light. Then filter for the Acme account, approved external use, and enough width for the web.

Work in layers

  1. Run a broad descriptive query.
  2. Review early results to learn the library's vocabulary.
  3. Add one filter at a time: project, date, orientation, status, or rights.
  4. Group frames from the same burst so you do not compare twenty near-duplicates.
  5. Open candidate records and confirm source, quality, and permissions.
  6. Save the search if it answers a recurring need.

If results remain irrelevant, do not tag thousands of files blindly. Fix a priority collection first and record which field would have resolved each failed search.

An agency reuse example

The team is preparing a collaboration campaign for a software client. It finds a suitable scene from an earlier workshop. Before reuse, it confirms that the agreement permits the new campaign, consent still covers the people involved, and no confidential notes appear on the wall.

It creates a portrait crop as a derivative linked to the source. It does not export another copy named good_photo_final.jpg into a separate folder.

Measure retrieval quality, not promises

There is no basis for a universal 90% reduction. Record:

  • searches ending in a published asset;
  • time to a verified candidate;
  • results rejected for quality, context, or rights;
  • zero-result queries;
  • reused photography versus newly purchased stock.

These figures show whether to improve search, complete metadata, retire material, or commission a new shoot.

If you remember one scene but not its name, use the unknown-file retrieval workflow. If disorder begins at delivery, start with the operational closeout for event photography.