Search: search...
Last modified by Thomas Mortagne on 2015/02/13 15:29
Refine your search
Select a category and activate filters on the current results
Creator
-
superadmin
790 -
Thomas Mortagne
615 -
XWikiGuest
521 -
Admin
460 -
Admin
209 - … 95 more
Last modification date
-
Older than 30 days
1477
Creation date
-
Older than 30 days
3246
Object type
-
Rights
1204
-
Users
1171
-
User Dashboard Preferences
1163
-
Tag
732
-
Feed Entry
508
- … 31 more
File type
Upload date
Search Improvements
Located in
- Title
Search Improvements
- Page
Search
- Raw document content
{{warning}}Moved to [[design.xwiki.org:Improvements.Search>>http://design.xwiki.org/xwiki/bin/view/Improvements/Search]]{{/warning}}
Search Improvements
Located in
- Title
Search Improvements
- Page
Search
- Raw document content
{{warning}}Moved to [[design.xwiki.org:Improvements.Search>>http://design.xwiki.org/xwiki/bin/view/Improvements/Search]]{{/warning}}
Search Interface
Located in
- Rendered document content
Requirements The aim of this proposal is to suggest and implement an overhaul to the current XWiki search interface. Search in XWiki has the following components: Search panel Search page (query field only) Search page (with results displayed) Search results currently use the default XWiki.Results template.
…Food for thought 1. Options Quick Search (Look at the "Quick Find" panel at the top left on the intranet for an example) Google-like search results Table search results Simple + Advanced search ?
…Options for search (also advanced search) Lucene has a very nice set of operators that can be used in advanced search to instruct user about search capabilities http://code.xwiki.org/xwiki/bin/view/Applications/SearchApplicationLuceneSearchQueryHelp 2.
- Title
Search Interface
- Objects
comment : 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.
…comment : 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?
…comment : Here are some additional remarks: * 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?
- Attachment content
Category Search ... All spaces All wikis SEARCH eq. xwiki* AND "search results" 100% Release Notes for XWiki Enterprise 1.2 ReleaseNotesXWikiEnterprise12 xwiki Main Location > > Sergiu Dumitriu Modified 31 Jan 2008 on 87% Macros Macros xwiki Code Location > > Vincent Massol Modified 17 Dec 2007 on 23% How do I find the backlinks to a given page?
- Attachment name
-
…
search.svg
…searchBar1.png
…searchBar2.png
- Page
Search Interface
- Raw document content
Requirements (%%) == The aim of this proposal is to suggest and implement an overhaul to the current XWiki search interface. Search in XWiki has the following components: * Search panel * Search page (query field only) * Search page (with results displayed) Search results currently use the default XWiki.Results template.
…Food for thought ===== **~1. Options** * Quick Search (Look at the "Quick Find" panel at the top left on the intranet for an example) * Google-like search results * Table search results * Simple + Advanced search ?
…Options for search (also advanced search) ==== Lucene has a very nice set of operators that can be used in advanced search to instruct user about search capabilities http://code.xwiki.org/xwiki/bin/view/Applications/SearchApplicationLuceneSearchQueryHelp ==== 2.
Search Interface
Located in
- Rendered document content
Requirements The aim of this proposal is to suggest and implement an overhaul to the current XWiki search interface. Search in XWiki has the following components: Search panel Search page (query field only) Search page (with results displayed) Search results currently use the default XWiki.Results template.
…Food for thought 1. Options Quick Search (Look at the "Quick Find" panel at the top left on the intranet for an example) Google-like search results Table search results Simple + Advanced search ?
…Options for search (also advanced search) Lucene has a very nice set of operators that can be used in advanced search to instruct user about search capabilities http://code.xwiki.org/xwiki/bin/view/Applications/SearchApplicationLuceneSearchQueryHelp 2.
- Title
Search Interface
- Objects
comment : 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.
…comment : 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?
…comment : Here are some additional remarks: * 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?
- Attachment content
Category Search ... All spaces All wikis SEARCH eq. xwiki* AND "search results" 100% Release Notes for XWiki Enterprise 1.2 ReleaseNotesXWikiEnterprise12 xwiki Main Location > > Sergiu Dumitriu Modified 31 Jan 2008 on 87% Macros Macros xwiki Code Location > > Vincent Massol Modified 17 Dec 2007 on 23% How do I find the backlinks to a given page?
- Attachment name
-
…
search.svg
…searchBar1.png
…searchBar2.png
- Page
Search Interface
- Raw document content
Requirements (%%) == The aim of this proposal is to suggest and implement an overhaul to the current XWiki search interface. Search in XWiki has the following components: * Search panel * Search page (query field only) * Search page (with results displayed) Search results currently use the default XWiki.Results template.
…Food for thought ===== **~1. Options** * Quick Search (Look at the "Quick Find" panel at the top left on the intranet for an example) * Google-like search results * Table search results * Simple + Advanced search ?
…Options for search (also advanced search) ==== Lucene has a very nice set of operators that can be used in advanced search to instruct user about search capabilities http://code.xwiki.org/xwiki/bin/view/Applications/SearchApplicationLuceneSearchQueryHelp ==== 2.
Search Proposal - Search Bar
Located in
- Rendered document content
Searh Bar - Content A. Simple Search B. Quick Search C. Advanced Search A. Simple Search Current Look Proposal 1 + the attention is set on the Search field first + in absence of query, if the "Search..." is replaced by user text, the serch icon remains + outside text (query, wiki, space) is eliminated + occuping the entire row of the display + the fields "All wikis" and "All spaces" resize depending on the content - the Search Button is too far if the user wants to keep the default settings - this is fixed by hitting "Enter" + query example shown Only one wiki Proposal 2 + the attention is set on the Search field first + in absence of query, if the "Search..." is replaced by user text, the serch icon remains + outside text (query, wiki, space) is eliminated - space remaining in the right, could be filled with query example, instructions - if one of the fields "All wikis" and "All spaces" resize, it was to resize also the "Search" field + the Search Button near the query + location setting like wiki and space are grouped visually and set as second step - if we have only one wiki the search is taking two rows B.
…q: if the user selects a space can the quick search look only in the selected space? q: how we manage multi spaces? Suggestion: don't highlight the query in space names Constrain: the highlight tehnique in quick search must be the same with the highlight tehnique in result list Proposal 1 + display the first 10-15 first most relevant items + separation between title and space (using the same colors as in settings) - the quick search results are too crowded- what happens when we have big title and big space names?
- Title
Search Proposal - Search Bar
- Objects
comment : JV just made a good point: if we want the search bar to be generic / scalable (that is, if we want to be able to use it for applications or to add search options in the advanced search) we will have to put the additional drop-down menus under the main search query field.
- Attachment name
XWiki-Main-LuceneSearch1236000549609.png
- Raw document content
Advanced Search>>http://incubator.myxwiki.org/xwiki/bin/view/Mockups/SearchProposal+SearchBar#advanced]] == (% id="simple" %)A. Simple Search (%%) == ==== Current Look ==== [[image:XWiki-Main-LuceneSearch1236000549609.png]] ==== Proposal 1 ==== + the attention is set on the Search field first + in absence of query, if the "Search..." is replaced by user text, the serch icon remains + outside text (query, wiki, space) is eliminated [[image:searchbar1.png]] + occuping the entire row of the display + the fields "All wikis" and "All spaces" resize depending on the content - the Search Button is too far if the user wants to keep the default settings - this is fixed by hitting "Enter" + query example shown ===== Only one wiki ===== [[image:searchbar1S.png||alt="E"]] ==== Proposal 2 ==== + the attention is set on the Search field first + in absence of query, if the "Search..." is replaced by user text, the serch icon remains + outside text (query, wiki, space) is eliminated [[image:searchbar2.png]] - space remaining in the right, could be filled with query example, instructions - if one of the fields "All wikis" and "All spaces" resize, it was to resize also the "Search" field + the Search Button near the query + location setting like wiki and space are grouped visually and set as second step - if we have only one wiki the search is taking two rows == (% id="quick" %)B.
…q: if the user selects a space can the quick search look only in the selected space? q: how we manage multi spaces?
Search Proposal - Search Bar
Located in
- Rendered document content
Searh Bar - Content A. Simple Search B. Quick Search C. Advanced Search A. Simple Search Current Look Proposal 1 + the attention is set on the Search field first + in absence of query, if the "Search..." is replaced by user text, the serch icon remains + outside text (query, wiki, space) is eliminated + occuping the entire row of the display + the fields "All wikis" and "All spaces" resize depending on the content - the Search Button is too far if the user wants to keep the default settings - this is fixed by hitting "Enter" + query example shown Only one wiki Proposal 2 + the attention is set on the Search field first + in absence of query, if the "Search..." is replaced by user text, the serch icon remains + outside text (query, wiki, space) is eliminated - space remaining in the right, could be filled with query example, instructions - if one of the fields "All wikis" and "All spaces" resize, it was to resize also the "Search" field + the Search Button near the query + location setting like wiki and space are grouped visually and set as second step - if we have only one wiki the search is taking two rows B.
…q: if the user selects a space can the quick search look only in the selected space? q: how we manage multi spaces? Suggestion: don't highlight the query in space names Constrain: the highlight tehnique in quick search must be the same with the highlight tehnique in result list Proposal 1 + display the first 10-15 first most relevant items + separation between title and space (using the same colors as in settings) - the quick search results are too crowded- what happens when we have big title and big space names?
- Title
Search Proposal - Search Bar
- Objects
comment : JV just made a good point: if we want the search bar to be generic / scalable (that is, if we want to be able to use it for applications or to add search options in the advanced search) we will have to put the additional drop-down menus under the main search query field.
- Attachment name
XWiki-Main-LuceneSearch1236000549609.png
- Raw document content
Advanced Search>>http://incubator.myxwiki.org/xwiki/bin/view/Mockups/SearchProposal+SearchBar#advanced]] == (% id="simple" %)A. Simple Search (%%) == ==== Current Look ==== [[image:XWiki-Main-LuceneSearch1236000549609.png]] ==== Proposal 1 ==== + the attention is set on the Search field first + in absence of query, if the "Search..." is replaced by user text, the serch icon remains + outside text (query, wiki, space) is eliminated [[image:searchbar1.png]] + occuping the entire row of the display + the fields "All wikis" and "All spaces" resize depending on the content - the Search Button is too far if the user wants to keep the default settings - this is fixed by hitting "Enter" + query example shown ===== Only one wiki ===== [[image:searchbar1S.png||alt="E"]] ==== Proposal 2 ==== + the attention is set on the Search field first + in absence of query, if the "Search..." is replaced by user text, the serch icon remains + outside text (query, wiki, space) is eliminated [[image:searchbar2.png]] - space remaining in the right, could be filled with query example, instructions - if one of the fields "All wikis" and "All spaces" resize, it was to resize also the "Search" field + the Search Button near the query + location setting like wiki and space are grouped visually and set as second step - if we have only one wiki the search is taking two rows == (% id="quick" %)B.
…q: if the user selects a space can the quick search look only in the selected space? q: how we manage multi spaces?
Search Interface
Located in
- Title
Search Interface
- Objects
comment : 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.
…comment : 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?
…comment : Here are some additional remarks: * 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?
- Attachment content
Category Search ... All spaces All wikis SEARCH eq. xwiki* AND "search results" 100% Release Notes for XWiki Enterprise 1.2 ReleaseNotesXWikiEnterprise12 xwiki Main Location > > Sergiu Dumitriu Modified 31 Jan 2008 on 87% Macros Macros xwiki Code Location > > Vincent Massol Modified 17 Dec 2007 on 23% How do I find the backlinks to a given page?
- Attachment name
-
…
search.svg
…searchBar1.png
…searchBar2.png
- Page
Search Interface
- Raw document content
{{warning}}Moved to [[design.xwiki.org:Mockups.Search Interface>>http://design.xwiki.org/xwiki/bin/view/Mockups/Search Interface]]{{/warning}}
Search Interface
Located in
- Title
Search Interface
- Objects
comment : 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.
…comment : 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?
…comment : Here are some additional remarks: * 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?
- Attachment content
Category Search ... All spaces All wikis SEARCH eq. xwiki* AND "search results" 100% Release Notes for XWiki Enterprise 1.2 ReleaseNotesXWikiEnterprise12 xwiki Main Location > > Sergiu Dumitriu Modified 31 Jan 2008 on 87% Macros Macros xwiki Code Location > > Vincent Massol Modified 17 Dec 2007 on 23% How do I find the backlinks to a given page?
- Attachment name
-
…
search.svg
…searchBar1.png
…searchBar2.png
- Page
Search Interface
- Raw document content
{{warning}}Moved to [[design.xwiki.org:Mockups.Search Interface>>http://design.xwiki.org/xwiki/bin/view/Mockups/Search Interface]]{{/warning}}
Blog Search
Located in
- Title
Blog Search
- Objects
content : #panelhiddenheader($msg.get("Search")) <form action="$xwiki.getURL('Blog.Search')"> <div id="globalsearch"> <input id="globalsearchinput" type="text" name="text" value="$msg.get('panels.search.inputText')" size="15" onfocus="if (this.value == '$msg.get('panels.search.inputText')') value=''; this.select();" onblur="if (this.value == '') value='$msg.get('panels.search.inputText')'; this.blur()"/> <input class="button" value="$msg.get('panels.search.submit')" type="image" src="$xwiki.getSkinFile("go.png")"/> </div> </form> #panelfooter()
…description : Search tool for the blog application.
…name : Blog Search
- Page
Blog Search
Blog Search
Located in
- Title
Blog Search
- Objects
content : #panelhiddenheader($msg.get("Search")) <form action="$xwiki.getURL('Blog.Search')"> <div id="globalsearch"> <input id="globalsearchinput" type="text" name="text" value="$msg.get('panels.search.inputText')" size="15" onfocus="if (this.value == '$msg.get('panels.search.inputText')') value=''; this.select();" onblur="if (this.value == '') value='$msg.get('panels.search.inputText')'; this.blur()"/> <input class="button" value="$msg.get('panels.search.submit')" type="image" src="$xwiki.getSkinFile("go.png")"/> </div> </form> #panelfooter()
…description : Search tool for the blog application.
…name : Blog Search
- Page
Blog Search


