Open alexgarel opened 1 year ago
Technically,
story 1 would be easy to implement using a special value to say the list is a final list (for example "FINAL") or maybe easier for users, in the title (categories_final). We just have to handle that in Import.pm around line 1322
story 2 (publication) has two alternatives
Many of the tags fields are not direct input fields, only a few can be written directly (allergens, categories, countries, labels etc.).
It's probably worth looking at each of those fields to see which behaviour we want, and which behaviour producers may want.
e.g. for allergens and traces, if the producer supplies a non empty value, we probably could remove pre-existing values, both on the producers platform and the public platform.
This would be very helpful for a lot of producers, especially for large ones. In my opinion, within the Pro platform issues, it is one of the most needed. Could it be prioritised over the next few weeks (/months?) please? cc @alexgarel @stephanegigandet
One common case is that producers want to clean the existing data in fields like the ingredient list.
Food for thought ... Here is an example of how Brevo deals with a similar situation.
Context
On pro platform, as we import data there are two types of behaviour:
This behaviour is true, either when I import data with a CSV, or when the data is published to pro platform.
Story
As a producer,
PS: making a single ticket as problems are related, might be splet though
Tags values:
relevant code:
%tags_fields
inTags.pm
@taxonomy_fields
inConfig_off.pm
Fields:
Also note that "brands" as some special handlings.