In earlier versions of Find MoJ data we showed 2 levels: domain and subdomain. This allowed us to organise metadata first by organisational unit (e.g. HMCTS) and then have finer grained subject areas within each one (e.g. different kinds of courts)
Later, we swapped this out for a single-level domain model. However, since this is not testing well, and Scottish Gov have also mentioned using subdomains, I'm proposing we add subdomains back again in some form.
This is a placeholder ticket to record what needs doing if/when we revisit this.
Value of a hierarchical filter
we can restrict the top level subject area to a small number to avoid overwhelming users with choice
it allows the user to be either vague or specific when filtering by subject area
Current design: filter by top level domain
Behaviour
there is a single list of options
domains only get displayed as an options if they are top-level
if subdomains are used, certain entities will be inaccessible by browse / filtered search
Datahub supports arbitrarily nested domains.
In earlier versions of Find MoJ data we showed 2 levels: domain and subdomain. This allowed us to organise metadata first by organisational unit (e.g. HMCTS) and then have finer grained subject areas within each one (e.g. different kinds of courts)
Later, we swapped this out for a single-level domain model. However, since this is not testing well, and Scottish Gov have also mentioned using subdomains, I'm proposing we add subdomains back again in some form.
This is a placeholder ticket to record what needs doing if/when we revisit this.
Value of a hierarchical filter
Current design: filter by top level domain
Behaviour
listDomains
query, which excludes subdomains (https://github.com/ministryofjustice/find-moj-data/pull/597)Previous design: Domain/Subdomain
Behaviour
Definition of Done