OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

search-ws message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [search-ws] Scan: another approach


But my point is this.  You can say I want "cat" to be the fifth term, and I
want 10 terms.  Or you can say I want 10 terms beginning with -3 (always
assuming that the seed term is in position 1).

 The latter approach is in line with the searchRetrieve operation. So why
not do it that way. Is it because:
- we want to keep the scan definition the way it is?
- we don't want to extend the start position parameter to allow negative
numbers?
- Other?

--Ray

----- Original Message ----- 
From: "Matthew J. Dovey" <m.dovey@jisc.ac.uk>
To: "LeVan,Ralph" <levan@oclc.org>; "Ray Denenberg, Library of Congress"
<rden@loc.gov>; <search-ws@lists.oasis-open.org>
Sent: Monday, November 19, 2007 3:05 PM
Subject: RE: [search-ws] Scan: another approach


p.s.

what we could do is allow both start and position as positional parameters,
so you could do a search indicating where in the result set you wanted the
most relevant term.

Of course using both start and position in the same request would (probably)
result in an error diag being returned.

Matthew

> -----Original Message-----
> From: LeVan,Ralph [mailto:levan@oclc.org]
> Sent: 19 November 2007 18:22
> To: Matthew J. Dovey; Ray Denenberg, Library of Congress; search-
> ws@lists.oasis-open.org
> Subject: RE: [search-ws] Scan: another approach
>
> Sorry, but startRecord and position are not the same thing.  They look
> the same when you keep using the value 1, but when do a scan asking for
> ten terms with my term in the 5th position, it's very different.
>
> The na´ve user, when seeing a request with start=5, max=10 will expect
> something completely different from what I expect when I say
> position=5, numTerms=10.
>
> Please stop trying to combine the two services.
>
> Ralph
>
> -----Original Message-----
> From: Matthew J. Dovey [mailto:m.dovey@jisc.ac.uk]
> Sent: Saturday, November 17, 2007 12:00 PM
> To: Ray Denenberg, Library of Congress; search-ws@lists.oasis-open.org
> Subject: RE: [search-ws] Scan: another approach
>
> Mmmm, interesting - it also got me thinking. Essentially the
> information
> we send on the request falls into three categories:
>
> The query
> Some positional information (startRecord, MaxRecords)
> Some response formatting instructions (recordFormat, sort)
>
> Can everything we send in a request be categorised as above?
>
> If so, we could simplify our request into three parameters each
> accepting a value which is in someway extensible.
>
> So our requests may look something like:
>
> http://myserver.com/sru?query=sru.CQL:dc.author=smith&positional=[sru.s
> t
> artRecord:1;sru.maximumRecords:10;myextension.stepping:2]&formatting=[s
> r
> u.recordFormat=MODS;sru.sort=dc.author]
>
> http://myserver.com/sru/query=sru.SCAN:dc.author%20any%20smith&position
> a
> l=[sru.startRecord:1;sru.maximumRecords:10]
>
> Any comments?
>
> Matthew
>
>
> > -----Original Message-----
> > From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov]
> > Sent: 16 November 2007 20:29
> > To: search-ws@lists.oasis-open.org
> > Subject: [search-ws] Scan: another approach
> >
> > Let's start over (indulge me).
> >
> > The cannonical scan example is:
> >
> >
> http://myserver.com/sru?operation=scan&version=1.2&scanClause=dc.title
> > =
> > frog           &responsePosition=1&maximumTerms=25
> >
> > Take away operation and version (which we're going to discard,
> > hopefully)
> > and you get:
> >
> >  http://myserver.com/sru?scanClause=dc.title =
> > frog&responsePosition=1&maximumTerms=25
> >
> > Now, we've talked about introducing multiple query types, which seems
> > to be
> > a well-received suggestion,  and scan as one of them, perhaps not
> quite
> > as
> > well recieved, but let's try the idea out anyway.
> >
> > -  Suppose we call scanClause a query type (we can come up with a
> > better
> > name later).
> > -  Change responsePosition to startRecord in the above.
> > - Change maximumTerms to maximumRecords in the above.
> >
> > You get:
> >
> >  http://myserver.com/sru?scanClause=dc.title =
> > frog&startRecord=1&maximumRecords=25
> >
> > Then you essentially have a searchRetrieve request.  For this query
> > type,
> > the rule is that all records are returned via the termFormat syntax.
> >
> >  The multiple operation and multiple database issues go away.
> >
> > Anything wrong with this approach.?
> >
> > --Ray
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this mail list, you must leave the OASIS TC that
> > generates this mail.  You may a link to this group and all your TCs
> in
> > OASIS
> > at:
> > https://www.oasis-
> open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]