search

nimble-platform / common

Common modules that can be accessed by the other NIMBLE services.
Apache License 2.0
2 stars 4 forks source link

Redundant properties for each uploaded product (if assigned to a category) #12

Open marcofranke opened 6 years ago

marcofranke commented 6 years ago

Each specific product (in Marmotta) is an Item and has a reference to a concept or eclass. Beyond this reference, there are properties like name or price which are defined both in Item and within the referenced concept. To have just one occurrence of the "same" property, we need a rule which property has to be used and which have to be ignored.

iot365 commented 6 years ago

In the "normal" case, the user should just add properties once for each product. If the same property is specified more than once using different concepts/names, we should already catch this by input validation, if possible.

marcofranke commented 6 years ago

Does it means there will be a check in the index: properties which checks whether a property has a value for any induvidual? If yes, I get the property and if not it isn't included in the index? then, we could seperate redundant properties like name or price in meaningful and meamingless for the product search.

iot365 commented 6 years ago

Yes, within the catalogue2 index, only properties that have been used in any catalogue will be available - otherwise the currently implemented LDPath statement does not find a match. I think that it makes sense for the user, if only "existing" properties can be selected (as in the classical faceted search).