openlibhums / openlibhums/janeway
Search function improvements
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
ULBD have had a long-open ticket about search function improvements / issues. This is specifically around the strictness of the search, inability to user jokers/wildcards and working with special characters.
"I’ve tested the search function over at ZIF and it’s working well. I just figured out you cant use jokers if you are unsure about the spelling (like Renner = re?er). Also the search is quite strict. It does not forgive missing letters. If I type in „renne“ I get zero results, only „renner“ will show me the article. This is also the issue for other themes."
"I just wanted to know If any improvements have been made. One journal reported some issues, like searching for the author "Kursiša":
If you fill in "Kursisa" without the special character there is no hit. You have to type the exact phrase. You also have to deactivate all other search options besides "seach authors" to find all articles, which is really strange."
We may need to invesitgate if we can match special character with their regular cousins / do some fuzzy matching?
This links to: https://janeway.freshdesk.com/a/tickets/5198
It has been requested by Andy this is top of BARF for 31/07.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported searches for “re?er”, “renne”, and “Kursisa” against the current search interface, including the author-only option. Then locate the search implementation and its tests; done means the intended wildcard, partial-match, special-character, and search-option behavior is documented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100