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

Improve User-Friendliness of Search Functionality and Advanced Search Options #158

Open
maehr opened this issue Oct 10, 2024 · 0 comments
Open
Assignees

Comments

@maehr
Copy link
Member

maehr commented Oct 10, 2024

Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!

The current search interface on the "Stadt.Geschichte.Basel" research data platform displays basic search results effectively but lacks certain features and enhancements that would improve user experience, especially when dealing with larger datasets or specific research needs.

Screenshot 2024-10-10 at 15 09 07
Screenshot 2024-10-10 at 15 09 21

Problems Identified

  1. Limited Search Feedback and Filters:

    • When a search term is entered (e.g., "Leuk"), the results are displayed, but there is no clear indication of additional filtering options. The user might benefit from suggestions on how to refine or expand their search (e.g., filtering by date, category, or keyword).
  2. Lack of Advanced Search Functionality:

    • There is no visible option for an advanced search where users can specify multiple criteria simultaneously (e.g., searching by date range, themes, or specific metadata fields). This would be especially useful for researchers needing more precise results.
  3. Repetitive Search Results:

    • The screenshots show what appears to be identical search results repeated in different views. There may be a need for deduplication or more distinct presentation in different contexts (e.g., list view vs. detailed view).
  4. Inconsistent Search Result Presentation:

    • The results do not make it clear what distinguishes one result from another when the same title appears. This can be confusing and does not provide much additional context or metadata to help users differentiate.
  5. Potential Accessibility Concerns:

    • The search interface lacks guidance for users who may not be familiar with the dataset's structure or terminology. A guide or tooltip explaining the search capabilities or offering examples could be beneficial.

Suggested Improvements

  1. Add Advanced Search Options:

    • Introduce an "Erweiterte Suche" (Advanced Search) feature, allowing users to filter by multiple criteria such as date, themes, keywords, or collection type. This should be easily accessible from the main search bar.
  2. Search Result Filtering and Sorting:

    • Implement dynamic filters (faceted search) that allow users to narrow down results based on criteria like time period, subject, or specific metadata. Sorting options (e.g., by relevance, date, or alphabetical) would also enhance usability.
  3. Improve the Clarity of Search Results:

    • Provide more metadata or preview content in the search results to help users distinguish between similar items. This could include additional information such as dates, themes, or descriptions.
  4. Enhance Search Interface with User Guidance:

    • Include help text, tooltips, or a dedicated "search help" section to explain the search functionalities, available filters, and advanced search features. This would assist new users in effectively using the platform.
  5. Avoid Redundancy in Search Results:

    • Ensure that search results are not repetitive by implementing deduplication algorithms or by displaying different levels of detail for the same result depending on the context (e.g., summarized in list view, detailed in expanded view).

What type of pull request would this be?

New Feature

Any links to similar examples or other references we should review?

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