Is there anything that can be done to get more accurate product listings when you are deeper in the listings. For instance, http://www3.shopping.com/xDN-sport_and_outdoor--sp_type_fishing-fishing_rods should be fishing rods, but get a fooseball table in the list and a number of other products that are completely unrelated. I would like to use the API to pull products at this level, but the inaccuracy of the results is making me hesitate?
You can add a keyword (e.g. 'fishing rod') to the query which should filter the results even further, but honestly you shouldn't have to. Unfortunately, there seem to be a lot of miscategorizations for this category/attribute - I've reported it to our catalog team.
Thank you for the response, and reporting it. I was able to add some additional keyword filters to get better results in rods, but in an area like fishing hooks, there isn't much i can do with adding keywords, and it's showing boxing gloves (as the top item even). I will continue to build out my project and hope the catalog team can do something on their end. Is there a way to tell the api to ignore products? I would like to do that in the query so that it doesn't interfere with the item count / pagination.
The API does not currently have the ability to filter specific products. Nor does it support re-ordering of attribute values when using 'showAllValuesForAttr'. However you should be able to do this in your code, as we provide the matchingItemsCount for each value in the response.
Hello,
Is there anything that can be done to get more accurate product listings when you are deeper in the listings. For instance, http://www3.shopping.com/xDN-sport_and_outdoor--sp_type_fishing-fishing_rods should be fishing rods, but get a fooseball table in the list and a number of other products that are completely unrelated. I would like to use the API to pull products at this level, but the inaccuracy of the results is making me hesitate?
-Reggie
Ryan – 7/2/09 4:25 pm
Hi Reggie -
You can add a keyword (e.g. 'fishing rod') to the query which should filter the results even further, but honestly you shouldn't have to. Unfortunately, there seem to be a lot of miscategorizations for this category/attribute - I've reported it to our catalog team.
--ryan
Reggie – 7/3/09 6:53 am
Thank you for the response, and reporting it. I was able to add some additional keyword filters to get better results in rods, but in an area like fishing hooks, there isn't much i can do with adding keywords, and it's showing boxing gloves (as the top item even). I will continue to build out my project and hope the catalog team can do something on their end. Is there a way to tell the api to ignore products? I would like to do that in the query so that it doesn't interfere with the item count / pagination.
Reggie
Reggie – 7/3/09 7:37 am
Another question: When using the showAllValuesForAttr, is there way to maintain the order by matchcount instead of the alpha order?
Ryan – 7/8/09 1:16 pm
Hi Reggie -
The API does not currently have the ability to filter specific products. Nor does it support re-ordering of attribute values when using 'showAllValuesForAttr'. However you should be able to do this in your code, as we provide the matchingItemsCount for each value in the response.
--ryan