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

The extension uploads Case Summaries using the wrong pacer_case_id #330

Closed
ERosendo opened this issue Jan 26, 2023 · 0 comments · Fixed by freelawproject/recap-chrome#315
Assignees

Comments

@ERosendo
Copy link

ERosendo commented Jan 26, 2023

I reviewed the dockets that @albertisfu mentioned here and realized that the issue is related to one of the approaches the extension uses to get the pacer_case_id before uploading the HTML page.

STR (using version 2.0):

  1. Go here while logged in.

  2. Search for the case '21-2172'

  3. Click on Case No. to get Case Summary

  4. Copy the following link:

    https://ecf.cafc.uscourts.gov/n/beam/servlet/TransportRoom?servlet=CaseSummary.jsp&caseNum=23-1210&incOrigDkt=Y&incDktEntries=Y
    
  5. Go back to the tab where the case '21-2172' is opened

  6. Paste the link you just copied into the address bar and press enter

  7. Accept charges and retrieve the docket

Here's a gif following the STR:

upload-wrong-case-id

Problem

The current implementation of the extension uses different approaches to get the pacer_case_id from an appellate page (here's the helper method) and it saves it to the tab storage when It's able to find it, so we can use it on another page that does not have it (like the Case Summary). In this case, the extension was able to find a case_id when we searched for case '21-2172' (step 2), It saved it in the tab storage and then used it to upload the case summary page (step 3).

After we accepted the charges and loaded a new docket in the same tab (step 7), the extension tried to get the case_id from the new Case Summary, checked the tab storage after failing to retrieve it from the HTML or the page URL, found the case_id that was saved in step 2 and uploaded the page using the wrong case_id.

Possible Solution

We should store more information related to the pacer_case_id ( like the docket number and the court id) in the tab storage, so we can add checks like the following:

  // check the docket number before using the pacer_case_id that's saved in the storage
  if (docketNumber == tabStorage.docketNumber) {
    pacer_case_id = tabStorage.caseId;
  }
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant