I came along this module because it can be used with the Feeds module. I am wondering about a usecase for this combination of modules, I have no clue. In what situation is this module helpful with feeds?

Comments

pounard’s picture

pounard
Primary language French
commented

Actually, the description may be confusing. We use feeds alone, to let users import content, which can lead to thousands of pieces of content pretty quickly.

As the site grows, the SolR index does too, then we use Solace Node Rereference to populate node reference fields selected amond all the site content using SolR complex requests, user configured. Queries can fetch back feeds item imported in the Drupal database (or not, this is configurable).

It's two distinct features, but which fits well together, as the site grows with content, using complex (and maybe accurate, depends on chat the user does) SolR queries become quite usefull.

hanno’s picture

hanno commented

Thank you for your explanation. As I understand, Feeds is useful because Solace Node reference becomes more useful with fast growing content.

I am still curious about this module. Honestly, I have still no idea of a usecase. It seems interesting. Hope to see a show case in the future :).

pounard’s picture

pounard
Primary language French
commented

A quite simple use case is a "Content that looks like this one" node list, being kept in a node reference field. This list will be automatically feeded by the Solace Node Reference module, using a SolR query, and the referer node owner will keep the power to rearrange automatically feeded content, and will also be able to enable or disable the automatic content feeding in the node reference field.

hanno’s picture

hanno commented

Ok, so
1. the editor can decide on a per node basis, if related content in a node reference field will show up automatically and refreshed by a solr query, or that it will be filled once (or never).
2. the editor can define a query that best will match the future results.

Is the following setup a typical use case?
- You have a website about national law with automatic feeds of new legislation.
- You have some pages with topics about legal issues, for example 'copyright'
- the editor can define a query in the node reference field to match automatically related legislation in that area
- it will automatically fill with new relevant legislation when it arrives in the feed.
- the editor can manually sort the relevant legislation, new legislation will be added beneath
- in some cases you might want to freeze this functionality, and want manually add the legislation

pounard’s picture

pounard
Primary language French
commented

For the first line, you are totally right.

For the set of use cases you gave, I would say, I don't know all about your project, so I cant decide for you :) Further, I'd say that it could fit, you have to take account that the module will populate node reference fields with content matching by searching the index in SolR, it's not quite like an SQL query, matches are often fuzzy, which means you can easily fetch content that looks like something that you want in the point of view of the indexer, but which in reality is not what you want (automated content feeding needs regular human eye review).

I have to warn you about something (there is no good module without warnings!), this module has been developed against a development version of the 'apachesolr', some monthes ago, which act for it as our indexer (send Drupal content to the SolR instance), because this module has evolved, there are few fatal errors that emerged in the current stable release of Solace Node Reference. I'm actually looking forward fixing it, within the next weeks, but I cant give you an exact date (it will be before end of august).

EDIT: By the way, if you feel the need to test it, and experience any problems, please report it opening issues, I will aptempt to fix it, or at least give you support, as my first official user! Any remarks or bug reports are welcome.

pounard’s picture

pounard
Primary language French
commented
Status: Active » Closed (fixed)

Closing the support request.