| Page Properties | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Summary
- This module will implement the search functionality in slidewiki platform, i.e. the users will be able to search slidewiki content & semantics. Content search will cover most of slidewiki entities like decks, slides, comments, questions, tests, users, institutions, etc.
- A simple search box for keywords as well as advanced search fields will be provided so that user can set specific criteria to his searches.
- Filters will also be provided in the results page in order for the user to manage the results better.
Background and goals
Assumptions
Requirements
| # | Title | User Story | Importance | Notes | JIRA |
|---|---|---|---|---|---|
| 1 | Relevance | If one searches with "Semantic Data Web Lecture Series" the whole expression should be queried first, then parts of it and finally the words themselves. | Must Have |
This is the default behavior of queries in SOLR | SWIK-138 |
| 2 | Auto |
| -suggest | Auto |
| suggestion should be created in such a way that it will propose the options of existing presentations or decks. For instance, if the user types “Open E”, auto fill should provide “Open Education” rather than “Open Edit”. Therefore, instead of searching for every type of auto filling, it should scan the database to match the existing ones. | Must Have |
| 3 | Tag cloud | Tag cloud was taking up too much space in the old platform. A possible solution is that it should be hidden and appear only when called. |
| 4 | Search Functionality | Basic Search Box: user inserts keywords and gets results Advanced search: Apart from the basic search box, filter fields are also provided to the user so that search criteria are applied in the initial query | Must Have |
| SWIK-138, SWIK-267, SWIK-268, SWIK-269, SWIK-405, SWIK-828 | |||||
| 5 | Facets in results | Facets will be provided in the results page, so that results can be further filtered | Must Have |
| 6 |
| Sorting | Search results should be sorted based on relevance, title, last update date etc. | Must Have |
User interaction and design
Search results UI
UI proposed following discussion in SWIK-707 . Mock up below proposes:
...
Source material for user/stakeholder feedback
Comments from SWIK-863 (we should consider them when re-designing search results):
- would be better if we aligned the search results and display it in a more structured manner (maybe reuse deckOverview components and something similar for slides with thumbnail).
- can we use the same icons used in deck tree for slides and decks?
- what I see as other versions are not exactly other versions of slides e.g. when I try http://testing.slidewiki.org/search/q=semantic%20web it shows different usage of the same revision. Is it the intended behavior?
Requirements (/user stories) from pilot roadmap:
Evaluation at UniBonn :
Project Partners feedback: