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

Design Clarify boolean instructions for legal search pages #2051

Closed
1 task done
jwchumley opened this issue Jun 5, 2018 · 8 comments
Closed
1 task done

Design Clarify boolean instructions for legal search pages #2051

jwchumley opened this issue Jun 5, 2018 · 8 comments
Assignees
Milestone

Comments

@jwchumley
Copy link

jwchumley commented Jun 5, 2018

What do we want:
To make the boolean search usage extremely clear on the legal search pages

Why do we want it?
Because there is confusion around the different uses on the regular and advanced search interfaces.

  • Figure out a way for users to know when and where to use boolean terms and when and where they are implied.
@jwchumley jwchumley added this to the Sprint 6.2 milestone Jun 5, 2018
@jwchumley jwchumley changed the title Clarify boolean instructions for legal search pages Design Clarify boolean instructions for legal search pages Jun 5, 2018
@PaulClark2 PaulClark2 modified the milestones: Sprint 6.4, Sprint 6.5 Jul 3, 2018
@JonellaCulmer JonellaCulmer modified the milestones: Sprint 6.5, Sprint 6.6 Jul 19, 2018
@JonellaCulmer JonellaCulmer self-assigned this Aug 13, 2018
@JonellaCulmer
Copy link
Contributor

JonellaCulmer commented Aug 13, 2018

Below is a mock-up of that includes two adjustments to the existing boolean search.

@patphongs I know we discussed modifying this further to remove the instructions from the "Find documents with..." pop-up, but I'd like to test this option first before removing those instructions further. My intention is to further clarify the instructions and make them a bit more clear before we remove them entirely. This would also be helpful on the legal resources landing page, where uses may not be aware that they can use those symbols. But I'm happy to discuss it further if you have reservations.

Designs:
In addition to clarifying the instructions for using boolean symbols on the searches for AOs, MURs, Statutes and the legal landing page search, there is also the addition of a tooltip for the Keyword search on the main search panels. This would work for each legal resource search where boolean search terms are used. Including: Advisory opinions, Matters under review and Statutes.

screen shot 2018-08-13 at 9 02 13 am

screen shot 2018-08-13 at 10 11 58 am

Next steps:

  • Content review of the language draft in the updated boolean search pop-up and tooltip language @llienfec @dorothyyeager @AmyKort
  • Make any additional edits
  • Move to implementation issue
  • Move to testing issue

@AmyKort
Copy link

AmyKort commented Aug 13, 2018

Maybe: Refine a keyword search by using AND, OR, "" - to expand or limit results.

I think it is a little confusing to call AND a symbol (but maybe I'm wrong), and since you can use these factors in combination, I think we should avoid the "or."

@JonellaCulmer
Copy link
Contributor

@AmyKort I updated the mock-up with your suggested text. If there are no other edits, I can move this to an implemention issue and create a testing ticket.
Here's the updated version:

screen shot 2018-08-14 at 8 40 26 am

@AmyKort
Copy link

AmyKort commented Aug 14, 2018

@llienfec and @dorothyyeager What do you think?

@llienfec
Copy link
Contributor

Looks good to me.

For the keyword info box, I like the language change.

For the big box, I like the "or" in the explanation box. I'll be interested to see whether this will help with people using the symbols on the left hand side.

@dorothyyeager
Copy link
Contributor

Looks good to me as well. I get confused on boolean searches so this seemed clear to me.

@AmyKort
Copy link

AmyKort commented Aug 14, 2018

Awesome! Thanks @JonellaCulmer !

@JonellaCulmer
Copy link
Contributor

Great! Thanks everyone! I've opened an implementation and a testing ticket to move this work forward. Both are linked below.

Implementation ticket: #2283
Testing ticket: fecgov/fec-testing#112

Closing this ticket in favor of those issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants