Development · integration · reverse engineeringOstwald · Alsace · Remote projectscontact@dtouch.fr
Cora · product data & images

Cora: structuring a common photo library

Define images that can circulate between several agencies and several uses: formats, color profiles, product references, clipping and nomenclature.

THE NEED

Photos produced by several participants, to be linked to the same references and for several uses.

THE INTERVENTION

Technical coordination of the preparation and sharing of visuals with the brand and agencies

THE CONCRETE CONTRIBUTION

Shared specifications for formats, profiles, variants and file names.

ContextPatrice Salib’s journey at Reymann
InterventionTechnical coordination of the preparation and sharing of visuals with the brand and agencies
Over timeProcedures and specifications 2014–2015

The situation: sharing coherent product material

The centralization of Cora visuals brought together several agencies and the brand's marketing department. To be reusable, a photo had to correspond to the right product and respect common preparation rules.

The coordination work focused as much on the information provided during the shoot as on the file delivered: product reference, designation, image and additional resources.

Developing a shared production format

The preparation specifications evolved between 2014 and 2015. The 2015 work notably defined a high-quality JPEG in RGB, an embedded ICC profile, a format of 3000 × 3000 pixels and a clipping path.

The objective was to have a source suitable for several destinations. Images requiring transparency or specific preparations retained their own constraints.

Add the nomenclature to the product benchmark

The naming combined department, SKU and image index. Ambient photographs had an explicit distinction, to differentiate them from packshots.

This organization linked the file to the business repository. It also made it possible to specify the information to be provided before a shooting and to prepare the classification of images in the common space.

Period documents & interfaces

Interfaces of the Reymann editorial channel, in their period version. These archives illustrate the journey of Patrice Salib, founder of Dtouch, within the agency.

Product information, offer and visualEnlarge
Product information, offer and visual

The product data, price and visual are reconciled before being included in the publication.

Archive Reymann · interface extract · 02/07/2014

Taking into account specialized variations

The procedure included variations, particularly for the bottle visuals: cut-out preparation, transparency, reflection and version intended for other uses. Additional information and files could accompany the product.

Centralization was to preserve these distinctions. A preview for the web is not a substitute for a production original, and two variations of a product may meet different needs.

Preparing the process of exchange between agencies

The deposit modalities and the automation of transfers were part of the framework between the brand and the agencies. The choice of a common format preceded certain tooling and mass transfer decisions.

This experience focuses on the construction of specifications and shared practices: naming, preparing and transmitting resources understandable by other stakeholders in the chain.

This case study presents the experience of Patrice Salib, founder of Dtouch, acquired at Reymann with the agency's teams and its development and production partners.

Understanding the exchanges

An image returns its product, versions and uses.

The organization of the photo library combines identifiers, metadata, preparation of visuals and reuse in publications.

An image returns its product, versions and uses.Enlarge the diagram
  1. 01

    Entry of visuals

    Images and supplier data

    Reference • radius • SKU
    Identify resources ↓
  2. 02

    Identification

    Bringing the product closer

    Nomenclature • metadata
    Preparing for Decline ▼
  3. 03

    Preparation

    Create useful resources

    Clipping • framing • versions
    Check returns ▼
  4. 04

    Control

    Check resources

    HDEF / overview • profile • duplicate
    Sorting resources ▼
  5. 05

    Photo library

    Preserve and find

    Reference • variant • condition
    Publish and reuse ▼
  6. 06

    Uses

    Reuse the right files

    PIM • pages • web supports
An image returns its product, versions and uses.Enlarge the diagram
Functional diagram · synthetic reading of flows and control points.
Closer

Distinguish between the product, the original file and its variations.

Control

Identify duplicates and gaps between previews and high definition.

Reuse

Find the appropriate visual for the document and its destination.

Your job deserves
the right tools.

A specific need, a software to evolve, a project to frame.

Exchange on your project

Complementary expertise, the same high standards.