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  September 2002

ZNG September 2002

Subject:

Re: Need Feedback on Re: DC Index definitions

From:

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Mon, 23 Sep 2002 12:01:34 +1000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (47 lines)

On Fri, Sep 20, 2002 at 07:33:01AM -0400, LeVan,Ralph wrote:
> Okay, let's start all over.
>
> When I extract keywords from records to build indexes, I do it two ways.  I
> either take the entire contents of a field and use that as an index term, or
> I take the individual words from the field, remember their relative
> positions and use them as index terms.  I have always called the first type
> of indexing "phrase" indexes and the second kind of indexing "word" indexes.

We support both of the above of course, but we also support another slight
variation - which is for you 'phrase' index to normalize the text based
on knowledge that it is a series of words. For example, we might strip
all the punctuation, map to upper case, compress multiple spaces, trim
leading and trailing spaces.

This index allows very efficient 'first word in field' type operators.
Its faster than just using word positions for queries where you have
several words at the front in the query. We also have done things
occasionally like remove leading 'A' and 'THE' etc.

My point is there is a bit of risk assuming everyone is going to implement
things the same way. Z39.50 has this abstraction layer allowing
implementations to do what they want, as long as the semantics are
the same.

Oh, and what you call phrase/string above I think the Bath profile calls
'complete field'. That is, they effectively recommend the 'completeness'
attribute type to distinguish between the cases. (Actually, they
don't define this level of semanitcs - they just say "this combination
means this, that combinations means that" - they don't try and justify
semantics to individual attribute types & values, they only define
semantics to complete combinations. My analysis of the attribute
lists was that completness was the best way, according to Bath, to
distinguish between word indexing and indexing the whole value.


Having typed up all of the above, I am not sure of my point exactly.
Probably more of a clarification. Or maybe pointing out that for what you
call phrase/string, Bath (as I understand it) recommends using completeness.
If nothing else, it highlights the confusion. I think SRW should stand
on its own two feet rather than using Z39.50/Bib-1 terminology.

I agree with your two types of indexes though (but point out that there
are other variations possible).

Alan

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