News

Icecat Release Notes 150: intro Auto-Generated Bullet Points and “Other Digital Assets” replaces “other PDF”

In these Icecat Release Notes 150, we will explain the development of the first part of auto-generated Bullet Points. Further, we will discuss the renaming of “other PDF” into an other multimedia object type. Please, find here the previous Icecat Release Notes.

The first stage of auto-generated Bullet Points

We finished developing the interface for auto-generated Bullet Points, the related data model, and the business logic that to update these Bullet Points. The new feature, auto-generated bullet points, allows us to add Bullet Points on product category level. But, it will work only for leave-level categories. To further explain it, the logic for the auto-generated Bullet Points works in three steps:

  • Firstly, Icecat editors will add Bullet Points for leave-level categories in the Icecat BackOffice.
  • Secondly, the Icecat system will check the availability of manually entered Bullet Points.
  • Finally, if manually entered Bullet Points are not provided, then the algorithm will publish the auto-generated Bullet Points of the respective product category.

For the output files, we will publish auto-generated Bullet Points under the separate tag <generated bullet points> alongside the manually entered Bullet Points that are already published under the <bullet points> tag.

MultiMedia type “other pdf” replaced with “Other Digital Assets”

Additionally, we released a change in the “other PDF” Multimedia Object (MMO) type, which we renamed to “other digital assets”. Previously, in the Icecat Release notes 147, we mentioned the support of JPEG assets as “other pdf” MultiMedia Object type. In the output files, this is known as “PDF”. However, the “other pdf” type is not correctly reflecting the content of this MultiMedia Object type. Therefore, we changed the classification of this MultiMedia Object into “other digital assets”

Other improvements in Icecat Release Notes 150:

  • Fixed a bug regarding the “on offer” tab: after activating the checkbox “On offer” on the search bar, it was not visible on product level.
  • Excluded Product 3D objects taken from the local feeds and left it only for the INT locale for Philips products.
  • Added additional endpoint to the Editor Storage API with the PUT method (Endpoint with PUT method will return the asset ID under the separate field when a user tries to upload the same asset that exists in our database).
Teymur Asgarov

Recent Posts

Meet Lena: instant, trustworthy answers about Icecat – in 80 languages

It's 11 p.m., and you're staring at a 403 app_key required error, or weighing Open against Full…

5 hours ago

Channel-Specific Product Content: Why One Description Doesn’t Fit All

Your product does not change, but the way people discover it does. So why would…

7 hours ago

The making of Lena: from fluent chatbot to grounded assistant

Building a chatbot is easy. Building one you would trust to talk to your customers…

7 hours ago

Adidas Is Turning E-commerce Into a Service for Other Brands

For many retailers, e-commerce is a way to sell products directly to consumers. Adidas is…

1 day ago

Joybuy Opens Its Marketplace as Competition for European Sellers Intensifies

Europe's e-commerce landscape continues to attract new competitors, and one of the latest developments comes…

4 days ago

Securing Against LLMs: Why the Icecat robots.txt Matters to You and Your E-Commerce Store

At Icecat, managing, enriching, and syndicating millions of product data-sheets across thousands of global brands…

5 days ago