solprovider apache.org schrieb:
> On 3/24/08, Andreas Hartmann <andreasapache.org> wrote:
[...]
>> > All text should be included, or do we have
field-level security?
>> No, we only have document-level security.
>
> The question was to provoke thought about future
enhancements. (I
> have not planned to include field-level security in
Lenya-1.3.0, but
> my planning includes not adding obstacles for
recognized possible
> improvements.) Security requires three functions:
> 1. Hide unauthorized information, handled by the
display system.
> 2. Hide unauthorized pages from menus, handled by the
navigation system.
> 3. Prevent search from using unauthorized information.
This must be
> handled by the search system (our current topic.) The
most difficult
> aspect of developing field-level (or any) security is
preventing
> search from creating security holes so mentioning
possible
> enhancements seemed useful to this discussion.
Thanks for bringing this up, it's certainly reasonable to
keep an eye on
this aspect.
>> > Should all properties be included? Should
the properties be
>> > associated with the field (element) name?
>> ATM this is up to the resource type (done using a
>> 2index.xsl stylesheet), and IMO we
can leave it like this,
>> e.g. map
>> <person>
>> <name>Henry Hamster</name>
>> </person>
>> to field
>> <lucene:document>
>> <lucene:field
name="personName">Henry
Hamster</lucene:field>
>> </lucene:document>
>>
>> It would be nice to have namespaced field names,
though, to avoid
>> clashes (see my other mail).
>> -- Andreas
>
> No special work is needed since search indexes all text
and "Henry
> Hamster" is text.
> Search indexing issues arise when the data is stored:
> <author name="Gabby Gerbil"/>
> rather than:
> <author>Gabby Gerbil</author>
With the current implementation, this is not an issue since
the Lucene
document is generated using a resource-type specific XSLT:
<xsl:template match="author">
<lucene:field name="author">
<xsl:value-of select="name"/>
</lucene:field>
</xsl:template>
> Or are you concerned with searches based on particular
fields, such as
> searching by author? Many search systems have stopped
providing those
> options from apparent lack of use; people dislike
organizing search
> terms into multiple fields.
Yes, this is what I had in mind. Last week at the OpenExpo I
was asked
if Lenya supports this feature. From the site visitor's
point of view it
is probably not necessary, but I could imagine field search
to be useful
in the authoring environment. Imagine, e.g., searching for
- documents by a particular author
- images with a particular width/height
- images belonging to a particular category or having
particular tags
BTW, JCR with its SQL queries would be great in this aspect,
since you
could even search for images with, e.g., width > 1000.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org
|