Revamping the Backend UI for matching-context : create product targeted fields

[zhinu]

Stakes

Transitioning from regex and xpath to nocode

Context

Today, the matching context has the following fields

The fields Regex target the url whereas xpath target the Document Object Model (DOM). Those two fields, need a special expertise to be used, hence not user friendly

Wished evolution

Web pages often have a similar structure :

Product

• Title Name
• Category
• Description
• Price

Offer

• Location

The previous parts should be targetable directly from the backend.

For Title, Category, and Description the possibility would be to have the following options logical connectors

AND OR EXCEPT
i.e.
(term1 and term2) or term3 except term4

For Price, the following possibility should be to have the following mathematical functions

lower than <, greater than, lower than or equal to <=, greater than or equal to >=

Ie.
lower than or equal to <= number 1 and greater than > number 2

For the last part location, a more intuitive way would be to select cities or regions directly from a dropdown list or a map.

[lutangar]

https://schema.org/Product

[MaartenLMEM]

@lutangar I just commented the related issue on mobile repo : dis-moi/mobile#239 (comment)
Afterwards, don't you think the BO/API should do this work ?
And clients such as mobile app would make his own "advanced" translations only if BO is less appropriate to make it (for efficiency reasons, privacy reasons or others) ?

[MaartenLMEM]

Ok discussed friday, there a misunderstanding.
Let's review this and we ll make other fields later

[MaartenLMEM]

Tested on BO. It s ok... But during next step, it s important to discuss about how it will be used by extensions et mobile apps.

See for example this notice in staging
=> An important rule will habe to add on extension part is the following : If there is product name filled, ignore this matching context. Otherwise it will match on each product page of Amazon.