LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  January 2005

ZNG January 2005

Subject:

Re: Adlib Base profile

From:

Hedzer Westra <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Mon, 3 Jan 2005 11:07:49 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (53 lines)

Hi Rob (& others),

[CQL prox vs. Adlib When boolean]
> > I'll add adlib.when and adlib.whennot modifiers to the 'and'
boolean, that's a better solution I guess.
> It's certainly better than incorrectly implementing prox, yes. 
> However what would be best is if we could decide how best to make CQL
provide a sensible mapping for 
> your operator.
Adding two new boolean operators would also do the trick, but since the
CQL booleans are not extensible, as opposed to relation and modifiers, I
chose that path (after getting stuck on the prox modifier). If you want
to add something to CQL, be my guest. But I do have to finish my code,
so I'm afraid I don't want to wait for that..

> >> So adlib.allIndexes will search all indexes in the adlib
context-set, yes?
> > Yep, the adlib context set being all indexes defined for the
configured database.
> Errr, no. To clarify: The adlib context-set contains only the bits
that you would 
> prefix with 'adlib.' in the CQL. So for example, adlib.allIndexes
would NOT search dc.title or 
> net.host, but would search adlib.foo and adlib.bar
Ah. But how do I define it then, in a way that doesn't 'trample' CQL ?
And another question: it's possible (and allowed) to map an index to
more than one context set, right? Then why won't you allow me to define
the adlib context set as: all indexes the exported database knows
(natively)? Seems valid CQL to me..

If I may say so: CQL defines a lot of (fortunately optional) pretty
esoteric stuff like word proximity searches and the prox operator, and
is prepared for implementation dependent things like relation modifiers.
All of this leads me to the conclusion that CQL is supposed to be
pluggable for any kind of search language, with it's own quirks. But
what happens when I file a profile in which I neatly define all these
quirks? Big discussions & lots of trouble (for me) to get our 'expert
search' lined up with CQL. Is it just me being cranky on my first
working day of 2005 (Happy new year BTW!), or isn't CQL as flexible as
it looks?

Best regards,

Hedzer Westra, Systems Developer

Adlib | Information Systems
Reactorweg 291
3542 AD Utrecht
Postbus 1436
3600 BK Maarssen
tel: +31-30-241 1885
www: http://www.adlibsoft.com

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager