Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties
Target release
Epic 
Document status
invalidmacro
Document owner
Designer
DevelopersFormer user (Deleted)
QA
Work Package & deliverables 
Related JIRA tasks

SWIK-138, SWIK-230, SWIK-267, SWIK-268, SWIK-269

...

#TitleUser StoryImportanceNotesJIRA
1RelevanceIf 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
 
2Auto fillAuto fill 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 

 

 

 

 

 

 

 

 

 

3Result language sortingResults should be viewed in different languages   
4Tag cloudTag 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.   
5Search 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  
46Facets in resultsFacets will be provided in the results page, so that results can be further filteredMust Have  
57Result language sortingResults should be viewed in different languages     
68Tag cloud     

User interaction and design

...

Evaluation/improvements by Farid Hasanov master thesis :

 

Issues with search functionality. Several issues arose in terms of searching for the website. The structured overview of them is shown here.

...

The advantage of this approach is that the user can quickly search for something and already see the results. In case of dissatisfaction he or she can change the domain from presentations/decks to authors. This solution saves time if the search object is highly relevant. So if a user searches for “Semantics”, he will get a result for “Semantic web lectures” at once without using the advanced search. Hereby I assume that this approach should be favoured over the previous two. Concerning searching for an author, the search should be fulfilled not only by the user’s login name, but also by his real name or e-mail address. To this end, coders should create a bind between login name, real name and e-mail and index them in database. In addition, here, a fixture for the Tag Cloud issue is proposed. The Tag Cloud will be moved to the tabs menu and can be accessed from there. The user can activate the tags by selecting them, thereby opening more space to the left and allowing the display of more search results.

 

Evaluation at UniBonn :  


Project Partners feedback: