Open marcofranke opened 6 years ago
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 Androidhttps://aka.ms/ghei36
On Tue, Jun 12, 2018 at 6:06 PM +0200, "fstroh" notifications@github.com<mailto:notifications@github.com> 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 GitHubhttps://github.com/nimble-platform/common/issues/11#issuecomment-396639304, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AInV5zNye9uIWykSTQzG1BwGXIaz9otuks5t7-LtgaJpZM4Uafh-.
I would rather take the Name instead of the URI, but I can discuss that with @dglachs tomorrow.
Depends on #13
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