You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The property values of a specific product are contained in index/core catalogue2. There, a product has for each property value a field. For example, item_name or item_price. This fields have to linkage to the properties of the corresponding ontology concepts. That means, the field item_name could be the datatype property name of a chair but it is defined. In conclusion, there is no mapping possible.
I propose to have an additional field in catalogue2 or properties to add a tuple (field name in core catalogue2, property name in core properties). Then, we could create a Entity Mapping Service in catalogue-search
The text was updated successfully, but these errors were encountered:
We will create another dynamic field that uses all item_properties as it's name to get this mapping into the index. We also need to include the "dimensions" in the item_properties (like cac:GoodsItem / cac:Item / cac: Dimension), to also cover the dimension properties.
The properties should include both, custom properties and "standard" properties.
Dear Felix,
It sounds good. I have an additional question: Do you mean with:"...
We will create another dynamic field that uses all item_properties as it's name to get this mapping into the index. ..."
Does that mean that you will add the Uri as property name for each property into the catalogue2?
Best regards
Marco
Get Outlook for Android<https://aka.ms/ghei36>
On Tue, Jun 12, 2018 at 6:06 PM +0200, "fstroh" <[email protected]<mailto:[email protected]>> wrote:
We will create another dynamic field that uses all item_properties as it's name to get this mapping into the index. We also need to include the "dimensions" in the item_properties (like cac:GoodsItem / cac:Item / cac: Dimension), to also cover the dimension properties.
The properties should include both, custom properties and "standard" properties.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#11 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AInV5zNye9uIWykSTQzG1BwGXIaz9otuks5t7-LtgaJpZM4Uafh->.
The property values of a specific product are contained in index/core catalogue2. There, a product has for each property value a field. For example, item_name or item_price. This fields have to linkage to the properties of the corresponding ontology concepts. That means, the field item_name could be the datatype property name of a chair but it is defined. In conclusion, there is no mapping possible.
I propose to have an additional field in catalogue2 or properties to add a tuple (field name in core catalogue2, property name in core properties). Then, we could create a Entity Mapping Service in catalogue-search
The text was updated successfully, but these errors were encountered: