1/ AFAIR Lucene can also index attached files and return multiple type of search results (wiki page, attached file, etc). You should take this into account for the results display, and also find an approach to illustrate location in this context (see 2/ ).
2/ for the Location I noticed you put wiki > Parent > Parent > ... > Page? Or is it just the spaces list? I think the breadcrumbs now are using parent pages for the full "path" and we should decide if Location == breadcrumb or is the actual location of the page as in wiki > Space > Page. Also, maybe the wiki name could be differentiated so that we know it's a wiki name and not only a lowercase space name, but we could also keep it like this for simplicity reasons.
1) The result items are scalable - you can add more info to it - like the query is in the attached file, what translations, version the page has, etc. The thing is not to overload the user - but the amount of details could be preselected from settings;
2) we will keep it for simplicity issue. The wiki is always in front (if multiple wikis), else space name > space name > ... (if multiple spaces will be implemented) and last the page name.
I agree on keeping location as "wiki > space > page" rather than the full breadcrumb path
Could you add a proposal for a drop-down menu with autosuggest of page titles when typing in the search field (as on Google -> it would behave as the intranet's quick find panel)
When a page has ratings -> where would you display that page's rating? The rating is different from the Lucene score, it's a rating like youtube's one ("do people like this page or not")
If we use compass, we may be able to extract the sentence in which a given word is located -> where would the sentence be displayed in a results item? Between the page title and the location line?
Hi Cati,
I think solution II would be too complex for users. Google-like search results as in Solution I seem like a better idea to me.
Hi Cati, it would be cool if you could provide higher resolution images / inkscape files in attachments for a better viewing experience ;-)
First 2 quick thoughts:
1/ AFAIR Lucene can also index attached files and return multiple type of search results (wiki page, attached file, etc). You should take this into account for the results display, and also find an approach to illustrate location in this context (see 2/ ).
2/ for the Location I noticed you put wiki > Parent > Parent > ... > Page? Or is it just the spaces list? I think the breadcrumbs now are using parent pages for the full "path" and we should decide if Location == breadcrumb or is the actual location of the page as in wiki > Space > Page. Also, maybe the wiki name could be differentiated so that we know it's a wiki name and not only a lowercase space name, but we could also keep it like this for simplicity reasons.
1) The result items are scalable - you can add more info to it - like the query is in the attached file, what translations, version the page has, etc. The thing is not to overload the user - but the amount of details could be preselected from settings;
2) we will keep it for simplicity issue. The wiki is always in front (if multiple wikis), else space name > space name > ... (if multiple spaces will be implemented) and last the page name.
Thanks for feedback.
Here are some additional remarks: