Difference between revisions of "SoC improved search"
(→Initial Ideas) |
(→Incentive) |
||
| Line 2: | Line 2: | ||
== Incentive == | == Incentive == | ||
| + | Many Geeklog sites have a lot of content spread across multiple plugins. Content can have different access rights so that needs to be respected when content search is made. | ||
| − | + | There is a need to better display the search results and improve the search speed and ability for the user to refine their search and filter/sort the displayed search results. | |
| − | |||
== Initial Ideas == | == Initial Ideas == | ||
Revision as of 20:20, 2 March 2008
Incentive
Many Geeklog sites have a lot of content spread across multiple plugins. Content can have different access rights so that needs to be respected when content search is made.
There is a need to better display the search results and improve the search speed and ability for the user to refine their search and filter/sort the displayed search results.
Initial Ideas
- Tags, Tag Cloud
- AJAX powered
- Better Formatting or layout options
- Sub Filtering of results
- Search within results
- Listing to have sortable headings and able to change view to see results for all or selected plugins
- User able to change the number of records per page and set preference
- Improved API
- Option on content to be excluded from search. So some public staticpages are not to be returned in searches.
Level of Difficulty
medium to high
This project will require someone to spend time understanding out the existing Search feature works, how plugins tie into the search, how the search class works.
Students will need to have experience to suggest how the ideas above would best be implemented and should likley do a proof of concept. Exploring how other tools provide search servics is a good approach to develop ideas.
Experience with User Interface design will benefit so that search implementation improvements can be made.
