Fec-cms: Design experience for linking to legacy legal resource tools
At the time of the site flip, we will need to continue to provide links to EQS and the AO search, alongside our own searches for those items. So that legal researchers always know where they can get what information, we need to design the experience around how those two things co-exist.
Basically we need to address why one would use the new tools vs. the old tools, and provide links back to the old tools. We'll need to talk with @AmyKort more about how to message this in the interface.
cc @nickykrause @onezerojeremy @jenniferthibault
noahmanger
All 16 comments
For the following tools, I know we have begun implementation on the beta site, but each is in varying stages of completeness for functionality or data quality:
I would need our legal devs and subject matter experts to help point out the specific ways that the tools on the beta site differ, or have incomplete data, but I think we have enough to start crafting an approach and basic messaging.
Placement of notice: guiding principle
Place the notice where it impacts the results you expect to see (or as close as we can get to that spot with the current site map)
- For the features we have preliminary search results pages for (AOs, Regs, MURs), this means we can put the notice at the top of the search results list (as we currently do to alert people Archived MURs aren't available) or in the filter panel.
We have precedent for each, but the search results area seems a better use of space.
Content of notice: guiding principles
These definitely benefit from content review, but I started with the template @emileighoutlaw set in https://github.com/18F/fec-cms/issues/836#issuecomment-284900830 for safe starting territory.
Set expectations for work in progress or not
- when we're actively developing something, say so. When we aren't planning to make improvements soon, acknowledge that too in order to set expectations for timely improvements (AOs) or somewhat of a wait (regulations improvements)
Help users know what's different between the two experiences
- Mention specific differences in data availability or completeness
Direct users to where the data is complete
- the transition site's URL
Drafts
Timeline for notifications
- These could be placed as early as they can be implemented (no need to wait until site flip, as they are accurate now), and should remain through the site transition until each feature reaches parity with its predecessor.
Thoughts on any of the above?
jenniferthibault
on 14 Mar 2017
Also — did I miss any other legal apps?
jenniferthibault
on 14 Mar 2017
@jenniferthibault Thanks for making this ticket! I was talking to @AmyKort and @amypike yesterday and there's a few missing from your list. Here's the full list, I also put in links to the new landing pages on the new site for these items. I hope this helps!
- AO Search
- http://saos.fec.gov/saos/searchao
- New site - https://beta.fec.gov/data/legal/advisory-opinions/ - Rulemakings
- http://sers.fec.gov/fosers/
- New site - To be built - MUR Archive (1975 - 1998)
- http://www.fec.gov/MUR/
- New site - https://beta.fec.gov/legal-resources/enforcement/ - Current MUR search (1999 - Present)
- http://eqs.fec.gov/eqs/searcheqs
- New site - https://beta.fec.gov/legal-resources/enforcement/ - Administrative Fine Program
- http://eqs.fec.gov/eqs/searcheqs
- New site - https://beta.fec.gov/legal-resources/enforcement/administrative-fines/ - Administrative Fine Calculator
- http://fec.gov/af/
- New site - https://beta.fec.gov/legal-resources/enforcement/administrative-fines/ - Alternative Dispute Resolution
- http://eqs.fec.gov/eqs/searcheqs
- New site - https://beta.fec.gov/legal-resources/enforcement/alternative-dispute-resolution/ - Audit Report Search
- http://fec.gov/auditsearch/auditsearch.do
- New site - https://beta.fec.gov/legal-resources/enforcement/audit-reports/
patphongs
on 14 Mar 2017
This is great Pat, thank you! I'll adjust a few things and will update this issue again with a new iteration
jenniferthibault
on 15 Mar 2017
Patterns
Use the message pattern with the information icon.
Language
I took a stab, but needs active work from @emileighoutlaw for the template she wants to establish for this notification type.
Principles:
- If we have a search feature on the new site, place the notification at the points where users can enter text to search.
- If we don't have a search feature begun on the new site, insert the notification on that feature's landing page in the overview section.
AOs
- search
- landing page
- all search results list
MURS
- enforcement landing page
- current MUR search
- archived MUR search
- all search results list
Alternative Dispute Resolution
- Landing page
Administrative Fines
- Landing page
- Fine calculator
Audit reports
- Landing page
Rulemakings
- This one is a little unusual, because we link to the Rulemaking is a section of the Regulations page. Since it's mid-page, maybe we use plain text links for now?
jenniferthibault
on 15 Mar 2017
A few thoughts (and maybe better to discuss in design pairing, but logging here before I forget):
For AOs and MURs, I like the "info message" style. This feels like the right component and placement. But for language what about also adding something to more clearly differentiate the two tools, which would also include why you'd want to use the new one over the old.
For both of those messages in the search results, they feel perhaps a little _too_ prominent. Should they be minimizable?
For ADRs and Admin Fines, what about taking the approach you suggested with rulemakings and just including regular links? Because there's not already some equivalent form of the tool on the new site, I think it's less important to call attention to their absence.
noahmanger
on 17 Mar 2017
- Language on all of these needs @emileighoutlaw , but I agree with your observation! On principle we should tell folks if there's more data/functionality on one or the other.
Love the idea of minimizing them on the data tables, I'll have that mocked up in a jiff!
The only reason I did plain-text links on rulemakings is because the text is written in paragraph style about the SERS tool. I'd prefer to use the alert style there too if we can.
I think folks will be looking for these tools, so calling the users attention isn't about pointing out the absence, it's about helping them find there it lives.
jenniferthibault
on 20 Mar 2017
Here's how the minimizing could work:
- alert would start open by default
Toggle closed:
jenniferthibault
on 20 Mar 2017
Sorry, I hit enter before finishing!
@emileighoutlaw are you ready to take this issue assignment over for content?
jenniferthibault
on 20 Mar 2017
Just chatted with Jen about a few things and here's a couple take-aways:
SERS
For the link to SERS, we want to stick with the current implementation, which uses a button:
But instead of the heading and content here being about SERS, we think it makes the most sense for it to be about the actual _substance_ of SERS (Rule making documents?). It can reference SERS, but should be oriented around what you'll actually find, no?
ADR and AO
In the spirit of framing in terms of _what you'll find_ rather than _the system you're using_, we think that instead of an alert style link to EQS from the ADR and AF pages, we could use the existing pattern of a block of copy + a button, like:
What do you think @emileighoutlaw ?
noahmanger
on 20 Mar 2017
@emileighoutlaw below is a collected summary of the alert text needed. When possible, it would be good to communicate:
- Clear differentiations between the two tools, which would also include why you'd want to use the new one over the old.
- Expectations around if the tool is a work in progress
AOs
Displayed on:
- AO landing page
- AO search table
- Legal search results list
MURs
Displayed on:
- Enforcement landing page
- MUR search table
- Legal search results list
ADR case search, Admin Fines case search, Admin fine calculator, Rulemaking document search
Displayed:
- As sections of the landing page for each type
See Noah's comment above for the best explanation of this thinking
Transferring over to you, Emileigh! Let us know if you want to pair up or have any questions on this
jenniferthibault
on 24 Mar 2017
After waiting patiently for two weeks, I finally have a draft of some words 🔒 that we can look at for all of these things.
👀 @AmyKort definitely needs to review these blurbs.
💟 And as always, I love having @jenniferthibault's and @noahmanger's smart copyedit eyes whenever they have time.
emileighoutlaw
on 6 Apr 2017
This all looks great to me.
noahmanger
on 7 Apr 2017
This works for me! I left one very small comment.
jenniferthibault
on 7 Apr 2017
This content is approved by Amy and me. 🚀 We can move to implementation
emileighoutlaw
on 7 Apr 2017
Being implemented by https://github.com/18F/openFEC-web-app/issues/1900
noahmanger
on 7 Apr 2017
Related issues
lbeaufort
·
5Comments
AmyKort
·
5Comments
JonellaCulmer
·
6Comments
dorothyyeager
·
4Comments
AmyKort
·
3Comments
Most helpful comment
Just chatted with Jen about a few things and here's a couple take-aways:
SERS
For the link to SERS, we want to stick with the current implementation, which uses a button:
But instead of the heading and content here being about SERS, we think it makes the most sense for it to be about the actual _substance_ of SERS (Rule making documents?). It can reference SERS, but should be oriented around what you'll actually find, no?
ADR and AO
In the spirit of framing in terms of _what you'll find_ rather than _the system you're using_, we think that instead of an alert style link to EQS from the ADR and AF pages, we could use the existing pattern of a block of copy + a button, like:
What do you think @emileighoutlaw ?