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

Inconsistent search results #2

Open
grunweg opened this issue Dec 7, 2014 · 3 comments
Open

Inconsistent search results #2

grunweg opened this issue Dec 7, 2014 · 3 comments

Comments

@grunweg
Copy link

grunweg commented Dec 7, 2014

Steps to reproduce:
Go to https://jpeople.jacobs-cs.club/. Enter "Michael" into the search bar, press enter, see several hits appearing (so apparently a valid query was made.)

Expected result: Among the hits, I can also find "Michael Benjamin Rothgang".
Actual results: I count 28 hits, but not this one. However, when searching for "Rothgang" (or even "Rot" already), I get only few hits, including the MBR one. How come?

@tkw1536
Copy link
Member

tkw1536 commented Dec 7, 2014

Hit the load more button at the very button (maybe this should be done automatically). Then "Michael Rothgang" shows up. Also searching for "Michael R" dramatically reduces the result.

Maybe we should prioritise first names in the search (we should think about prioriitisation anyways. )

@grunweg
Copy link
Author

grunweg commented Dec 7, 2014

Yeah, "load more" fixes it for me. +1 for rethinking prioritisation, but to me at least it's not obvious whether first or last names should be preferred.
What you could do, however, is note that there were many more results, and asking me if I wanted to show them all/mention the load more button at the bottom. That seems like a good thing anyways.

@grunweg
Copy link
Author

grunweg commented Apr 12, 2015

Re-thinking how this should be: Can you add something like "displaying first N matches, M found", with possibly a button "load all" (not only "load more") - quite a few times I already found myself clicking "load more" almost until exhaustion - this would improve a lot by this.
(And as I'd see how matches I'd load, performance cliffs or so would be "my fault".)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants