Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 13360 invoked from network); 6 Dec 2009 16:04:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Dec 2009 16:04:52 -0000 Received: (qmail 75359 invoked by uid 500); 6 Dec 2009 16:04:51 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 75256 invoked by uid 500); 6 Dec 2009 16:04:50 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 75246 invoked by uid 99); 6 Dec 2009 16:04:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Dec 2009 16:04:50 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dionne@dionne-associates.com designates 67.222.53.251 as permitted sender) Received: from [67.222.53.251] (HELO outbound-mail-305.bluehost.com) (67.222.53.251) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 06 Dec 2009 16:04:47 +0000 Received: (qmail 11946 invoked by uid 0); 6 Dec 2009 16:04:27 -0000 Received: from unknown (HELO host183.hostmonster.com) (74.220.207.183) by outboundproxy6.bluehost.com with SMTP; 6 Dec 2009 16:04:27 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=dionne-associates.com; h=Received:From:Content-Type:Content-Transfer-Encoding:Subject:Date:Message-Id:To:Mime-Version:X-Mailer:X-Identified-User; b=BB3bAqKK+mxkkjJj2/w8/k5mRYVlUMyvqlXnIEag0fuaWwI5FewhwBrS5QQWBnbOS4RE/dxkZV+tXvudlI8zZV+ISCFK2ffPaNinOfjuXXBsuOVQ5Ty0ShpwQLrcx+be; Received: from adsl-99-37-17-196.dsl.wlfrct.sbcglobal.net ([99.37.17.196] helo=[192.168.1.100]) by host183.hostmonster.com with esmtpa (Exim 4.69) (envelope-from ) id 1NHJb0-0002Lb-LZ for dev@couchdb.apache.org; Sun, 06 Dec 2009 09:04:26 -0700 From: Robert Dionne Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: rendering docs in Futon Date: Sun, 6 Dec 2009 11:04:25 -0500 Message-Id: <00BE18F1-B2B0-4130-B187-E488E38A58A6@dionne-associates.com> To: dev@couchdb.apache.org Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) X-Identified-User: {2551:host183.hostmonster.com:dionneas:dionne-associates.com} {sentby:smtp auth 99.37.17.196 authed with dionne@dionne-associates.com} I have what I guess is a design question about Futon: I've been playing and prototyping with FTI in couchdb [1,2] and have = tweaked Futon to replace the "Jump to ID" feature with "Search For:" [3] = and an interesting question comes up. Currently I"m indexing all the = values in the docs and returning the slot names as well as the doc ids = in the search results. Even though couchdb is schema-less, there is an = implicit schema within a given database as a rule. This is what allows = us to define a Document object in Lucene which contains the fields we = want to index up front. In this approach I'm indexing everything but of course in practice I = may only be interested in particular slots like "PreferredName" or = "GeneEncodes". So the question I have is how to control that in the = search field, because it is database dependent. Should I let the display = slot in jquery.suggest be configurable? I suppose one approach would be = to index views rather that the entire document. This would be closer to = how Lucene indexing works where the view itself defines the fields of = interest. Still there may be multiple fields, so the question of how to = configure the display remains. Anyway if this makes sense to anyone I'd appreciate your thoughts. Cheers, Bob [1] http://github.com/bdionne/indexer [2] http://github.com/bdionne/couchdb/tree/lucille [3] http://dionne.posterous.com/searching-in-futon-0