This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
[BUG-10688] [SLM Beta Search] Marketplace Beta Results do not take into account frequency of Sale when ranked by "Relevance" #990
Labels
Steps to Reproduce
Just doing a simple search in the BETA Marketplace engine.
Actual Behavior
BETA MP search results "Relevance" ranking no longer seems to receive any weight or bearing from sales frequency. Best selling objects are last in my shop. My best selling items are dead last in overall catagory search order. I can understand some slight rearrangement due to search algorithm changes but seriously dead last for all the most popular items?? Did someone accidentally put a negative in for the sales popularity 'influence' in the Relevance ranking?
BETA MP search results prioritize store and creator names over actual product names and descriptions in relevance search rankings making it borderline impossible to actually find anything that you're actually searching for
Expected Behavior
I was expecting relevance to maintain sales frequency and positive review rating in the searches as one of the primary criteria.
I was expecting a more integrated / streamlined review experience which made it so I didn't have to actively interact with customers in order to receive a review.
I was expecting to have item names be relevant and have creator/store names only show up when searching by creator.
I was expecting a handling of "DEMO" items so they aren't part of standard search results.
I was expecting a behavior similar to any other shopping experience online in 2015 ( Like Amazon.com for example! )
In fact I heavily question why SL isn't just paying Amazon or Google to handle their search engine and database statistics like the rest of the world does when they need this type of service. Why is SL attempting to reinvent the wheel here?
Other information
THIS LITERALLY HAS THE POTENTIAL TO DESTROY ENTIRE BUSINESSES, MINE AND 100's OF OTHERS IN SL. PLEASE PLEASE PLEASE TAKE OUR LIVELIHOOD INTO CONSIDERATION WHEN IMPLEMENTING THIS CHANGE.
Links
Related
Original Jira Fields
The text was updated successfully, but these errors were encountered: