-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autocomplete feature for 4.0 search #108
Comments
Moving to "In Review" for it to be worked on after 4.0 is released. |
This week I brought up autocomplete in the context of making files searchable from the dataset page and this idea was captured in a Google Doc. We gave up on autocomplete relatively early on in developing Dataverse 4.0 (removing it in 83e8705 ) but I'm not sure if the bugs were due to JSF/Primefaces or something I was doing wrong on the backend. Now that @raprasad has pioneered a new way of building pages using nunjucks.js I think it would be worth giving autocomplete another try at some point. I can imagine autocomplete being a feature of the Search API that could be used by mobile applications or third party clients. From looking at the code I'm realizing that I was attempting to use Solr's TermsComponent which is billed as the easiest one to start with but from searching through the Solr mailing list I found a fantastic blog post by @alessandrobenedetti at http://alexbenedetti.blogspot.co.uk/2015/07/solr-you-complete-me.html and I'd like to try Solr's Suggester feature instead. |
Offset by better faceting and performance would be an issue so not as feasible as when first conceived of. |
for non-JSF, use jquery + API endpoint. |
Author Name: Philip Durbin (@pdurbin)
Original Redmine Issue: 3517, https://redmine.hmdc.harvard.edu/issues/3517
Original Date: 2014-02-03
Original Assignee: Philip Durbin
We are working on an autocomplete feature for 4.0 in search.
Redmine related issue(s): 3430
The text was updated successfully, but these errors were encountered: