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

Sub-epic: MUR search #221

Open
13 of 19 tasks
Tracked by #139
JonellaCulmer opened this issue Apr 28, 2022 · 2 comments
Open
13 of 19 tasks
Tracked by #139

Sub-epic: MUR search #221

JonellaCulmer opened this issue Apr 28, 2022 · 2 comments

Comments

@JonellaCulmer
Copy link

JonellaCulmer commented Apr 28, 2022

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

MUR-Document with lines

Tickets

@patphongs
Copy link
Member

@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
Copy link
Author

@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?

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

3 participants