10:18 < nessita> sergiusens, try this https://search.apps.ubuntu.com/api/v1/search?q=%228nzc1x4iim2xj1g2ul64%22
10:18 < nessita> ie, with double quotes, I'll explain why
10:21 < nessita> sergiusens, our package index performs analysis for both the data being indexed, and the search term. The analysis, among other things, try to parse the given string to take out the most relevant part and also search for derivates
10:23 < nessita> sergiusens, using quotes all the time is a bad idea, quotes mean exact match
10:24 < sergiusens> nessita: right, so then beowulf using the strange package name for searching is a bad idea
10:24 < sergiusens> for testing it at least
10:24 < sergiusens> as in eyeball testing
10:25 < nessita> sergiusens, indeed. Ideally, a user will search for keywords, such as "news" and we want to include results for "newspaper" for example
Querying for 8nzc1x4iim2xj1g 2ul64 as in http:// webdm.local: 4200/api/ v2/packages/ ?q=8nzc1x4iim2x j1g2ul64 is not the best test subject.
10:18 < nessita> sergiusens, try this https:/ /search. apps.ubuntu. com/api/ v1/search? q=%228nzc1x4iim 2xj1g2ul64% 22
analysis, among other things, try to parse the given string to take out the most relevant part and also search for
derivates
"newspaper" for example
10:18 < nessita> ie, with double quotes, I'll explain why
10:21 < nessita> sergiusens, our package index performs analysis for both the data being indexed, and the search term. The
10:23 < nessita> sergiusens, using quotes all the time is a bad idea, quotes mean exact match
10:24 < sergiusens> nessita: right, so then beowulf using the strange package name for searching is a bad idea
10:24 < sergiusens> for testing it at least
10:24 < sergiusens> as in eyeball testing
10:25 < nessita> sergiusens, indeed. Ideally, a user will search for keywords, such as "news" and we want to include results for