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 administrative fine and Alternative Dispute Resolution datatables and canonical pages #2338

Closed
7 tasks done
Tracked by #139
JonellaCulmer opened this issue Sep 6, 2018 · 4 comments
Closed
7 tasks done
Tracked by #139
Assignees
Milestone

Comments

@JonellaCulmer
Copy link
Contributor

JonellaCulmer commented Sep 6, 2018

User story: As a user interested in enforcement matters, I want to efficiently use different enforcement data sets, so that I can complete my research quickly and easily.

What we’re after: Two types of enforcement actions, administrative fine cases and Alternative Dispute Resolution cases, need to be moved over from the Enforcement Query System (EQS). This work will require getting the data into our systems and building the front-end search and individual case pages. These cases have very similar data structures to MURs, and because of this, we should be able to extend the same templates we’re using for MURs.

This issue will examine the current research and design work that's been done to date and identify the MVP state in order to move this information from EQS.

Why we’re after it: If users are looking through one set of enforcement documents (like MURs), they most likely need to review the other types as well. Until these are available on the new site, users doing this sort of legal research are forced to use the legacy Enforcement Query System.

Completion criteria:

  • Examine prior research and identify needs
  • Examine prior designs and identify needs
  • Mock-up initial templates, including filters
  • Demo initial designs in design sync
  • Make the necessary design improvements
  • Move to implementation issue
  • Create user testing ticket Test new ADR/AF pages fec-testing#115
@JonellaCulmer JonellaCulmer added this to the Sprint 7.1 milestone Sep 6, 2018
@JonellaCulmer JonellaCulmer self-assigned this Sep 6, 2018
@JonellaCulmer
Copy link
Contributor Author

As part of determining the high-value data and filtering I'm looking at the following:

Using this spreadsheet as a basis for needs: https://docs.google.com/spreadsheets/d/1i8GeWHEeTzt3jdN3RZg3wKA_dSq2J-6CR5JGtq6G2nQ/edit#gid=0

Coupled with the existing functionality:
http://eqs.fec.gov/eqs/searcheqs?clearSession

@JonellaCulmer JonellaCulmer changed the title Design administrative fine and Alternative Dispute Resolution datatables Design administrative fine and Alternative Dispute Resolution datatables and canonical pages Sep 13, 2018
@JonellaCulmer
Copy link
Contributor Author

Mock-ups for the ADR/AF are below. These are a combination of maintaining what we currently have implemented on MURs, but also trying to incorporate some data that we already have and can implement as part of a first-round. I plan to go through these during design sync.

ADRs

screen shot 2018-09-14 at 8 29 30 am

screen shot 2018-09-14 at 8 32 04 am

Admin fines

screen shot 2018-09-14 at 8 29 53 am

screen shot 2018-09-14 at 8 32 26 am

@JonellaCulmer
Copy link
Contributor Author

JonellaCulmer commented Sep 18, 2018

Updated mockups following conversations during design sync and dev pairing.
screen shot 2018-09-18 at 9 08 24 am

screen shot 2018-09-18 at 10 58 30 am

screen shot 2018-09-18 at 9 09 18 am

screen shot 2018-09-18 at 10 58 48 am

@JonellaCulmer
Copy link
Contributor Author

Closing in favor of followup issues for implementation.

#2385
#2386

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

1 participant