I'm using Product Advertising API for fetch product reviews by ASIN. Its good. But can we sort product reviews by "Date".
Because I want to display latest review on the top. Is that possible?
Can anybody help me, I stuck here from last few days.
Thanks,
Surinder
This type of call will get top reviews, including some recent.
https://www.amazon.com/reviews/iframe?akid=[AWSAccessKeyId]&alinkCode=xm2&asin=[ASIN]&atag=[ASSOCIATE_TAG]&exp=[DATE]&summary=1&truncate=1000&v=2&sig=[SIGNATURE]
You can experiment with different flags for possible sorting, however Amazon's API document does not detail sort specific parameters:
http://docs.aws.amazon.com/AWSECommerceService/latest/DG/EX_RetrievingCustomerReviews.html
Related
I am trying to create an app that will help users find restaurants/movie theaters/malls/etc. to hang out based on ratings and distance. Other than just the place itself, I would also like to know more detailed information about the place. For example, if I were to look for parks, I would also like to know if theres a basketball or tennis court there. Ratings and popularity would also be an important aspect to prioritize suggestions.
After looking through all three of the APIs, I could not really find any substantial differences other than their search limits. Could anyone really differentiate each API for me? Maybe even recommend one based on my specific need?
Thanks!
The Foursquare API would fit this use case perfectly because you can supply very specific filters through the API. Also, they have extensive coverage around the world, unlike Google or Yelp.
I would check out the venues/explore endpoint and use a categoryId of Parks. You can use a query parameter of "basketball" or "tennis" to find parks that have courts for these.
how to get available item quantity in picking ticket form in netsuite?
Thanks,
Shachi
You may want to try using item.onhand as well if you are talking about total inventory available or location.onhand if you are talking about shipping from a certain location.
You would probably be best off using the item.locationquantityavailable.
The difference in available vs. on hand is:
On hand is inventory that has yet to be shipped, but includes inventory in a picked fulfillment status, which may be allocated to other orders.
Available is inventory that is not allocated to other orders and not currently in a stage of fulfillment.
If you're using the advanced form, view source code and add element item.locationquantityavailable#label
This question is complementary to Retrieving more than 150 Instagram comments and a repetition of this older post in the group.
Currently it appears to be impossible to retrieve a full list of likes or comments for a specific post. There are no documented pagination parameters, and it is unclear how one could paginate over likes as they have no publicly exposed timestamps or time-related identifiers.
At the very least the developer documentation on http://instagram.com/developer/endpoints/comments/ and http://instagram.com/developer/endpoints/likes/ should be amended to mention that it is not possible to get a full list of either comments or likes.
Are there any workarounds for this, or plans to support pagination for the comments and likes endpoints?
If no such plans exist, how about allowing for control over the ordering of results? This would at least allow for new entries to be retrieved with reasonable confidence.
At the moment, it looks like the /likes endpoint returns results in newest to oldest order, but unfortunately the comments endpoint uses oldest to newest.
I have a project I'm working on that involves working with warehouse deals on Amazon. I've been looking and trying to find a way to pull only warehouse deals using the Product Advertising API. So, question #1 is, is there a way of achieving this?
If there is not a way, then question #2 is, if I pull a list of items, is there a way of determining whether any one of those items is a warehouse deal or not?
Essentially, I need a way to find warehouse deals using the API. Does anyone have any ideas I could try out?
In some regions Warehouse Deals are simply BrowseNodes. This is the case in DE. In UK and US it seems to be different. If your region works like DE:
1: You could include the Warehouse Deal BrowseNode in your search request. This does not work with searches in the All and Blended search indexes.
2: You can use the BrowseNodes response group in your search or ItemLookup calls to find out what BrowseNode an item belongs to. This gives you the whole ancestry of the BrowseNode. You just have to follow it up and check it against a known Warehouse Deals BrowseNodeId.
http://docs.aws.amazon.com/AWSECommerceService/2013-08-01/DG/RG_BrowseNodes.html
I use Solr for product filtering on our website,
for example you can have a product filter where you can filter database of Televisions by size, price, company etc.,. I found Solr+FilterQuery to be very efficeint for such functionality. I have a separate core that has the product info of all TVs in our DB.
I have another Core for product reviews. The review can be on a specific product type or company. So someone can write a review on a Samsung TV or Samsung customer service. So when someone searches for a text (for example "Samsung TV review" or "Samsung customer service"), I search this core.
Now I want to merge the results from the above cores. So when someone searches for 'samsung 46 lcd contrast ratio review', I esentially want to filter the TVs by Company (Samsung), then by size (46") and then find reviews that have text "contrast ratio review". I have no clue how to do this. Basically I want to merge the results by document ID and add additional colums for result 2 into result 1.
I have seen suggestions to flatten out the data but I want to use reviews index on a lot of other filters. So I am not sure if thats a good idea. Moreover if new reviews start coming in I dont want to reindex all the cores of products (even delta reindexing will touch lot of products).
Any ideas on how to acheieve this?
If I got your question right what you are looking for is JOIN functionality.
http://www.slideshare.net/lucenerevolution/grouping-and-joining-in-lucenesolr
http://wiki.apache.org/solr/Join