What is a good way to test combining search results?  For example, the combined search box dropdown config has Google, but by comparison the combined results only have Summon (not available to the public).  

Currently, when I copy the stock file and enable every line in:
   local/config/vufind/combined.ini

I don't see any difference in the application behavior or logs.  Even when I add a new nonsense section, nothing changes.  Shouldn't that at least give a warning like "WARN: No back end for combined section 'nonsense'.  Ignoring."? 

Or is there a related portion in the general config that is required?

--joe


On Fri, Jul 19, 2013 at 2:56 AM, <hatop@ub.uni-marburg.de> wrote:


  Hi David, Hi Demian,

  It wasnt clear to me, if there is already build some magic into
  the backend to handle xml responses.

  I will have no time to dig deeper into this the next weeks, and it
  may even be better to have solr talking json as a requirement.

  So, thanks for the clarification !

  -- Goetz.

On Wed, Jul 17, 2013 at 02:22:25PM +0200, David Maus wrote:
>Hi Demian,
>Hi Goetz,
>
>At Tue, 16 Jul 2013 15:00:03 +0000,
>Demian Katz wrote:
>>
>> David may be able to comment more specifically on this, but the assumptions about JSON responses are built into the search backend and should be reasonably well isolated.  If you look at the VuFindSearch\Backend\Solr\Backend class and the related VuFindSearch\Backend\Solr\Response\Json\* classes, you'll get an idea of what would need to be adjusted/overridden to add XML support.  At a glance it looks like there may be some classes in the Json namespace that are actually more generic.
>>
>> Let me know if you have specific questions on what to do next -- but I'm optimistic that it may be possible to get native XML support built in with relatively little work.
>>
>> - Demian
>>
>> > -----Original Message-----
>> > From: hatop@ub.uni-marburg.de [mailto:hatop@ub.uni-marburg.de]
>> > Sent: Monday, July 15, 2013 5:47 AM
>> > To: Demian Katz
>> > Cc: vufind-tech@lists.sourceforge.net
>> > Subject: Re: [VuFind-Tech] Combining search types
>> >
>> >
>> >    That looks really good ! I personally prefer the drop-downs,
>> >    but as you know, every fool is different.
>> >
>> >    I am wondering about how to integrate a solr index (from a third party)
>> >    which does not talk json but xml. By removing the wt=json
>> >    from Solr/Connector.php, I am able to receive a xml response
>> >    from the index, but then VuFind JSON decoding fails of course.
>> >    Is that easy to handle (e.g. by some converter somewhere in the
>> >    search backend) or should I go back to VuFind 1.x for that ?
>> >
>
>Instead of converting XML to JSON I would rather go for a Decorator
>approach: Write a RecordCollection that is instantiated with the
>deserialized XML of the SOLR response and reads the respective
>elements (e.g. total number of records found).
>
>You also need a RecordCollectionFactory that is called with the
>deserialized XML response, creates the RecordCollection and adds the
>records to the collection.
>
>With these two classes you have the absolute minimum: You can search
>and retrieve records from SOLR.
>
>Deserialization is the tricky part: Backend::deserialize() is not only
>used to create record collections but also in terms() and
>alphabeticBrowse().
>
>Hum. Maybe an abstract factory?
>
>VuFindSearch\Backend\Solr\Response\Json\AbstractFactory::factory($response)
>
> - deserializes the response
> - selects the factory instance or function depending on the response
>
>Best,
>  -- David
>
>
>> >    -- Goetz.
>> >
>> > On Wed, Jul 10, 2013 at 04:57:35PM +0000, Demian Katz wrote:
>> > >I have completed porting all of Villanova's custom code for combining
>> > multiple search types into VuFind 2.  While the original 1.x Villanova code
>> > was hard-coded and messy, the new implementation is better-designed and fully
>> > configurable.  You can now set up multi-column result screens, tabbed search
>> > boxes, and flexible multi-purpose search type drop-downs.
>> > >
>> > >Some basic documentation has been added here:
>> > >
>> > >http://vufind.org/wiki/vufind2:combining_search_types
>> > >
>> > >All of this functionality will be released next month as part of VuFind 2.1.
>> > Please let me know if you have questions about anything!
>> > >
>> > >- Demian
>> >
>> > >-----------------------------------------------------------------------------
>> > -
>> > >See everything from the browser to the database with AppDynamics
>> > >Get end-to-end visibility with application monitoring from AppDynamics
>> > >Isolate bottlenecks and diagnose root cause in seconds.
>> > >Start your free trial of AppDynamics Pro today!
>> > >http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> >
>> > >_______________________________________________
>> > >Vufind-tech mailing list
>> > >Vufind-tech@lists.sourceforge.net
>> > >https://lists.sourceforge.net/lists/listinfo/vufind-tech
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Vufind-tech mailing list
>> Vufind-tech@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/vufind-tech

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Vufind-tech mailing list
Vufind-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vufind-tech