Re: [greenstone-users] Client/Server setup, AZList and Child nodes, Configuring AZList to ignore whole words.

From Michael Dewsnip
DateWed, 30 Mar 2005 16:29:36 +1200
Subject Re: [greenstone-users] Client/Server setup, AZList and Child nodes, Configuring AZList to ignore whole words.
In-Reply-To (42430E33-9000100-ubcic-bc-ca)
Hi Jenn, Jonathan,

You're right, this is a problem that we'll have to fix (I've
successfully reproduced it here).

I don't think we'll have time to track it down today, but in the
meantime you might like to try the GenericList classifier
(http://www.cs.waikato.ac.nz/~mdewsnip/greenstone/GenericList.pm.zip) --
I've tried this and it seems to work better. A similar configuration to
Jenn's AZCompactSectionList would be:

classify GenericList -metadata Name -leafnodesort Title
-classify_sections -alwaysgrouplastelement -buttonname People

All the best,

Michael

Jenn Cole wrote:

>>
>>
>>> 2. My child nodes are not listing alphabetically even though I have
>>> configured it to do this in the GLI. Has anyone else experienced this
>>> problem? It appears in the collect file as listed below:
>>>
>>> classify AZCompactList -metadata dc.Subject -minnesting 1
>>> -mincompact 1 -sort dc.Title -mingroup 1 -maxcompact 15
>>
>>
>> With this classifier, the classifier nodes should be sorted by
>> dc.Subject, and the child document nodes should be sorted
>> alphabetically by dc.Title. Have you
>
>
>> changed the format statement at all? ie, you are displaying dc.Title
>> for the node?
>
>
>
> Katherine & Jonathan,
>
> We are also having this problem, here is the classifier we are using:
>
> classify AZCompactSectionList -metadata Name -sort Title
> -doclevel section -mingroup 1 -allvalues -maxcompact 30 -buttonname
> people
>
> This should be based on extracted metadata . A sample of the metadata
> used for sections is included at the bottom of this email.
>
> The only change we made in the relevant format statement is the
> removal of the icon as below:
>
> format VList "<td>[link][Title][/link]</td>"
>
> We do get some Warnings during build, though they don't seem to be
> related to this problem I'm including a sample below for reference.
>
> Jenn Cole
>
> -----------
> Section metadata sample:
>
> <!--
> </Section>
> <Section>
> <Description>
> <Metadata name="Title">Page 4</Metadata>
> <Metadata name="Name">Commissioner James Pearson Shaw</Metadata>
> <Metadata name="Name">Commissioner Saumarez Carmichael</Metadata>
> <Metadata name="Name">Philip, Chief</Metadata>
> <Metadata name="Subject">Hunting</Metadata>
> <Metadata name="Subject">Fishing</Metadata>
> <Metadata name="Subject">Food</Metadata>
> <Metadata name="Subject">Indigenous/Settler Relations</Metadata>
> <Metadata name="Subject">Aboriginal Title and Rights</Metadata>
> </Description>
> -->
>
> -------------
> Build warnings <???>
>
> buildcol.pl> WARNING: SectionList::classify called multiple times for
> HASH01c564b643424703c036774d.16.2
> buildcol.pl> WARNING: SectionList::classify called multiple times for
> HASH01c564b643424703c036774d.1.6
> buildcol.pl> WARNING: SectionList::classify called multiple times for
> HASH01c564b643424703c036774d.19
>
>
> _______________________________________________
> greenstone-users mailing list
> greenstone-users@list.scms.waikato.ac.nz
> https://list.scms.waikato.ac.nz/mailman/listinfo/greenstone-users
>