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

Add 3 additional filters to front end #2961

Closed
seanprivett opened this issue Jan 16, 2024 · 4 comments
Closed

Add 3 additional filters to front end #2961

seanprivett opened this issue Jan 16, 2024 · 4 comments
Assignees

Comments

@seanprivett
Copy link

seanprivett commented Jan 16, 2024

Removing as this duplicates #3047

The following filters to be implemented in the front end:

Source system or service name (acronym OR full name) _- eg. NOMIS / National Offender Management System, LPA / Lasting Power of Attorney
Data location/availability (AP, other platform,...)
Sensitivity level

Subdomain not to be implemented in this ticket

@alex-vonfeldmann
Copy link

User stories:

  • As a user, I want to be able to search for all data that matches a specific topic, so I can see whether and how much relevant data exists (eg. “rehabilitation science”).
  • As a user, I want to be able to search for data supporting a specific query/insight/reporting need, so can see whether and how much relevant data exists (eg. “forecast prison occupation”).
  • As a user, I want to be able to filter down topic and query search results by effective and easy to recognise filters, so I can narrow down the results list to a manageable subset.

@alex-vonfeldmann
Copy link

alex-vonfeldmann commented Feb 7, 2024

@seanprivett the simplified 'high ranked' filter list for UR purposes could look something like his:

  • Domain
  • Subdomain - THS WILL BE A SEPARATE SPIKE
  • Source system or service name (acronym OR full name) _- eg. NOMIS / National Offender Management System, LPA / Lasting Power of Attorney
  • Data location/availability (AP, other platform,...)
  • Sensitivity level

I imagine source system or service name could be delivered as tags rather than as filter UI components

I expect users will want additional filters to the above which we will hear about in UR

I'm not sure the current options for the search result sort is right ('Relevance / Ascending / Descending'). 'Recently created' and 'Recently updated' might be better candidates. 'Relevance' might be useful if someone can explain to me how this is actually modelled and ranked?

I'm not sure that we can deliver the two use cases above if we do not massage the metadata content (ie. adding proper descriptions, tags, etc)

@jemnery
Copy link
Contributor

jemnery commented Feb 8, 2024

First stab at subdomains from refinement:

HMPPS
  -- prisons
  -- probation
HMCTS
  -- magistrates courts
  -- crown courts
  -- family courts
  -- civil courts
OPG
  -- Lasting power of attorney
  -- supervision orders
HQ
  -- people
  -- finance
  -- performance
  -- estates
LAA
  -- legal aid
  -- public defender
  -- civil legal advice
CICA (no subdomains)

@alex-vonfeldmann
Copy link

  • CICA (as a domain)

@seanprivett seanprivett changed the title Refine filtering for search Add 3 additional filters to front end Feb 15, 2024
@tom-webber tom-webber self-assigned this Feb 15, 2024
@tom-webber tom-webber removed the status in Data Catalogue Feb 22, 2024
@tom-webber tom-webber moved this to Done in Data Catalogue Feb 22, 2024
@github-project-automation github-project-automation bot moved this from 👀 TODO to 🎉 Done in Analytical Platform Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Status: Done ✅
Development

No branches or pull requests

5 participants