Skip to content
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

Closed
eaquigley opened this issue Jul 9, 2014 · 4 comments
Closed

Autocomplete feature for 4.0 search #108

eaquigley opened this issue Jul 9, 2014 · 4 comments
Labels
Feature: Search/Browse Type: Feature a feature request UX & UI: Design This issue needs input on the design of the UI and from the product owner

Comments

@eaquigley
Copy link
Contributor

eaquigley commented Jul 9, 2014


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


@eaquigley eaquigley added this to the Dataverse 4.0: In Review milestone Jul 9, 2014
@eaquigley eaquigley modified the milestones: In Review, Dataverse 4.0: In Review Jul 15, 2014
@eaquigley
Copy link
Contributor Author

Moving to "In Review" for it to be worked on after 4.0 is released.

@scolapasta scolapasta modified the milestones: In Review - Long Term, In Review - Short Term May 8, 2015
@pdurbin
Copy link
Member

pdurbin commented Jul 30, 2015

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.

@pdurbin pdurbin removed their assignment Jan 21, 2016
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@mheppler mheppler added the UX & UI: Design This issue needs input on the design of the UI and from the product owner label Jan 29, 2016
@kcondon
Copy link
Contributor

kcondon commented May 2, 2016

Offset by better faceting and performance would be an issue so not as feasible as when first conceived of.

@raprasad
Copy link
Contributor

pdurbin added a commit that referenced this issue Mar 20, 2018
Sadly, we gave up on getting autocomplete working (removed in 83e8705)
so no point in maintaing this AutoCompleteBean.java. #108 was closed a
long time ago but maybe some day we can add this feature to Dataverse
under a new issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Search/Browse Type: Feature a feature request UX & UI: Design This issue needs input on the design of the UI and from the product owner
Projects
None yet
Development

No branches or pull requests

6 participants