Hi Louis,

I was waiting for the GSearch heavyweights to reply, but here's a
starter for you.  The config/index/BasicIndex directory contains a
number of style sheets that can be tailored in order to tell GSearch
what to index.  The DemoFoxmlToLucene.xslt sheet can be edited to
populate the GSearch index based on the datastreams present in your
FOXML files.

As for searching the whole repository, you can issue queries via the
rest interface on any field that GSearch has indexed.  For instance, a
query of:

dc.title:"search-term"

will look for "search-term" in all dc.title fields in all records.  If
you've configured GSearch to index the full text by tailoring the
stylesheet (and updating the index afterward), you should be able to
find what you want.

Jason

On 8/31/09 9:06 PM, Louis Malenica wrote:
> Just another couple of questions re Gsearch if I could throw it out there.
> 
> - Now that I have indexed the repository, how can I run a general full text 
> search against GSearch, ie the whole repository and not just one object?
> 
> - Is gsearch capable of being harvested by an OAI front end?
> 
> Thanks everyone.
> 
> Louis.
> 
> -----Original Message-----
> From: Louis Malenica 
> Sent: Tuesday, 1 September 2009 9:46 AM
> To: [email protected]
> Subject: RE: [Fedora-commons-users] Generic Search error
> 
> Thanks Jason,
> 
> That seems to have sorted that issue. I'm running Fedora on Windows btw, so 
> if anyone has any "gotchas" with Windows feel free to share.
> 
> Windows server 2003 R2.
> 
> Thanks.
> 
> Louis.
> 
> -----Original Message-----
> From: Jason Nugent [mailto:[email protected]] 
> Sent: Monday, 31 August 2009 8:47 PM
> To: Louis Malenica
> Cc: [email protected]
> Subject: Re: [Fedora-commons-users] Generic Search error
> 
> Hi Louis,
> 
> When you initially set up GSearch, there are no segments in the search
> index.  If you navigate to the /rest interface, there is an option to
> "create from empty" on the updateIndex page. That option will initially
> create an empty index, after which you can load documents.
> 
> Jason
> 
> On 8/31/09 12:08 AM, Louis Malenica wrote:
>> Hi,
>>
>>  
>>
>> I keep getting the error:
>>
>>  
>>
>> IndexReader open error indexName=BasicIndex : ; nested exception is:
>> java.io.FileNotFoundException: no segments* file found in
>> org.apache.lucene.store.fsdirect...@c:\Fedora\gsearch\BasicIndex: files:
>>
>>  
>>
>> When navigating to http://..../fedoragsearch/rest
>>
>>  
>>
>> Does anyone have any ideas about this? The C:\Fedora\gsearch\BasicIndex
>> is empty, should it be populated on startup?
>>
>>  
>>
>> Config for gsearch attached. Tomcat is not complaining on startup.
>>
>>  
>>
>> Thanks.
>>
>>  
>>
>> Louis.
>>
>>  
>>
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
>> trial. Simplify your report design, integration and deployment - and focus 
>> on 
>> what you do best, core application coding. Discover what's new with 
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Fedora-commons-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
> 

-- 
Jason Nugent
Systems Programmer/Database Developer
Electronic Text Centre
University of New Brunswick
[email protected]
(506) 447 3177

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to