Re: [greenstone-users] Greenstone v2.53 released!

From Chaitra Rao
DateThu, 19 May 2005 15:11:08 +0530 (IST)
Subject Re: [greenstone-users] Greenstone v2.53 released!
In-Reply-To (428BB620-7040701-cs-waikato-ac-nz)
Hi Katherine,
Thank you so much for the timely help. I think we are getting close to
solving the problem :) But there are still a few glitches. I made the
changes that you'd suggested and I get the foll message when I build from
command line:

doclevel = document
Saving the document text
ArcPlug: processing D:Program
Filesgs6collect estarchivesarchives.inf
GAPlug: processing HASH01ed.dirdoc.xml
**** ARGS = text Doc D:Program Filesgs6collect estbuilding dummy
Stats (Compressing text from text)
Total bytes in collection: 256531
Total bytes in text: 336201

*** building index allfields,allfields,text,Title,Source at level Doc in
subdirectory didx

creating index dictionary (lucene_passes -I1)
ArcPlug: processing D:Program
Filesgs6collect estarchivesarchives.inf
GAPlug: processing HASH01ed.dirdoc.xml
--->Can't open perl script "D:Program": No such file or directory<---
Stats (Creating index allfields,allfields,text,Title,Source)
Total bytes in collection: 256531
Total bytes in allfields,allfields,text,Title,Source: 90374

*** creating the info database and processing associated files
ArcPlug: processing D:Program
Filesgs6collect estarchivesarchives.inf
GAPlug: processing HASH01ed.dirdoc.xml

*** creating auxiliary files

The line marked between --> <-- suggests that it can't it open some perl
script. Which script is this referring to? I have put the quotes as you
had suggested. The build.cfg file in the "building" directory shows
"buildtype lucene" but the directory called "didx" is empty.It also
contains 2 other dirs called assoc and text. Please help.

Regards,
Chaitra

On Thu, 19 May 2005, Katherine Don wrote:

> Hi
>
> When you built on the command line, did you copy the building directory
> to index? You may have been looking at the old mgpp index, while the new
> indexes were built in the building directory.
>
> I have just fixed the GLI so that you can select lucene from the search
> types panel, and it doesn't delete the buildtype line. This will be
> available in the next release
>
> Regarding the error messages in your following email,
>
> there are two lines in gsdl/perllib/lucenebuilder.pm
> $full_lucene_passes_exe = "perl.exe -S $lucene_passes_exe";
>
> Try changing them both to
> $full_lucene_passes_exe = "perl.exe -S "$lucene_passes_exe"";
>
> (ie adding quotes around the $lucene_passes_exe bit)
>
> Does this help?
> Regards,
> Katherine
>
> Chaitra Rao wrote:
> > Hi Katherine,
> > Thanx for the info. I followed the steps you mentioned and the output
> > of buidcol.pl gave a message that it was doing "lucene_passes". However,
> > the index directory still doesn't seem to be containing lucene indexes.
> > The index dir looks something like this
> >
> > index- |assoc
> > |idx----| test.i,test.ib1,test.ib2,test.ic,...test.invf.state.357
> > |text
> >
> > None of these indexes look like lucene indexes which normally are in the
> > form _a0.cfs,deletable,segments, etc. Something is still missing. Please
> > help!
> >
> > The build.cfg file has the foll contents (indicating that the buildtype
> > is still mgpp and not lucene...may be problem lies here :)):
> >
> > builddate1116421441
> > buildtypemgpp
> > indexfieldmapallfields->ZZtext->TXTitle->TISource->SO
> > indexfieldsallfieldstextTitleSource
> > indexlevelsDocDoc
> > indexmapallfields,text,Title,Source->idx
> > numbytes256531
> > numdocs1
> > textlevelDoc
> >
> > GLI modifies the collect.cfg file each time I build using the GLI, and
> > deletes the "buildtype lucene" line.Can you also do something about this.
> >
> > Thanxks!
> >
> > Regards,
> > Chaitra
> >
> > On Wed, 18 May 2005, Katherine Don wrote:
> >
> >
> >>Hi Chaitra
> >>
> >>There is a bug in Greenstone that meant that if you have searchtype in
> >>your config file, then it didn't use lucene.
> >>
> >>In gsdl/bin/script/buildcol.pl
> >>around line 258, change
> >>
> >> if (defined $collectcfg->{'searchtype'}) {
> >> $buildtype = "mgpp";
> >> }
> >> elsif (defined $collectcfg->{'buildtype'}) {
> >> $buildtype = $collectcfg->{'buildtype'};
> >>} else {
> >> $buildtype = "mg"; #mg is the default
> >>}
> >>
> >>to
> >>if (defined $collectcfg->{'buildtype'}) {
> >> $buildtype = $collectcfg->{'buildtype'};
> >>} elsif (defined $collectcfg->{'searchtype'}) {
> >> $buildtype = "mgpp";
> >>} else {
> >> $buildtype = "mg"; #mg is the default
> >>}
> >>
> >>Also, there is a bug in the c++ code for querying - you can get around
> >>it by making sure that the buildtype line comes after the searchtypes
> >>line in the config file.
> >>
> >>Please let us know if it still doesn't work after these changes.
> >>
> >>Regards,
> >>Katherine
> >>
> >>Chaitra Rao wrote:
> >>
> >>>Hi Katherine,
> >>>I have put buildtype lucene in the config file, and checked the
> >>>"enable advanced search" option. The indexes don't look anything like
> >>>lucene indexes!!! Doesn't look like there's much diff between mgpp indexes
> >>>and the "lucene" indexes built by greenstone.The only difference that I
> >>>have seen is that there are 3 directories viz., assoc, idx and text,
> >>>unlike typical mgpp indexes that build arnd 6-7 directories. Besides, the
> >>>build.cfg file shows buildtype mgpp!!! I fail to understand what's
> >>>happening. Lucene indexes normally have files that look something like
> >>>_a0.cfs, deletable,segments, etc.
> >>>The build.cfg has the foll contents:
> >>>builddate1116313884
> >>>buildtypemgpp
> >>>indexfieldmapallfields->ZZtext->TXTitle->TISource->SO
> >>>indexfieldsallfieldstextTitleSource
> >>>indexlevelsDocDoc
> >>>indexmapallfields,text,Title,Source->idx
> >>>numbytes1206
> >>>numdocs2
> >>>textlevelDoc
> >>>
> >>>I get the same results even when I build it from the command line. Please
> >>>help!
> >>>
> >>>Regards,
> >>>Chaitra
> >>>
> >>>On Tue, 17 May 2005, Katherine Don wrote:
> >>>
> >>>
> >>>
> >>>>Hi Chaitra
> >>>>
> >>>>First check that the 'buildtype lucene' line is in your config file.
> >>>>Then try building the collection on the command line. Does it use lucene
> >>>>this time?
> >>>>
> >>>>Regards,
> >>>>Katherine
> >>>>
> >>>>Chaitra Rao wrote:
> >>>>
> >>>>
> >>>>>Hi Katherine,
> >>>>> I was able to configure greenstone to use lucene as you'd suggested.
> >>>>>But the GLI seems to be building indexes for mgpp rather than lucene
> >>>>>indexes. Even the index directory seems to be in mgpp format and not a
> >>>>>lucene index format. Why is it so? Is it a bug? What do I need to do to
> >>>>>rectify it? Please help.
> >>>>>
> >>>>>Regards,
> >>>>>Chaitra
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>On Mon, 7 Mar 2005, Katherine Don wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>Hi
> >>>>>>>
> >>>>>>>You need to set up the collection configuration in the same way as for
> >>>>>>>mgpp, then add
> >>>>>>>buildtype lucene
> >>>>>>>to the config file.
> >>>>>>>
> >>>>>>>If you are using the GLI, you need to 'enable advanced searching' in the
> >>>>>>>search types panel in the design pane.
> >>>>>>>Once you have configured your indexes, and before you build the
> >>>>>>>collection, you need to close the collection in GLI, edit the config
> >>>>>>>file to add the 'buildtype lucene' line, then reopen the collection and
> >>>>>>>build it.
> >>>>>>>You will only need to add the lucene directive once, as once it is in
> >>>>>>>the config file, it will stay there.
> >>>>>>>
> >>>>>>>I am not sure if it is unicode compatible - try it and see. Please let
> >>>>>>>us know if its not.
> >>>>>>>
> >>>>>>>Regards,
> >>>>>>>Katherine Don
> >>>>>>>
> >>>>>>>Chaitra Rao wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>Hi,
> >>>>>>>>I wanted to know how to enable Lucene search in Greenstone. I couldn't
> >>>>>>>>find any documentation on this. Is the lucene support provided with
> >>>>>>>>greenstone unicode compatible? If not can u please tell me how I can do
> >>>>>>>>this?
> >>>>>>>>
> >>>>>>>>Regards,
> >>>>>>>>Chaitra
> >>>>>>>>
> >>>>>>>>On Wed, 2 Mar 2005, Emanuel Dejanu wrote:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>Hello,
> >>>>>>>>>
> >>>>>>>>>I think that will be good if you can update also greenstone project in
> >>>>>>>>>freshmeat.net.
> >>>>>>>>>The last update is from Wed, Jul 2nd 2003 21:13 PDT (1 year, 8 months ago)
> >>>>>>>>>:-D
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>http://freshmeat.net/projects/greenstone/
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>Best regards,
> >>>>>>>>>
> >>>>>>>>>Emanuel
> >>>>>>>>>
> >>>>>>>>>-----Original Message-----
> >>>>>>>>>From: greenstone-devel-bounces@list.scms.waikato.ac.nz
> >>>>>>>>>[mailto:greenstone-devel-bounces@list.scms.waikato.ac.nz] On Behalf Of
> >>>>>>>>>Michael Dewsnip
> >>>>>>>>>Sent: Wednesday, March 02, 2005 6:42 AM
> >>>>>>>>>To: greenstone-users@list.scms.waikato.ac.nz;
> >>>>>>>>>greenstone-devel@list.scms.waikato.ac.nz
> >>>>>>>>>Subject: [greenstone-devel] Greenstone v2.53 released!
> >>>>>>>>>
> >>>>>>>>>Hello everyone,
> >>>>>>>>>
> >>>>>>>>>We're pleased to announce that the Windows/Linux/Source distributions of
> >>>>>>>>>Greenstone v2.53 are now available for download from our sourceforge
> >>>>>>>>>page: http://sourceforge.net/projects/greenstone, or via
> >>>>>>>>>http://www.greenstone.org
> >>>>>>>>>
> >>>>>>>>>This release contains a lot of new functionality, and is therefore likely to
> >>>>>>>>>be a little less stable than usual. Please give it a good workout and report
> >>>>>>>>>any bugs you find (see below), as we want the next release of Greenstone
> >>>>>>>>>(version 2.60) to be a stable release.
> >>>>>>>>>
> >>>>>>>>>Important changes in this release include, in no particular order:
> >>>>>>>>>
> >>>>>>>>>- A brand new installer (see below)
> >>>>>>>>>- Much improved GLI compatibility with Java 1.5.0
> >>>>>>>>>- The ability to import documents exported from DSpace, and vice versa
> >>>>>>>>>- A smarter HTMLPlug that blocks the images in the HTML files it processes,
> >>>>>>>>>and no others
> >>>>>>>>>- New GLI metadata sets: Qualified Dublin Core, NZGLS, AGLS, and RFC 1807
> >>>>>>>>>- Lucene building support (for real this time!)
> >>>>>>>>>- An improved and much more bandwidth-efficient GLI applet
> >>>>>>>>>- Support for subfields in the Greenstone Editor for Metadata Sets (GEMS)
> >>>>>>>>>- ...and many many other improvements and bug fixes
> >>>>>>>>>
> >>>>>>>>>The new installer for Greenstone is built using the same multi-platform
> >>>>>>>>>installation technology that has been used for the Greenstone Language
> >>>>>>>>>Packs. The obvious advantage of this is that we only have to maintain one
> >>>>>>>>>installer, rather than one for each of our target platforms (Windows, Linux,
> >>>>>>>>>Mac). Additionally, this new technology makes it easier for us to release
> >>>>>>>>>patches and upgrades.
> >>>>>>>>>
> >>>>>>>>>The disadvantage of the new installer is that it requires Java to be
> >>>>>>>>>installed on your system. Most machines already have Java installed, but if
> >>>>>>>>>yours doesn't you can download it for free from http://java.sun.com.
> >>>>>>>>>You will also need Java to run the Greenstone Librarian Interface, which we
> >>>>>>>>>recommend you use. (On Linux machines, you can run the old Unix/Install.sh
> >>>>>>>>>installer instead of the new setupLinux.bin if
> >>>>>>>>>necessary.)
> >>>>>>>>>
> >>>>>>>>>We want to ensure that Greenstone works well for you. Please report any
> >>>>>>>>>problems to greenstone@cs.waikato.ac.nz, or on one of the Greenstone mailing
> >>>>>>>>>lists.
> >>>>>>>>>
> >>>>>>>>>All the best,
> >>>>>>>>>
> >>>>>>>>>Michael
> >>>>>>>>>On behalf of the Greenstone team
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>PS New versions of the Export collection package, Greenstone Language Pack,
> >>>>>>>>>and Mac OS X binary distribution will follow over the next couple of weeks.
> >>>>>>>>>
> >>>>>>>>>_______________________________________________
> >>>>>>>>>greenstone-devel mailing list
> >>>>>>>>>greenstone-devel@list.scms.waikato.ac.nz
> >>>>>>>>>https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-devel
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>_______________________________________________
> >>>>>>>>>greenstone-users mailing list
> >>>>>>>>>greenstone-users@list.scms.waikato.ac.nz
> >>>>>>>>>https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-users
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>_______________________________________________
> >>>>>>>>greenstone-users mailing list
> >>>>>>>>greenstone-users@list.scms.waikato.ac.nz
> >>>>>>>>https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-users
> >>>>>>>>
> >>>>>>>
> >>>>>>_______________________________________________
> >>>>>>greenstone-users mailing list
> >>>>>>greenstone-users@list.scms.waikato.ac.nz
> >>>>>>https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-users
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >
> >
> >
>