Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration of all properties of a product in core properties #9

Open
marcofranke opened this issue Jun 5, 2018 · 3 comments
Open
Labels
data schema Related to the NIMBLE ontology and generated cores/index high priority
Milestone

Comments

@marcofranke
Copy link

The index (core) properties defines a set of properties for each concept. The given set of properties doesn't contain properties in which the name of the property is set during the product upload. Examples are e.g.:

  1. The user can set the label "width" and a value for the property dimension of a product.
  2. Custom properties have a label and a value which can be set

The catalogue-search calls this kind of properties "virtual proeprties", because the property in the first example would be not dimension but width and would have a specific value.

These kinds of properties and the properties of eclass are not contained yet. For a semantic (hierachical search) the are needed.

@marcofranke marcofranke added high priority data schema Related to the NIMBLE ontology and generated cores/index labels Jun 5, 2018
@marcofranke marcofranke added this to the Release 3.0 milestone Jun 5, 2018
@suatgonul
Copy link
Member

We will have an additional index field named item_properties including the names of the custom properties via an LDPath expression similar as follows:

item_properties = cac:GoodsItem / cac:Item / cac:AdditionalItemProperty[cbc:ItemClassificationCode / cbc:listID is "Custom"] / cbc:Name :: xsd:string;

@marcofranke
Copy link
Author

I think , this is a good starting point. With respect to your last ontology, there are more than just custom properties which have to be considered. I mentioned in my issue description also dimension. ( urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2#Dimension). Are going to add it also?

@iot365
Copy link
Member

iot365 commented Jun 11, 2018

Yes, the idea is to have an "or" between the "custom" and the "standard" properties. I'm just trying to add such index in the staging environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data schema Related to the NIMBLE ontology and generated cores/index high priority
Projects
None yet
Development

No branches or pull requests

3 participants