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

Link docket authorities to search results #4134

Closed
mlissner opened this issue Jun 25, 2024 · 11 comments · Fixed by #4854
Closed

Link docket authorities to search results #4134

mlissner opened this issue Jun 25, 2024 · 11 comments · Fixed by #4854
Assignees

Comments

@mlissner
Copy link
Member

When you're looking at the authorities page for a docket, it shows you all the case law that has been cited in the case so far:

image

That's cool, but it leaves a big question unanswered: Which documents are making the citations to those cases?

For example, in the screenshot above, we learn that U.S. v. Arthur Young has been cited six times. But which documents do that?

Well, that case has an ID of 111119, so we can actually check using the search engine with a query like:

docket_id:63337698 cites:111119

That reveals:

image

Cool!

So there is an easy way to fix this. Just make the word "references" into a link to the search results, so it looks like:

image

And the link goes to the search results.

One gotcha: The citations are to opinions, not clusters, but the authorities page shows clusters. The way to solve this is to make the link use the opinion IDs, not the cluster IDs, and to be sure to include all of the sub-opinions for the cluster in an OR query. For example, cluster 123 might have sub-opinion 345 and 456. You might think that the query should be docket:whatever cites:123, but that'd be wrong. The correct query is docket:whatever cites:(345 OR 456). We do this elsewhere too.

@mlissner mlissner moved this to Main Backlog in @erosendo's backlog Jun 25, 2024
@mlissner mlissner moved this to CourtListener Backlog in Volunteer backlog Jun 25, 2024
@mlissner mlissner moved this from Main Backlog to CourtListener Backlog in @erosendo's backlog Aug 1, 2024
@mlissner mlissner moved this from CourtListener Backlog to Main Backlog in @erosendo's backlog Aug 1, 2024
@mlissner mlissner moved this from Main Backlog to CourtListener Backlog in @erosendo's backlog Aug 1, 2024
@mlissner mlissner moved this from CourtListener Backlog to Main Backlog in @erosendo's backlog Aug 1, 2024
@mlissner mlissner moved this from Main Backlog to CourtListener Backlog in @erosendo's backlog Aug 1, 2024
@mlissner mlissner moved this from CourtListener Backlog to Main Backlog in @erosendo's backlog Aug 1, 2024
@s-taube s-taube moved this to To Do in Sprint (Web Team) Nov 5, 2024
@mlissner mlissner moved this from Backlog Nov 25 - Dec 6 ( 💀 ➡️ ☀️ ) to Backlog Dec 9 - Dec 20 (🔔) in Sprint (Web Team) Dec 6, 2024
@s-taube s-taube moved this from Backlog Dec 9 - Dec 20 (💅) to To Do in Sprint (Web Team) Dec 9, 2024
@tactipus
Copy link
Contributor

Hi guys! I want to help on this issue!

@mlissner
Copy link
Member Author

Lovely, it's yours, @tactipus! It's on our sprint that ends this week, but if you think you can take it on, we'll hold off and leave it to you. @elisa-a-v is assigned here and would be the natural person to help guide you if you need help getting set up.

@tactipus
Copy link
Contributor

tactipus commented Dec 18, 2024

I'm sorry, but I just re-read this message. I didn't realize you were on a sprint for this, & I was looking at the code more deeply since my last message & i would not be fast enough to finish it this week. I think i'll just follow along for now. my apologies!

@elisa-a-v
Copy link
Contributor

elisa-a-v commented Dec 20, 2024

@tactipus I plan on looking into this later today, if you're available we might be able to do some pair programming, which I know is not everyone's cup of tea but I personally love it so let me know, that way you can still contribute without so much pressure :)

oh and thank you for reaching out regardless! 🙌🏽

@tactipus
Copy link
Contributor

@elisa-a-v i'd love to, but today's no good :/

@elisa-a-v elisa-a-v moved this from To Do to In progress in Sprint (Web Team) Dec 23, 2024
@elisa-a-v elisa-a-v moved this from In progress to In review in Sprint (Web Team) Dec 23, 2024
@github-project-automation github-project-automation bot moved this from In review to Done in Sprint (Web Team) Dec 24, 2024
@mlissner
Copy link
Member Author

Hm, I'm a bit confused as I play with this because the numbers don't line up. For example, on this docket, it says that there are " 22 references to Rodriguez v. West Publishing Corp., 563 F.3d 948 (9th Cir. 2009)":

https://www.courtlistener.com/docket/4214664/authorities/national-veterans-legal-services-program-v-united-states/

But when I click the new link:

https://www.courtlistener.com/?type=r&q=docket_id%3A4214664%20AND%20cites%3A(1264596)

I get:

Image

I would have expected 1 docket with 22 documents.

Is this because that one document has 22 references to Rodriguez?

@mlissner mlissner reopened this Dec 24, 2024
@mlissner mlissner moved this from Done to In progress in Sprint (Web Team) Dec 24, 2024
@tactipus
Copy link
Contributor

tactipus commented Dec 27, 2024

Nvm

@ERosendo
Copy link
Contributor

Is this because that one document has 22 references to Rodriguez?

@mlissner This seems right! A manual check reveals 22 occurrences of the string "563 F.3d 948" within the text of the document.

Image

@tactipus
Copy link
Contributor

tactipus commented Dec 27, 2024

Ahhh crap I wish I hadn't edited my comment. It should also be more clear in the DOM that the references are scattered throughout the documents. There can be a number that tells the user the number of citations each user has.

I'm open to pair programming!

imageimage

@mlissner
Copy link
Member Author

OK, there are two possible solutions:

  1. Fix the authorities page to say "22 reference from 1 document cite..." and then make "1 document" into the link.

    I don't know if we can easily get this from the data we have.

  2. Update the search results to display the depth of treatment when a cites query is made, so that each result shown says something like, "22 references to case XYZ".

    I think we do that (or used to do that?) elsewhere in the search results, but I can't trigger it now.

Anyhow, @elisa-a-v, can you please make an issue with these two approaches, and we'll get the scheduled for a later sprint?

@mlissner mlissner moved this from In progress to Done in Sprint (Web Team) Dec 27, 2024
@mlissner mlissner closed this as completed by moving to Done in Sprint (Web Team) Dec 27, 2024
@elisa-a-v
Copy link
Contributor

I opened the issue, and I looked a little bit into this so I added my findings there :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants