bcgov / bcgov/entity

PPR Search - Search Result list of Exact and Partial Matches not Convenient for printing or screen shots

Open
#8,623 3 comments 0 reactions 0 assignees View on GitHub
Assets Client/Staff Feedback enhancement PPR Priority2 Review with Business
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

GIVEN I am a PPR user
WHEN I choose a PPR search option, enter search criteria and click to search
THEN I see the exact and similar matches
AND I want the ability to save an image of the exact and similar matches that were retrieved

From Client Usability Testing:

Some PPR users are required to screen shot the search results page to show exact and partial matches, as well as which results were selected for reporting to their clients. The search results page initially only shows 3 results and scrolling is required to see the rest. A result list with hundreds of exact and partial matches won't be easy to screen shot.

Suggestions include:
- Have the screen focus jump to the Search Results section with a larger search results window so more results can be viewed at once.
~~- Include the Search Results with the details of selected registrations in the PDF file.~~

**Suggestion from Tracey** - the current height of the search result box with table is shorter than it needs to be. I would recommend increasing the height of the box to 650px minimum (starting from top of white container box to bottom of search table rows), which will allow users to also see more results without having to scroll as often.

![image.png](https://images.zenhubusercontent.com/601b37c65322cfe9e09d47c2/a6a55468-1dc6-4a59-9797-c7a2864deee0)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the PPR search results page and inspect the search-results container and table that currently show only three results. Increase the results area so more matches are visible at once, using the suggested 650px minimum as the target; done means exact and partial matches are easier to print or capture without as much scrolling.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.