How Can We Help?
< All Topics
Print

Configure Asset Identification

Introduction

Assetflw has the ability to automatically name each image file through the use of an intelligent identification and naming engine. It is based on rules that are defined in Assetflw. The  automatic identification and naming engine may use any available field in Assetflw both for identification and naming.

The purpose of the Upload Matching Rule is to try and find out what product and view an asset should be related to. This is done by analysing vilename, file name extetion and metadata on the image.

Asset upload Matching Rule

As stated, the Upload Matching Rule determines how to identify an image when uploading to Assetflw, e.g. anything in the filename and or metadata tags can be used to match the asset with the right product and view.

Here are several options available for the user. Select “Settings/Advance” from the main menu and click on “Asset Upload Matching Rule”. Here you may select to add a rule, click on the “+Add” button. There are several ways a product can be identified and these can be divided into three different types:

  1. Using fields in the product information
  2. Using views from the styleguide
  3. Using Metadata from Bridge or Capture1

Note: You may define several different Matching rules, these are used when uploading images (Assets). 

When you click on the “+Add” button a window will appear on the right hand side. Here you have two fields to fill in and two selection boxes:

  • Name – Free text field
  • Product identified by – Selection via dropdown
  • View identified by- Selection via dropdown
  • Upload filename pattern – Field to ender specific parameters

The Name  is important because that is whet you select in the Asset uploading procedure so a name that you understan is good to have.

The – Product identified by – and the –View identified by – dropdown, are what you use to identify the product and the view. There are two option here

  • File name pattern
  • Metadata – Adobe Bridge Labels

The File Name Pattern is used to identify anything in the file name that may be matched to anything in the product information data and/or the Style Guide Upload identifier.

The metadata selection is used to identify any color labels that may be set on the the Asset. There main identifications are  the product attributes that have been defined in Assetflw, wether it is item number, GTIN, etc. The main thing to remember is that it has to be a field that is unique to the product. There are also some fixed selections that are also available

Example: A product may be identified by the “EAN code” and the front view by the metadata color label “red”. The file may come with a random number after the EAN code that you really don’t care about. The pattern would then look like this:

          [ean-code]_[wildcard]

NOTE: it is important that the fields begin and end with bracket.

Fixed selections:

  • separator
    • Anything you want to separate the field with,e.g. an underscore
  • viewid
    • Upload identifier field on the Style guide view.
  • extension
    • Any file extension that the asset may have, e.g. TIFF
  • wildcard
    • Any value at all, normally used if you get a field in the filename that is there but you want to ignore it. 

Asset Naming definition

Most of the studio operations need a way to name images so that they are easily identified. This is as valid for the studio operation as it is for the applications using the asset later on. The best option to do this is to use names and numbers that is commonly used to identify a product or item on the company, it may be the sku’ nr or the product number etc.

In order to support this we have implemented an “Asset naming definition” in Assetflw. Thios naming definition allows you to specify your specific way of naming assets.

In order to set your “asset naming definition” you go to: Settings/Advanced”. Here you will find the menu “Asset naming definition on the left hand side.

Here you find a list of available attributes to select from. Thes are some fixed field as well as som of the dynamically defined fields.

Most of these fields are defined as the fields. you specified under “Product attributes”. At the end you have three fields that are fixed and those are:

  1. Category
  2. View
  3. Sequence

Category will use whatever you set in the Asset category for that asset, e.g. if you defined a category as “model” and use this in your naming definition it will name the asset with “model# in the name.

View is the view name specified on the style guide view. You may easily define a view identity that defines how this view should affect the naming of an asset.

Sequence gives you the option to add a sequence number to your asset name. If you are shooting model images but don’t know from time to time how many variants of a specific view you want, the sequences may help. The sequence automatically steps up the sequence nr as you add assets, e.g. the first asset will be named “…1” and the next will be named “….2” etc.

Asset status

Asset status is defined so that you may easily work with assets during photo production. It is used to visualise where the asset is in the workflow- E.g. to show if an asset is new, in post production or approved.

It is fully dynamic and may be implemented with color labels and your choice of naming to fit your defined workflow.

You must define a default status which is the one status that is used when first uploading assets to Assetflw.

Furthermore you may define the sort order of the status, this is the order that the status will be displayed in status drop-downs.

Asset categories

Asset categories are used to categorise assets in Assetflw. This is used to help you sort and filter on assets in the system.

Categories are defined freely and may be as many as needed. You simply add a new one if required.

Table of Contents