Message from discussion
Modifying 'Modify Search'
Received: by 10.180.105.2 with SMTP id gi2mr845655wib.4.1346952751187;
Thu, 06 Sep 2012 10:32:31 -0700 (PDT)
X-BeenThere: xtf-user@googlegroups.com
Received: by 10.180.82.231 with SMTP id l7ls1857814wiy.4.canary; Thu, 06 Sep
2012 10:32:30 -0700 (PDT)
Received: by 10.180.24.202 with SMTP id w10mr5109038wif.0.1346952750527;
Thu, 06 Sep 2012 10:32:30 -0700 (PDT)
Received: by 10.180.24.202 with SMTP id w10mr5109037wif.0.1346952750515;
Thu, 06 Sep 2012 10:32:30 -0700 (PDT)
Return-Path: <bdysonsm...@gmail.com>
Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181])
by gmr-mx.google.com with ESMTPS id bb7si693296wib.2.2012.09.06.10.32.30
(version=TLSv1/SSLv3 cipher=OTHER);
Thu, 06 Sep 2012 10:32:30 -0700 (PDT)
Received-SPF: pass (google.com: domain of bdysonsm...@gmail.com designates 209.85.212.181 as permitted sender) client-ip=209.85.212.181;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of bdysonsm...@gmail.com designates 209.85.212.181 as permitted sender) smtp.mail=bdysonsm...@gmail.com; dkim=pass header...@gmail.com
Received: by wibhm2 with SMTP id hm2so1690306wib.16
for <xtf-user@googlegroups.com>; Thu, 06 Sep 2012 10:32:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
bh=c0ogGWZyWW5YObvtjkAzLjDtahyVwy/blASkDGmPyJw=;
b=RpPoPEn9MYQ6QTJx5eHKwSVqSKlbjbHzgG5cWM+1zxapEanpBYeTHE9lJmalTSuq+F
LeYCspqxUmLHe2ZDWMCDROom+Q2RyFpyCrsYh2GRr8BFIA5fur2P1TL3T6KBekw5+Q2I
ybRrVn1tRYJi5YfWupNbGaSGGUAdLBRKDHF3PJ0T4mAuIXFG5wzxCHNKHIZcTaRXsmrM
IPspp53r7xOJhQTHtD0gEBrmGs5Wk6j+h4Kz9wE0SlC/oi9+2b8eyy4BQA96cRnbzTaC
tlk0j7bo3oet4JNZ7C4u6G5MDO9flX8/8JbcIMtYyWaTV7/fzP1M5BYMqxonsSg4aqWZ
URUA==
MIME-Version: 1.0
Received: by 10.216.212.228 with SMTP id y78mr1547638weo.43.1346952733266;
Thu, 06 Sep 2012 10:32:13 -0700 (PDT)
Received: by 10.227.98.27 with HTTP; Thu, 6 Sep 2012 10:32:13 -0700 (PDT)
In-Reply-To: <CAD-FYmTraxj_wzuScx_5cXADmCkRRwyCELDaqb9oGe+Nod7...@mail.gmail.com>
References: <CAD-FYmTraxj_wzuScx_5cXADmCkRRwyCELDaqb9oGe+Nod7...@mail.gmail.com>
Date: Thu, 6 Sep 2012 13:32:13 -0400
Message-ID: <CAD-FYmTVU5R0S79+GAu+Kr+0QCNA_mJxDJkc3kKuPwGSb72...@mail.gmail.com>
Subject: Re: Modifying 'Modify Search'
From: Bridger Dyson-Smith <bdysonsm...@gmail.com>
To: XTF Users List <xtf-user@googlegroups.com>
Content-Type: multipart/alternative; boundary=0016e6d96c363212fb04c90bdf86
--0016e6d96c363212fb04c90bdf86
Content-Type: text/plain; charset=ISO-8859-1
Thrashing around in stylesheets will occasionally yield results for me --
not this time. It looks like format-query.xsl *isn't* the place to do this
sort of string modification. I'm tinkering in style/xtfCommon/xtfCommon.xsl
now, but I'm still not quite sure about this.
Thanks again!
Cheers,
Bridger
On Thu, Aug 30, 2012 at 10:57 AM, Bridger Dyson-Smith <bdysonsm...@gmail.com
> wrote:
> Hi all --
>
> I've been wondering about modifying the URL string that is passed back to
> the Search page from the Modify Search link. My goal is to allow users to
> Browse > select a facet > then Modify Search to perform keyword searching
> on the selected facet [1].
>
> Currently the values passed back to the Search Page are something like:
> localhost:8080/xtf/search?f1-subject=Subject;smode=simple-modify
>
> I'm thinking that adding a bit of replace() to the right spot should
> change that f1-subject to subject and return keywords + facet. It's the
> right spot that's causing some problems for me.
>
> format-query.xsl (style/crossQuery/resultFormatter/common/) *seems* like
> it might be right, but I'm not sure.
> Any suggestions would be most appreciated! Is this a ridiculous idea?
>
> Thanks!
> Bridger
>
> [1] The driving idea behind this is being able to deliver multiple
> collections in XTF, and allow users to constrain searches to specific
> collections. It looks like Advanced and/or Freeform search might offer
> this, but I was hoping to make it more transparent.
>
>
>
>
>
--0016e6d96c363212fb04c90bdf86
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Thrashing around in stylesheets will occasionally yield results for me -- n=
ot this time. It looks like format-query.xsl *isn't* the place to do th=
is sort of string modification. I'm tinkering in style/xtfCommon/xtfCom=
mon.xsl now, but I'm still not quite sure about this.<br>
<br>Thanks again!<br>Cheers,<br>Bridger<br><br><div class=3D"gmail_quote">O=
n Thu, Aug 30, 2012 at 10:57 AM, Bridger Dyson-Smith <span dir=3D"ltr"><=
<a href=3D"mailto:bdysonsm...@gmail.com" target=3D"_blank">bdysonsmith@gmai=
l.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi all --=A0<div><br></div><div>I've bee=
n wondering about modifying the URL string that is passed back to the Searc=
h page from the Modify Search link. My goal is to allow users to Browse >=
; select a facet > then Modify Search to perform keyword searching on th=
e selected facet [1].=A0</div>
<div><br></div><div>Currently the values passed back to the Search Page are=
something like:</div><div>localhost:8080/xtf/search?f1-subject=3DSubject;s=
mode=3Dsimple-modify</div><div><br></div><div>I'm thinking that adding =
a bit of replace() to the right spot should change that f1-subject to subje=
ct and return keywords + facet. It's the right spot that's causing =
some problems for me.</div>
<div><br></div><div>format-query.xsl (style/crossQuery/resultFormatter/comm=
on/) *seems* like it might be right, but I'm not sure.</div><div>Any su=
ggestions would be most appreciated! Is this a ridiculous idea?=A0</div>
<div>
<br></div><div>Thanks!</div><div>Bridger</div><div><br></div><div>[1] The d=
riving idea behind this is being able to deliver multiple collections in XT=
F, and allow users to constrain searches to specific collections. It looks =
like Advanced and/or Freeform search might offer this, but I was hoping to =
make it more transparent.=A0</div>
<div><br></div><div><br></div><div><br></div><div><br></div>
</blockquote></div><br>
--0016e6d96c363212fb04c90bdf86--