Hi John,
Sorry for the drought in responses.
I'm not an expert in this section of the code, but it looks like the
predefined types (for the indexer) are:
- text (default)
- timestamp
- date
http://fisheye3.atlassian.com/browse/dspace/dspace/branches/dspace-1_6_x/dspace-api/src/main/java/org/dspace/search/DSIndexer.java?r=HEAD#l971
So its definitely ignoring your name:name-space:type of integer or float.
I'm not sure what the solution to this is. I was wondering if a condition
could be added for when (type = "integer") or (type = "float"), but I'm not
sure what you would need to do in the code to get it to work well with
numeric info.
Peter Dietz
Systems Developer/Engineer
Ohio State University Libraries
On Tue, Jun 22, 2010 at 4:35 PM, John Preston <[email protected]> wrote:
> I sent the email some weeks ago with no response. Am I to take it that no
> one is able to help me?
>
> John
>
> ---------- Forwarded message ----------
> From: John Preston <[email protected]>
> Date: Wed, Jun 9, 2010 at 5:50 PM
> Subject: Lucene search indexes
> To: [email protected]
>
>
> Hi, I am using DSpace 1.6 and am trying to create some specific indexes and
> use them via the query box. So for example I define an index in the
> dspace.cfg file as :
>
> search.index.13 = indexname:dc.element.qualifier
>
> where dc.element.qualifier is replaced by my metadata field name. Now in
> the query string I can refer to this index by the syntax:
>
> indexname:xxxx
>
> This works OK when the metadata field containes strings. However I need
> some to be integers and floating point values, so I can refer to them in
> range statements such as:
>
> indexname:[1.3 TO 5.6]
>
> When I put floating point values in the metada fields and try the lucene
> range statement query syntax it gives unexpected results. it finds the items
> sometimes when the value is outside the range and sometimes when it is
> inside the range depending on what the range values are.
>
> Now I saw in the codebase that the search.index.n syntax allows a type
> entry such that the following sahould create a floating point index field:
>
> search.index.13 = indexname:dc.element.qualifier:float
>
> However this does not work as expected as the range statement does not
> return the correct items as per range values. Can anyone say what I am doing
> wrong, or not understanding.
>
> John
>
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit. See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
