Difference between revisions of "Improve project search engine (GSoC task)"
(Created page with "The [https://archive.softwareheritage.org/ homepage of the Software Heritage archive] features a small search engine, that searched in project URLs and project metadata. Proje...") |
(add § about web ui) |
||
| Line 15: | Line 15: | ||
instead of simply doing a full-text search on the entire metadata; | instead of simply doing a full-text search on the entire metadata; | ||
but we are open to suggestions. | but we are open to suggestions. | ||
| + | |||
| + | Depending on your preferences, this can be either purely backend changes, | ||
| + | or may involve changes to the web interface to use these new features. | ||
[[Category:GSoC task]] | [[Category:GSoC task]] | ||
Revision as of 12:16, 10 February 2021
The homepage of the Software Heritage archive features a small search engine, that searched in project URLs and project metadata. Project metadata includes name, description, authors, etc.
By the time GSoC starts, it will be implemented by a very small Python service (under 100 lines of code) backed by ElasticSearch.
This service is a MVP (Minimum Viable Product) that was written to replace an older service, based on Postgresql, which was too slow. So there is a lot of room for improvement in terms of adding features and making results more relevant.
Most of the features we have in mind are to allow finer search on project metadata, instead of simply doing a full-text search on the entire metadata; but we are open to suggestions.
Depending on your preferences, this can be either purely backend changes, or may involve changes to the web interface to use these new features.