-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feature/text locator result source indicator #194
Feature/text locator result source indicator #194
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A changelog entry is missing.
…//github.com/Dataport/polar into feature/text-locator-result-source-indicator
🏓 @dopenguin The changelog entry has been unmissingfied. b3b5249 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also added a suggestion as I prefer imperative in changelogs
apply suggestion "imperator changelogs" Co-authored-by: Pascal Röhling <[email protected]>
…/text-locator-result-source-indicator
…//github.com/Dataport/polar into feature/text-locator-result-source-indicator
Summary
The results in the TextLocator client may seem confusing at times, since not all places to each piece of literature, nor all pieces of literature to each place are shown at all times. However, this must stay this way; else, we'd pretty much load the whole database due to overlap chains. (Literature has place, which has other literature, which has other places, which ...)
Still, users may have problems in understanding this in detail. To help with this, a minimal indicator has been placed in the UI so that the source for the currently visible results is kept. This may later be extended by a more sophisticated description in e.g. a tooltip, depending on the customer review. For now, it's mostly meant to transport the idea and implement the feature roughly.
Instructions for local reproduction and review
Run TextLocator and try all different ways to display the search results. All major paths (search for literature/toponym/geometry) have their own respective display string.
Relevant tickets, issues, et cetera
Based/Blocks on #172