-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
User stories:
|
@seanprivett the simplified 'high ranked' filter list for UR purposes could look something like his:
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) |
First stab at subdomains from refinement:
|
|
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
The text was updated successfully, but these errors were encountered: