Sub-epic: MUR search

[JonellaCulmer]

What we're after: As a developer, I want to be able to upgrade the legal web search application so that I can create useful functionality and confidently build upon our legal web application.

Completion criteria

• [ ] Conducted research and built prototypes to utilize the elasticsearch DSL.
• [ ] Made upgrades to the legal web search app

Redesigned MUR search

Tickets

• [ ] fecgov/fec-cms#5257
• [ ] fecgov/fec-cms#5262
• [ ] fecgov/fec-cms#5263
• [x] fecgov/fec-cms#5264
• [ ] fecgov/fec-cms#5265
• [x] fecgov/openFEC#5153
• [x] fecgov/openFEC#5155
• [x] fecgov/openFEC#5156
• [x] fecgov/fec-cms#5261
• [x] fecgov/openFEC#5152
• [x] fecgov/openFEC#5121
• [x] fecgov/fec-cms#5423
• [x] fecgov/fec-cms#5357
• [x] fecgov/fec-cms#5258
• [x] fecgov/fec-cms#5255
• [x] fecgov/fec-cms#5256
• [x] fecgov/openFEC#5119

[patphongs]

@JonellaCulmer Can you explain what is expected in the "Disposition" field of the search results?

This is an example API call based on the search term "filings" and dispositions is a list of multiple dispositions, which we can group together. So if we use the first MUR in the list as an example, 7958, do you expect dispositions to look like this:

Dispositions: Conciliation-PPC (1 respondent); Dismissed-Other (9 respondents)

[JonellaCulmer]

@patphongs Yes, exactly what I had imagined. If we're able to calculate a count similar to the number of results for the keyword search. If you'd like me to open a separate ticket, I can do that and add it to a future sprint. PI 19?