search

freelawproject / recap

This repository is for filing issues on any RECAP-related effort.
https://free.law/recap/
12 stars 4 forks source link

RECAP should have a way to rescan a page #273

Closed johnhawkinson closed 1 year ago

johnhawkinson commented 5 years ago

I often find myself on a docket report that I know is not up to date with respect to [R] tags (e.g. because documents were uploaded prior to my running the docket report). There should be a UI mechanism (e.g. button in the toolbutton menu) to rescan the current page and update the [R] tags.

Although sometimes I can follow a link and then Back, it's always a bit fraught with what actions will trigger a POST and thus more charges.

mlissner commented 5 years ago

because documents were uploaded prior to my running the docket report

That shouldn't be solvable by a re-scan at this point. When dockets are uploaded, we already check if there are any orphan documents that can be associated with the new HTML.

I'm not sure a button as you describe it would do anything, tbh.

johnhawkinson commented 5 years ago

Sure it would. Chronology:

  1. Documents are uploaded without corresponding dockets. They sit around in the queue unprocessed.
  2. I run a docket report. It displays on my screen, the extension queries the server for available documents, and it uploads the docket report to the server, all simultaneously. At the point at which it queries the server, the server has not yet processed the new docket report.
  3. A few milliseconds (optimistically) to hours (something is busted), the server processes the uploaded docket report and finds the ophaned documents.
  4. At this point, a docket report that is run will show such documents. Or, if I click on a document and get the billing page (or not, I guess) and click Back, the extension will re-query the server and show the newly available documents. It is this reliance on browser caching I wish to escape.
mlissner commented 5 years ago

Ah! This button would go on the PACER docket, not the CourtListener one. I didn't get that. Yeah, that could certainly do something like you describe, thanks.

I'm +1 on this. I want to add other buttons too:

jraller commented 5 years ago

Instead of a single button would it be ok to have a single recap button with a down arrow that expands to offer all of those options, and in the options.html page add an option to change which is the default shown?

mlissner commented 5 years ago

Sure, I'm flexible on implementation, though I don't thing an option is warranted.

johnhawkinson commented 5 years ago

My expectation was this would all go in the existing options.html page that appears when you hit the button. I do not think it would be OK to have more than one button.

mlissner commented 5 years ago

I do not think it would be OK to have more than one button.

Extensions don't let you have more than one button in the browser chrome. I'm imagining this as an action button in the PACER HTML itself on the docket page (and probably in a few other places too).

johnhawkinson commented 5 years ago

that might also be acceptable, but I am kinda wary of going down that path. not sure i can clearly articulate why right now... Also it's a bit too prominent for the expected frequency of use...

--jhawk

On Sun, Apr 28, 2019, 17:58 Mike Lissner notifications@github.com wrote:

I do not think it would be OK to have more than one button.

Extensions don't let you have more than one button in the browser Chrome. I'm imagining this as an action button in the PACER HTML itself on the docket page (and probably in a few other places too).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/freelawproject/recap/issues/273#issuecomment-487419078, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJWHPUIHB5BUT6QFKT25ZLPSYMZDANCNFSM4HI4FWGA .

mlissner commented 5 years ago

Prominence seems fine by me. Even if it's the only thing on the page, I could see people pressing it over and over in popular cases while they wait for somebody else to upload an item.

It's no more prominent than the HTML we inject already, like on the reports page, where we put our link to get the docket.

johnhawkinson commented 5 years ago

the appropriateness of prominence is a function of utility (incl freq of use)

--jhawk (mobile)

On Sun, Apr 28, 2019, 18:32 Mike Lissner notifications@github.com wrote:

Prominence seems fine by me. Even if it's the only thing on the page, I could see people pressing it over and over in popular cases while they wait for somebody else to upload an item.

It's no more prominent than the HTML we inject already, like on the reports page, where we put our link to get the docket.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/freelawproject/recap/issues/273#issuecomment-487421098, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJWHPWQLNUYW4X2RIV2BULPSYQYNANCNFSM4HI4FWGA .

mlissner commented 5 years ago

Agree. I don't think we have anywhere else to put such a button, however.

mlissner commented 1 year ago

I've consolidated this into #308.

mlissner commented 1 year ago

Thanks for the suggestion, John. This is now implemented via https://github.com/freelawproject/recap-chrome/pull/282, and will be in the next version of RECAP.