remove from list

2010-06-23 Thread Susan Rust 
Hey SOLR folks -- There's too much info for me to digest, so please  
remove me from the email threads.


However, if we can build you a forum, bulletin board or other web- 
based tool, please let us know. For that matter, we would be happy to  
build you a new website.


Bill O'Connor is our CTO and the Drupal.org SOLR Redesign Lead. So we  
love SOLR! Let us know how we can support your efforts.


Susan Rust
VP of Client Services

If you wish to travel quickly, go alone
If you wish to travel far, go together

Achieve Internet
1767 Grand Avenue, Suite 2
San Diego, CA 92109

800-618-8777 x106
858-453-5760 x106

Susan-Rust (skype)
@Susan_Rust (twitter)
@Achieveinternet (twitter)
@drupalsandiego (San Diego Drupal Users' Group Twitter)



This message contains confidential information and is intended only  
for the individual named. If you are not the named addressee you  
should not disseminate, distribute or copy this e-mail. Please notify  
the sender immediately by e-mail if you have received this e-mail by  
mistake and delete this e-mail from your system. E-mail transmission  
cannot be guaranteed to be secure or error-free as information could  
be intercepted, corrupted, lost, destroyed, arrive late or incomplete,  
or contain viruses. The sender therefore does not accept liability for  
any errors or omissions in the contents of this message, which arise  
as a result of e-mail transmission. If verification is required please  
request a hard-copy version.














On Jun 23, 2010, at 1:52 AM, Mark Allan wrote:


Cheers, Geert-Jan, that's very helpful.

We won't always be searching with dates and we wouldn't want  
duplicates to show up in the results, so your second suggestion  
looks like a good workaround if I can't solve the actual problem.  I  
didn't know about FieldCollapsing, so I'll definitely keep it in mind.


Thanks
Mark

On 22 Jun 2010, at 3:44 pm, Geert-Jan Brits wrote:

Perhaps my answer is useless, bc I don't have an answer to your  
direct

question, but:
You *might* want to consider if your concept of a solr-document is  
on the

correct granular level, i.e:

your problem posted could be tackled (afaik) by defining a   
document being a

'sub-event' with only 1 daterange.
So for each event-doc you have now, this is replaced by several sub- 
event

docs in this proposed situation.

Additionally each sub-event doc gets an additional field 'parent- 
eventid'
which maps to something like an event-id (which you're probably  
using) .

So several sub-event docs can point to the same event-id.

Lastly, all sub-event docs belonging to a particular event  
implement all the

other fields that you may have stored in that particular event-doc.

Now you can query for events based on data-rages like you  
envisioned, but
instead of returning events you return sub-event-docs. However  
since all
data of the original event (except the multiple dateranges) is  
available in
the subevent-doc this shouldn't really bother the client. If you  
need to
display all dates of an event (the only info missing from the  
returned
solr-doc) you could easily store it in a RDB and fetch it using the  
defined

parent-eventid.

The only caveat I see, is that possibly multiple sub-events with  
the same

'parent-eventid' might get returned for a particular query.
This however depends on the type of queries you envision. i.e:
1)  If you always issue queries with date-filters, and *assuming*  
that
sub-events of a particular event don't temporally overlap, you will  
never

get multiple sub-events returned.
2)  if 1)  doesn't hold and assuming you *do* mind multiple sub- 
events of

the same actual event, you could try to use Field Collapsing on
'parent-eventid' to only return the first sub-event per parent- 
eventid that
matches the rest of your query. (Note however, that Field  
Collapsing is a

patch at the moment. http://wiki.apache.org/solr/FieldCollapsing)

Not sure if this helped you at all, but at the very least it was a  
nice

conceptual exercise ;-)

Cheers,
Geert-Jan


2010/6/22 Mark Allan 


Hi all,

Firstly, I apologise for the length of this email but I need to  
describe

properly what I'm doing before I get to the problem!

I'm working on a project just now which requires the ability to  
store and
search on temporal coverage data - ie. a field which specifies a  
date range

during which a certain event took place.

I hunted around for a few days and couldn't find anything which  
seemed to
fit, so I had a go at writing my own field type based on  
solr.PointType.

It's used as follows:
schema.xml
 
 stored="true"

multiValued="true"/>
data.xml
 
 
 ...
 1940,1945
 
 

Internally, this gets stored as:
 1940,1945
 1940
 1945

In due course, I'

Re: remove from list

2010-06-23 Thread Susan Rust 

Will do -- but wasn't selling -- trying to donate!

Susan Rust
VP of Client Services

If you wish to travel quickly, go alone
If you wish to travel far, go together

Achieve Internet
1767 Grand Avenue, Suite 2
San Diego, CA 92109

800-618-8777 x106
858-453-5760 x106

Susan-Rust (skype)
@Susan_Rust (twitter)
@Achieveinternet (twitter)
@drupalsandiego (San Diego Drupal Users' Group Twitter)



This message contains confidential information and is intended only  
for the individual named. If you are not the named addressee you  
should not disseminate, distribute or copy this e-mail. Please notify  
the sender immediately by e-mail if you have received this e-mail by  
mistake and delete this e-mail from your system. E-mail transmission  
cannot be guaranteed to be secure or error-free as information could  
be intercepted, corrupted, lost, destroyed, arrive late or incomplete,  
or contain viruses. The sender therefore does not accept liability for  
any errors or omissions in the contents of this message, which arise  
as a result of e-mail transmission. If verification is required please  
request a hard-copy version.














On Jun 23, 2010, at 9:30 AM, Markus Jelsma wrote:

If you want to unsubscribe, then you can do so [1] without trying to  
sell something ;)




[1]: http://lucene.apache.org/solr/mailing_lists.html



Cheers!

-Original message-----
From: Susan Rust 
Sent: Wed 23-06-2010 18:23
To: solr-user@lucene.apache.org; Erik Hatcher  
;

Subject: remove from list

Hey SOLR folks -- There's too much info for me to digest, so please
remove me from the email threads.

However, if we can build you a forum, bulletin board or other web-
based tool, please let us know. For that matter, we would be happy to
build you a new website.

Bill O'Connor is our CTO and the Drupal.org SOLR Redesign Lead. So we
love SOLR! Let us know how we can support your efforts.

Susan Rust
VP of Client Services

If you wish to travel quickly, go alone
If you wish to travel far, go together

Achieve Internet
1767 Grand Avenue, Suite 2
San Diego, CA 92109

800-618-8777 x106
858-453-5760 x106

Susan-Rust (skype)
@Susan_Rust (twitter)
@Achieveinternet (twitter)
@drupalsandiego (San Diego Drupal Users' Group Twitter)



This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please notify
the sender immediately by e-mail if you have received this e-mail by
mistake and delete this e-mail from your system. E-mail transmission
cannot be guaranteed to be secure or error-free as information could
be intercepted, corrupted, lost, destroyed, arrive late or incomplete,
or contain viruses. The sender therefore does not accept liability for
any errors or omissions in the contents of this message, which arise
as a result of e-mail transmission. If verification is required please
request a hard-copy version.













On Jun 23, 2010, at 1:52 AM, Mark Allan wrote:


Cheers, Geert-Jan, that's very helpful.

We won't always be searching with dates and we wouldn't want
duplicates to show up in the results, so your second suggestion
looks like a good workaround if I can't solve the actual problem.  I
didn't know about FieldCollapsing, so I'll definitely keep it in  
mind.


Thanks
Mark

On 22 Jun 2010, at 3:44 pm, Geert-Jan Brits wrote:


Perhaps my answer is useless, bc I don't have an answer to your
direct
question, but:
You *might* want to consider if your concept of a solr-document is
on the
correct granular level, i.e:

your problem posted could be tackled (afaik) by defining a
document being a
'sub-event' with only 1 daterange.
So for each event-doc you have now, this is replaced by several sub-
event
docs in this proposed situation.

Additionally each sub-event doc gets an additional field 'parent-
eventid'
which maps to something like an event-id (which you're probably
using) .
So several sub-event docs can point to the same event-id.

Lastly, all sub-event docs belonging to a particular event
implement all the
other fields that you may have stored in that particular event-doc.

Now you can query for events based on data-rages like you
envisioned, but
instead of returning events you return sub-event-docs. However
since all
data of the original event (except the multiple dateranges) is
available in
the subevent-doc this shouldn't really bother the client. If you
need to
display all dates of an event (the only info missing from the
returned
solr-doc) you could easily store it in a RDB and fetch it using the
defined
parent-eventid.

The only caveat I see, is that possibly multiple sub-events with
the same
'parent-eventid' might get returned for a particular query.
This however depends on the type of q