Introduction

Most studio operations require a consistent method for naming images to ensure they are easily identifiable. This is just as important for the studio team as it is for the applications that will use the assets later on. The best approach is to use naming conventions based on identifiers commonly associated with the product, such as the SKU, product number, or any other internal reference. This helps e-commerce systems accurately associate images with the correct products.

To support this, we’ve implemented an “Asset Naming Definition” feature in ProStudio. This allows you to define a custom naming convention that aligns with your specific asset identification needs.

Creating the Asset Naming Definition

To configure your “Asset Naming Definition,” navigate to Settings > Advanced. In the left-hand menu, you’ll find the Asset Naming Definition option.

Here, you’ll find a list of available attributes to choose from. These include both fixed fields and dynamically defined fields.

Most of these fields are based on the attributes you have defined under Product Attributes and the View Attribute used in the Style Guide. 

At the end of the attribute list, you’ll find three key options for constructing your asset names. Two of these are required, and one is optional:

• Product - Required

• View - Required

• Sequence - Optional

Product - This field is used to identify the product that the asset belongs to. For example, if you choose Product Code in your naming definition, the asset will be named using the corresponding product code.

View - This refers to the view name defined in the Style Guide. You can easily assign a view identifier that determines how this specific view should be reflected in the asset name.

Sequence (Optional) - The sequence option lets you add an automatic sequence number to your asset name. This is especially useful when shooting model images, where the number of image variations per view may vary. As you add assets, the system will automatically increment the sequence number—e.g., the first asset will end in “...1”, the next in “...2”, and so on.

Note: You may use any of the available fields listed under "Asset Naming Definition". The important thing is to ensure that your naming convention includes something that represents the product and something that represents the view.

Example: If you choose to use the ProductCode to identify the product and the ViewId from your style guide to represent the view, and separate them with an underscore, your assets will follow this naming format:

    "ProductCode_ViewId"