wish list: Improving search feature

Author Message

Georg Franz

Thursday 04 December 2003 5:57:22 am

Hi,

I've some suggestions to improve the search-feature:

-) Search by "First letters"
e.g. I've 15.000 users and want to show all users whose lastname or login starts with an "A" or "An" etc. in a template. (Extended: find users whose lastname starts with "Aa" or "Ab" or "Ac" etc.)

-) Sort order by section-id of the result (e.g. if more than one site is installed I can sort the search result by the section id and output in the template someting like: Search result for Site 1 / Site 2 and so on)

-) Search priority: If you use the datatype ezkeyword in a content class and a keyword is found in that attribute, the result should get a higher ranking.

-) Search priority, 2nd: If a keyword is found in the name of an object, it should get a higher ranking.

The high-end feature: Extend the content-class, each added datatype can get an user defined "search ranking".
Example:
content class "small article":
field "title" - search ranking 5
field "keywords" - search ranking 4
field "intro" - search ranking 3
field "body" - search ranking 1

(Higher numbers - higher rankings)

-) Search in more than one content class at once (inlcude/exclude content class ids as in the fetch"-function). (e.g. I've 4 different article-classes and I want to do one search in all of the 4 article-classes)

-) Small search result: e.g. in some cases you need only the object ids or the main node ids or data_map and not the filled objects (with children, subtree and so on) - could prevent "overload".

Kind regards,
Emil.

Best wishes,
Georg.

--
http://www.schicksal.com Horoskop website which uses eZ Publish since 2004

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 15:09:05
Script start
Timing: Jan 18 2025 15:09:05
Module start 'layout'
Timing: Jan 18 2025 15:09:05
Module start 'content'
Timing: Jan 18 2025 15:09:05
Module end 'content'
Timing: Jan 18 2025 15:09:05
Script end

Main resources:

Total runtime0.0152 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0066 587.9375152.6250
Module start 'layout' 0.00660.0025 740.562539.4453
Module start 'content' 0.00900.0042 780.007889.3359
Module end 'content' 0.01330.0019 869.343830.3047
Script end 0.0151  899.6484 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002617.0538140.0002
Check MTime0.00117.0786140.0001
Mysql Total
Database connection0.001610.757810.0016
Mysqli_queries0.002214.581630.0007
Looping result0.00000.072310.0000
Template Total0.001610.310.0016
Template load0.00085.563610.0008
Template processing0.00074.686610.0007
Override
Cache load0.00064.125510.0006
General
dbfile0.00021.384680.0000
String conversion0.00000.051940.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs