DASISH / TERESAH

DASISH Task 2.3 Tools Registry
European Union Public License 1.1
4 stars 2 forks source link

UC 2: Search for a tool #37

Closed jfihn closed 9 years ago

jfihn commented 10 years ago

Context of use: User wants to search for a tool. User knows the name of the tool he is interested in and wants to find more details about it.

Minimal Guarantees: Each request to the search functionality is responded according to user sessions state and logged for statistical purposes.

Success Guarantees: Users are able to find the tool(s) they were looking for

Main Success Scenario - Quicksearch:

  1. System shows search box
  2. User types in the name of the tool he is looking for into the search box
  3. System displays one or more results for the search
  4. User clicks on the result he is interested in
  5. Systems redirects to the tool record page
  6. User reads information about the tool he is interested in
martavillegas commented 10 years ago

OK. everything works as expected.

PonteIneptique commented 10 years ago

Close ?

borsna commented 9 years ago

General search and facet search is now ready for testing: http://staging.teresah.php.dev.dasish.eu/search

PonteIneptique commented 9 years ago

Hey, I know I am not anymore working for this project but may I suggest to use Twitter Typeahead for the faceted search ? It provides continuous browsing as well as query and preloaded data, which seems to be a good match. I am not convinced by the actual UI (which I assume is a test one :) )

borsna commented 9 years ago

Twitter Typehad is currently used for the quicksearch and may come in use for the facet search as well. I don't know if we need filters on the facet values via a input text under each type. I think just display the most frequent at the top and a limit (~10-15 top values) with the possibility to load more via a ajax-call would work quite nicely.

The search field does a general text search in tool name and all associated facet values, the facet displayed on the left (these values are updated from the search result) will make further filtering possible from this search result.

Any suggestion how the facet list on the left hand side could improve UI-whise (I just made a fast mockup as for now)?

PonteIneptique commented 9 years ago

Actually, we used Select2 and not typeahead (Those js libraries...) http://ivaynberg.github.io/select2/

I would try to add an input list with continuous browsing and input available. For example, see : https://portal.ehri-project.eu/units on the right side (its not continuous browsing through... The part with it is private and I can't share it :/)

For the recommended facet, I would actually try with a box like recommanded facets OR add an order function for the typeahead search box (Alphabetically / Occurence) [Maybe a general setting working for each facet group ?)

Right now I don't see how to use the UI with a large set of tools.

In EHRI, we do use on top of that an autoselect jQuery little plugin which post when you select something :

$(document).on("change", ".autosubmit", function (e) {
    $(e.target).closest("form").submit();
});

And then display selected items with a button :

<span class="btn btn-group">
<span class="btn">Facet Name</span>
<a class="remove-filter btn" href="URL_WITHOUT_THIS_FACET">
<span class="glyphivcon glyphicon-remove"></span>
</a>
</span>

Using continuous browsing with select2 means that you will have to exclude previous selected results. I used something like $_GET["exclude"] parameter to pass the selected one.

One of the thing I would consider is wether there is more than 20 or X facets available, go with Continuous browsing. Else, load them directly in select 2 (Instantiating different select with two different select2 routines)

nostneji commented 9 years ago

Right now seems that database behind http://staging.teresah.php.dev.dasish.eu/ is empty and testing of the Search functionality is difficult without data. Please reply when the data is loaded and testing is possible.

borsna commented 9 years ago

Sorry, the test-data was not updated when the latest changes got pushed to staging. its up now.