https://fec-eregs.apps.cloud.gov/100-19/2015-annual-100#100-19-a

"file," filed" and "filing" are italicized in the print version of 11 CFR

Would it be useful to include the 11 CFR Index to the e-regs (by link or otherwise) - some people are more comfortable with that than with coming up with specific search terms. Suggest having Ed's 18F UX team discover user thoughts on the issue.

The effective date for all parts seems to be 2/22/2016. This is incorrect.

Currently we display the combined search page which only displays the top 10 results.

Let's implement the next page where the user has clicked on display all results for AOs.

I'd like to assess the ease of use and comprehension of two versions of the Advisory Opinion canonical page, a basic version and one with the addition of a summary from the FEC Record newsletter.

Required activities:

• Create test materials
• Run test
• Post conclusions here

Test materials

Task: Advisory Opinion pages

Version 1 link: https://gsa.invisionapp.com/share/9Q710V45R#/screens/152290010
Version 2 link: https://gsa.invisionapp.com/share/9Q710V45R#/screens/152290007

Script:

Version 1

• (Go to link 1)
• What is this page about?
• What is this Advisory Opinion about?
• Where can you go from here?

Version 2

• (Go to link 2)
• What is different now?
• What is this Advisory Opinion about?

Clicking on some linked definitions pulls up a window that says that the definition is "best viewed in original location" -- how it is determined which definitions produce this statement?

Stories that are coming out of our retrospective feedback

Part 6: Because each individual section is separately labeled "reserved" (instead of grouped together), the Part is hard to navigate, and the TOC scrolling bar is so small that it disappears behind the TOC header.

Given aches and pains of folks deploying fec-eregs; we need to have light weight documentation for devs to be able to follow.

These should be added as part of or a link to the readme for this repo.

Update the styles for the legal/all sources search results pages according to @jenniferthibault's 18F/fec-style#318 (comment) guidance.

(taken from the comment referenced above)

This is the sibling issue to @jenniferthibault's issue on openFEC-web-app for data: fecgov/openFEC-web-app#1202

Put together a plan for how to learn from user interactions via Google Analytics.

Some subsection designations are hidden behind the text of the subsection title (e.g., 114.4(b)(1), 114.4(c)(3)(i), 114.4(c)(7)(i)).

The content area below the hero can be prepared and integrated into the site. Initial testing showed people able to navigate the area and it closely follows patterns established elsewhere.

@emileighoutlaw We should talk about content needs, which are pretty basic here.

For sections not ready, we should fade/deactivate them.

cc @Porta @adborden

Lets discuss this during planning.

In the next few sprints, we want to have eregs visible from beta.fec.gov so that
a) we will be able to release it to the public
b) we are able to search across eregs and other legal resources

To the untrained user, it should feel as if they are just viewing beta.fec.

However, currently eregs is a separate stack of assets from a separate instance of elastic search backend to a separate app. Integrating this into beta.fec is not a trivial task.

Does it make sense for us to design spike the way we will merge the two? Or do we start the work (but need guidance on how to split it up into manageable stories)

Things to keep in mind

• eregs search vs. integrated search : do we keep both or just support integrated search?
  • if we just support integrated search, will that preclude us from supporting historical diff searches in the future.
• iFrame?
• Keep separate backends
• etc etc

Testing to see what happens in trello when i open an issue.

Epic for getting eregs on beta.fec

https://fec-eregs.apps.cloud.gov/100-14/2015-annual-100#100-14

Compare "B" to "C"

Subsections are designated throughout by the subsection letter/number followed by a period -- CFR convention is to put the letter/number within parens. Similarly, on the main TOC, the Title is labeled "Title XI" -- that should be "Title 11" per CFR convention.

Testing to see if Trello integration works.

Some definitions aren't really definitions (e.g., in 100.22(b), "defeat" is linked to 100.22(a), which doesn't define that term).

See #10

Currently, we are linking to the PDFs hosted on fec.gov. We should port the AOs into cloud.gov and update links in elasticsearch:

• Get binary data out of Oracle into file
• Add S3 write API (/load/legalfile/)
• Write shipper code to post file to /load/legalfile/

We have presented several mockups in our demos and used the feedback there to implement code.
Now that we have a healthy user experience designed, we want to get into a cadence of performing usability testing to validate the designs before implementing.

In this sprint we want to test:

• Browsing
• AO canonical landing page

@porta-antiporta follow up from Slack, we haven't found any missing parts but there are parts in eRegulations that are not FEC regulations. Parts 9405 to 9430 are EAC regulations. We should not include them in our eRegulations platform.

@AmyKort

Upon running the 18F/regulations-parser on FEC regulations (title 11), there were 50 regulations that parsed properly (at least, completed parsing- have not manually verified accuracy), and 3 that failed. This issue may be closed once all 53 regulations can be parsed.

https://fec-eregs.apps.cloud.gov/100-19/2015-annual-100#100-19-a

"Document," "election," "commission" and "states" are linked as defined terms but these are not definitions we want.

The box in the upper left that takes you back to the overall TOC isn't very intuitive.

@edmullen I believe this is the behavior you're going for, please correct me if I'm wrong.

On the front end, we'll limit the number of hits displayed, and then "Display all hits" will expand to include all the snippets found. Currently the snippets are too short to be displayed on their own but #75 allows us to have longer snippet text.

I'd like to get initial thoughts on the advisory opinion landing page.

Required activities:

• Create test materials
• Run test
• Post conclusions here

Test materials

Task: Look at this page and talk about what you can do here.

[Note: I'm interested in getting some pretty basic initial responses to the page as currently designed, including what the subject matter is and what actions a person can take from the page.]

Link: https://invis.io/9Q710V45R#/152290006_AOs_Landing

Script:

• Are you familiar with Advisory Opinions?
  • (If no, read this) An Advisory Opinion is when a campaign or committee asks the FEC to determine if something they are interested in doing is legal. Once the FEC decides, other campaigns and committees look at the Advisory Opinion as guidance.
• I'd like to have you take a look at a page and tell me about it. You'll notice some of the content is placeholder text, but I'd like to hear what you think the text would be about.
• Load page
• Talk me through this page. What is it? What do you see? What can you do?
• If you wanted to find an advisory opinion about, say, "filing", can yo do that?
• (If they haven't talked about the left column...) What's going on in that gray column on the left?

The Legal landing page will need content created for the two sections that will be present in the near future, Advisory Opinions and Regulations, and coming text for the Enforcement matters. It also could probably use some adjustment to the hero language.

The dev page is here. It will be updated as part of #68

cc @emileighoutlaw @porta-antiporta

Currently functionality to support regulation timelines is not supported. We have both bugs that need to be resolved as well as missing Federal Register data required to support that functionality. Due to a prioritization discussion, we want to hide that functionality in the fec-eregs instance.

I can also see this being a flag that we may want to enabled/disable on core as there are other agencies that may have the same problem (validate with #eregs)

We need to:

• Hide the regulations timeline icon
• Hide the effective date in the top bar
• HIde the "Regulation Effective" date field on the search menu

100.2 (d)d. Runoff election. Runoff election means the election which meets either of the following conditions:

https://fec-eregs.apps.cloud.gov/100-2/2015-annual-100#100-2-d

Some of the linked definitions don't accurately reflect the term as used in context (e.g., in 1.1(b), "Act" is linked to the definition of FECA, even where the word is used in term "Privacy Act"; in 100.1, "Election" and "Commission" are individually linked even when used within the phrases "Federal Election Commission" and "Federal Election Campaign Act")

https://fec-eregs.apps.cloud.gov/100-5/2015-annual-100#100-5-d

• Team calls out any perceived delays
• Mid sprint check up

As part of https://github.com/18F/openFEC/issues/1623 the API now supports enhanced fucntionality that can be reflected in the UI.

Notably:

• Confirm that ranking is now using default proximity search
• Update snippets using data returned
• Update UI to display total number of results in (10 of X)
• Update links of individual documents to bring up the .pdf

How does it get updated? E.g., if we modify a reg, how do the new text and history get into the e-regs site?

Is it possible to link USC cites?

The canonical page for an advisory page is ready for development. The information was generally understood as straight forward in initial testing and I think it's fairly non-controversial.

Citations: The mock-up below includes citations on the right, which I do not believe are available. I think we could include the box with grayed-out "Coming" text.

Audio: the mock-up below includes a link to the audio from the hearing. This is not ready and should not be included yet.

Please note that this version does not include the FEC Record summary. That would be an enhancement in the future, so please be aware of it, but don't built it yet. Here's is the current placement of that potential future content:

CC @porta-antiporta @adborden

To support MURs, we want to include current and archived MURs in our search. Archived MURs are part of a separate story. This story focuses on loading current MURs into elastic search.

Assumptions

• FEC has loaded MURs up in Postgres

Tasks

• Enhance the API developed in #220 to include current MURs (should be same API for current and archived)
• Load MURs into S3
• Index MURs in Elastic search
• Set up celery tasks to ensure freshness and consistency across our environments
• Create tests

Mockup
https://gsa.invisionapp.com/share/AR7U3Y662

• Enhance API to load data
• Load remaining AOs
• Paging
• Putting in AO Ids should give AO as first hit
• Snippets
• Proximity search
• Include total result count

Is there a way to pull up a specific reg by going straight to it (instead of by clicking through the TOC)

If possible, let's configure the legal search snippet text length to be longer. Ideally added as a query parameter to the API so we can play with it.

The current snippet text is too short. We're including all the hits concatenated together, joined with ellipsis. This is misleading because it looks like the text is related but in fact these snippets could be pages apart in the document.

cc @edmullen

Move to fec-shipper:

• - Get Oracle running on MacOS. I'm over the Oracle VM.
• - Connect to Oracle with pyodbc
• - Decide on maintainable solution for code execution
• - Implement AO shipping code in fec-shipper repo