LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


ZNG@C4VLPLISTSERV01.LOC.GOV


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  June 2005

ZNG June 2005

Subject:

Betr.: Multiple Sources in SRU/W

From:

Theo van Veen <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Fri, 10 Jun 2005 22:58:39 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (73 lines)

Even when one single database is connected to, it is desirable to
specify a subset of that database as target. We use "x-collection" as
parameter to specify a single target. I would suggest a comma-separated
list of collections as value for x-collection in case there are more
collections. It is also possible to have virtual collections which can
be a predefined list of collections but will appear as one name for
x-collection. One could add an extension to the service that allows a
client to define a set of databases as a single virtual database which
can be used as a surrogate for the list of targets.
We have done an experiment with accessing a MSE via SRU. It is not only
a matter of specifying the metasearch targets but also how to return the
results. In the experiment we did we defined a "operation=metaSearch"
with a normal SRU query but with a response consisting of a list of
target ids with the number of hits for each speciifc target. To obtain
the actual results for a specific target the target id is used as value
for the x-collection parameter and the query is retransmitted.

Theo


>>> [log in to unmask] 06/10 5:28  >>>
Hi All,

This is a SRU/W for MetaSearch Engines (MSEs) question. It occurred
during
internal discussions in MuseGlobal and then again at the ELAG meeting
last
week.

As far as I can tell from the documentation and from searching this
thread
there is no preferred/recommended/allowed method of asking a server to
search more than one target database. Obviously with "real" SEs this is
not
a problem as they only have one database (well, the vast majority of
them),
but for SRU/W to be used to connect TO an MSE it is obviously a bit of
a
problem. From the MSE to the SEs is no problem.

In the message from the client to the MSE we're, obviously, not
talking
about real database, but what we call Sources which are a particular
database (or other Data Service) at a particular Host. However they
have IDs
just like any internal database for an SE, so the semantics of the
"database
name" is not a problem, only the number of them allowed in the SRU
string.

We have a couple of methods in mind, (just stringing the IDs together
as one
long 'database name' string is one way which would be sort of legal,
but not
very elegant) but they would be 'non-standard'. It's a problem which
would
be much better addressed now rather than later.

Ideas? suggestions? modifications to standards?

Peter

Dr Peter Noerr
Chief Technical Officer
Museglobal, Inc.

tel: +1 801 208 1880
fax: +1 801 208 1889
cell:+1 801 910 4912

[log in to unmask]
www.museglobal.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