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  July 2006

ZNG July 2006

Subject:

Re: CQL Bilbiographic Searching Proposal

From:

"Scherle, Ryan E" <[log in to unmask]>

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Fri, 7 Jul 2006 12:21:39 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (47 lines)

 
(finally catching up on this...)

A while back, Rob Sanderson and Ray Denenberg had a conversation (see
below) about keyword searching and the usefulness of the proposed
excludeOriginInfo modifier on the cql.anywhere index. 

In my opinion, the server should be the one making the decision on which
fields/indexes are inluded in a keyword search. The developer creating
the server has knowledge of the data being searched, and which portions
of the data are useful for keyword searching. In every collection I've
dealt with, we have had a meeting go through the available fields and
determine which were useful as keywords. Sometimes, this inludes
originInfo, but often it does not. I wouldn't want the people posing
queries to make this decision, because they do not have enough knowledge
of the structure of the data. 

If cql.anywhere truly means "any field in the data", including fields
that wouldn't normally be searchable (like originInfo and notes), it is
guaranteed to produce a lot of noise. However, the current CQL context
set says it means "search all indexes", which I take to mean "search all
information that would normally be searchable", roughly equivalent with
a keyword search where keywords are defined by the server.

The bottom line, then is that if we define cql.anywhere properly, we
don't need the excludeOriginInfo modifier.

----- Ryan Scherle
----- Digital Library Program
----- Indiana University


----------- Quoted conversation -------------

Rob: I don't see the need for excludeOriginInfo, and would suggest 
removing it unless someone can speak as to its utility.

Ray: The idea is that there may be several different types of keywords
defined. One such keyword would be defined as "anywhere in the 
record with the exception of OriginInfo" and someone else could define a
keyword to
exclude some other area of the record.  originInfo is the only one
suggested 
so far. The suggester posed this requirement, that excluding originInfo
dramatically improves precision of the search because so much 
irrelevant junk is contained there.

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