Closed (fixed)
Project:
Nodequeue
Version:
6.x-2.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
23 Apr 2009 at 01:00 UTC
Updated:
31 Aug 2009 at 23:00 UTC
Jump to comment: Most recent file
This patch adds Solr boosting selection to the apachesolr boosting form. And it boosts the queries, thus allowing nodes in a nodequeue to be boosted so they appear more often in search results.
This patch is a lil involved because I ran into a nasty static cache in nodequeue_load_subqueues_by_reference(). Added reset param and pass in reset only when nodequeue_get_subqueues_by_node says this is a different nid then before.
It also add as a if (module_exists) when a node is added/removed to a subqueue. This is so we can mark the node as dirty so it can be indexed later.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | nodqueue.patch | 1.02 KB | Scott Reynolds |
| #3 | booster.png | 73.17 KB | Scott Reynolds |
| patch49.patch | 5.26 KB | Scott Reynolds |
Comments
Comment #1
ezra-g commentedI wasn't sure what it means so I googled "solr boosting selection" and this very node is the first result :D!
I'm afraid the maintainer needs more info here...
What does this patch do?
Comment #2
Scott Reynolds commentedhaha ok. So this will give all nodes in the specified node queue more weight, making them more likely to show up in the search results.
So if I have two nodes with a body of "test". The second node is in a boosted nodequeue. When I search for test, the first result will be the node in the nodequeue cause its been boosted.
It bias' the nodes in the queue. So two identical nodes, one in the queue and one not in the queue, the one in the queue will be the above the other one
Comment #3
Scott Reynolds commentedSee attached screen shot. Its of the form. Apachesolr project itself comes with the standard sticky and promoted to front page boosting. This adds that same boosting to nodes in a nodequeue.
Comment #4
ezra-g commentedI changed the $reset parameter to $bypass_cache to be consistent with the other nodequeue api functions. this is committed. Thanks a lot!!!
Comment #5
ezra-g commentedps one hunk failed for some reason so I also rerolled this.
Comment #7
Scott Reynolds commentedQuick follow up. Shouldn't put the facet field in the query more then once, it isn't needed. (thats what i get for testing with only one nodqueue).
Comment #8
ezra-g commentedLooks good. Committed, thanks!