IntersectMBO / IntersectMBO/govtool

Search scope is too small and search results pages need context for both DReps and GAs

Open
#2,223 4 comments 0 reactions 0 assignees View on GitHub
🌐 Post/After Plomin hard fork 🎨 Design Needed 🧬 UX
Dominant language
HTML
Stars
21
Forks
29
Avg merge
2d 22h
Merged PRs (30d)
7

Description

Problem:

1. Search results have no context - currently a search just returns the same DRep or GA list of 'cards' and the user cannot tell if their search has worked, or not. Also, we are searching metadata, and there are differing fields of metadata, of which the context is important.

The reason we have this issue is that the search was designed before we had metadata in GovTool. It was only made to handle the drep name and ID.I know everyone is familiar with a DRep metadata, See screenshot of DRep detail page for all the fields on it.

For DReps: he fields that we should search:

- Drep name
- DRep ID
- Objectives
- Motivations
- Qualifications

Maybe also:

- Links
- Identity

The same problem is found in our Governance Actions search:
The fields we should search:

- GA Type
- Title
- Abstract

- Motivation
- Rationale

Maybe also:

- Receiving address
- Supporting links

It would be much more informative if we provide more and better context for search results, and that would mean telling users where we found their search term.I've made a quick wireframe of this, and attached it below.

Drep fields on detail page: ![image](https://github.com/user-attachments/assets/3954b70a-5ed0-4bf1-bcc8-aa8253710bb7)

GA fields on detail page: ![image(1)](https://github.com/user-attachments/assets/65d4f475-b28b-4ca4-90a9-ca7181841547)

Wireframe solution:
![search results improved](https://github.com/user-attachments/assets/7d237d81-f3d6-4620-8a6d-326979b203b5)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.