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

Add a variety of optional enhancements to PACER #207

Closed
1 task
mlissner opened this issue Nov 15, 2017 · 6 comments
Closed
1 task

Add a variety of optional enhancements to PACER #207

mlissner opened this issue Nov 15, 2017 · 6 comments

Comments

@mlissner
Copy link
Member

This is a follow on from #191.

The idea here is to add another checkbox to the options that just says something like:

  • Optimize PACER (learn more)

By default it could be off, but when enabled, it'd make little changes that make PACER more palatable:

  1. Uncheck Parties and Counsel from the docket report page.
  2. Check "Include headers" on the docket report page.
  3. Check "List of member cases" on the docket report page.

What else? I imagine there's a lot more we could do here.

@johnhawkinson
Copy link
Collaborator

As expressed in #191, I don't think this is a great way to go.

First and foremost, it's not self-documenting. An option like "Uncheck Parties and Counsel box" is fairly clear and unambiguous. It doesn't need a "learn more" link and the extra baggage that brings. It's narrow and surgical. But "Optimize PACER" is nearly meaningless, as you've recognized with the "learn more" link. That's an extra click to understand, an extra click most users will never try. Single-page UIs are generally better than multi-page UIs unless there is so much information it doesn't comfortably fit (we are nowhere close).

Secondly, a broad option is future-ambiguous, and that's bad. If I check it now, the definition of "Optimize PACER" may change in the future. That's kind of like an opt-out system without clear notice of the opt-out choice, and those systems are generally disfavored by users but liked by system developers (because fewer people will make conscious choices so they get higher adoption rates).

Thirdly, I don't think it's apparent that user desires all track each other on these. I mean, you can say, sure, "Who wouldn't want Include headers"? and I think a lot of districts check it by default? I dunno about "List member cases" -- does that add to the page count and result in more $0.10 charges?

Anyhow, just my opinion as a PACER user.

@mlissner
Copy link
Member Author

Definitely appreciate it, John. I actually see the future-ambiguity as a feature. I see this feature as an escape valve that people can use to tell us they aren't sticklers.

@johnhawkinson
Copy link
Collaborator

johnhawkinson commented Nov 15, 2017

"generally disfavored by users but liked by system developers "

:)

@johnhawkinson
Copy link
Collaborator

What else? I imagine there's a lot more we could do here.

  1. Fill in the last docket number or date thereof in the date_from or document_numbered_from fields, in order to limit the report to only what is new.

Problems:

(a) What if RECAP had partial information, e.g. it had docs 101-102, but not 1-100?
(b) Some courts (EDNY, for example) don't display unnumbered documents when you set document_numbered_from. This is irritating and creepy and maybe even a bug?
(c) Even the people who want this probably do not want it all the time. Thereofre there should be a button added to the page to do these functions (and maybe submit the form? Or maybe not.)

@johnhawkinson
Copy link
Collaborator

Oops, I guess I mentioned the 4(c) button idea in #190.

@mlissner
Copy link
Member Author

mlissner commented Nov 2, 2022

Eh, I'm not seeing anything here being worth doing. Closing.

@mlissner mlissner closed this as completed Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants