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

Support domain-specific keywords #1675

Closed
choldgraf opened this issue Aug 15, 2017 · 3 comments
Closed

Support domain-specific keywords #1675

choldgraf opened this issue Aug 15, 2017 · 3 comments

Comments

@choldgraf
Copy link

I think it'd be really helpful for people in the scientific community if there were keywords based on scientific / analytic domain (e.g., geospatial analytics, neuroscience) as opposed to the more functional computer-sciencey keywords that are there (e.g., API, wrapper, etc). Any plans to do something like this?

One idea that comes to mind is not to support this explicitly, but do improve the search algorithm in order to find packages that are conceptually related even if the search phrase doesn't explicitly show up with the package. If there's already a dependency tree that (I assume) is used in generating search results, perhaps it could be supported by an idea of project similarity based on the content of their READMEs, documentation, etc.

@andrew
Copy link
Contributor

andrew commented Aug 30, 2017

@choldgraf at the moment all the keywords come from being specified in the libraries that are indexed, looks like there are 46 projects tagged neuroscience: https://libraries.io/keywords/neuroscience

The problem seems to be more around the UI only showing the most popular keywords in the search UI:

screen shot 2017-08-30 at 4 27 47 pm

Those keywords should really be only the ones that are related to the projects from the search results, I wonder if we can get elasticsearch to do that automatically when faceting.

@choldgraf
Copy link
Author

ahh I see - I didn't notice that there were non-language-specific keywords later in the list...

@andrew andrew added the roadmap label Oct 9, 2017
@andrew
Copy link
Contributor

andrew commented Oct 9, 2017

Moving this to the Backlog as we'd still like to implement it but can't see that happening in the near future.

@andrew andrew closed this as completed Oct 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants