Git Product home page Git Product logo

recap's Introduction

Reporting Issues

This repository is a centralized place for filing issues on any RECAP-related effort. When you file an issue, please search to make sure no one else has already reported that issue. If you open a new issue, please use labels to indicate which component(s) are affected (firefox, chrome, affects all browsers, server, etc.) and whether you are reporting a "bug" or requesting an "enhancement."

Contributing

If you'd like to help with development work, here's a brief overview:

All current work is happening in the recap-chrome repository, which is cross-compatible with Firefox and Chrome.

The following repositories are now archived or otherwise obsolete:

  • recap-firefox (deprecated in favor of recap-chrome, which is now cross-compatible with Firefox)
  • recap-ie (Never completed experimental version for Internet Explorer; Now archived)
  • recap-server (deprecated, code is being migrated to CourtListener)
  • recap-openforge (Experimental cross-compatible version before WebExtensions were supported in all browsers, now archived)
  • recap-extension-2.0 (Experimental upgrade of RECAP Chrome. Never completed, now obsolete.)

Contact Us

You can reach us on Twitter at @RECAPtheLaw.

recap's People

Contributors

audiodude avatar devd avatar divergentdave avatar dkapadia avatar filosottile avatar harlanyu avatar janderse avatar martey avatar mlissner avatar semenko avatar sjschultze avatar yinglei avatar zestyping avatar ziorufus avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

recap's Issues

Idea for capturing "free look" documents: email forward gateway

Issue by sjschultze
Tuesday Jun 11, 2013 at 18:00 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/33


We've talked about capturing "free look" documents. It's been hard to figure out how to get the appropriate metadata. What if we offered an email address to which you could forward all of your "free look" emails? When an email is received, we parse the email text in order to get the metadata, download the doc and ingest it into the system, and send an email to the original sender with their new free and pubic download link?

We would have to address privacy concerns (including data retention) and appropriately disclaim them up front. Anybody want to take the lead on implementing this?

Appellate file renaming not working in ca3?

Issue by johnhawkinson
Tuesday Aug 06, 2013 at 16:23 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/38


In USA v. Auernheimer (weev) 13-1816 at ca3, i.e. http://ia601700.us.archive.org/17/items/gov.uscourts.ca3.13-1816/gov.uscourts.ca3.13-1816.docket.html, I just tried to download documnet 003011347514 0 ECF FILER: Response filed by Appellant Andrew Auernheimer to Motion to Accept Noncompliant filing, Motion stay request. Certificate of Service dated 08/05/2013. (HMF) from yesterday.

I ended up with ca3-Tra0sportRoom?servlet=ShowDoc&dls_id=003011347514&caseId=87236&dktType=dktPublic.pdf in my filesystem, and I don't know if anything was successfully uploaded to archive.org (looks like not), though docket metadata made it (unsurprisingly). debugging output was not fatal-looking:

8/6/13 12:18:07.546 PM [0x0-0x17e77e6].org.mozilla.firefox: RECAP: Url: /cmecf/servlet/TransportRoom?servlet=ShowDoc&dls_id=003011347514&caseId=87236&dktType=dktPublic
8/6/13 12:18:07.546 PM [0x0-0x17e77e6].org.mozilla.firefox: RECAP: Name: 003011347514.pdf
8/6/13 12:18:07.546 PM [0x0-0x17e77e6].org.mozilla.firefox: RECAP: List of stuff:
...
8/6/13 12:18:12.243 PM [0x0-0x17e77e6].org.mozilla.firefox: RECAP: Posting file: 003011347514.pdf
8/6/13 12:18:21.506 PM [0x0-0x17e77e6].org.mozilla.firefox: RECAP: RECAP File Upload - PDF uploaded to the public archive.
8/6/13 12:18:21.509 PM [0x0-0x17e77e6].org.mozilla.firefox: RECAP: [object Object]

Multi-defendant criminal case confusion / split destinations

Issue by johnhawkinson
Thursday Jun 20, 2013 at 11:09 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/36


USA v. Weeks, et al, in ecf.mad, case 99-10371, has multiple defendants, and CM/ECF lets you select which ones when running a docket report, including All.

Apparently if you select All, or select James Bulger, RECAP documents end up in different places. So if one is looking for a James "Whitey" Bulger document, it could be in either of:

http://ia600609.us.archive.org/33/items/gov.uscourts.mad.71378/
http://ia600602.us.archive.org/2/items/gov.uscourts.mad.71381/

And, of course, if one was looking for any of the other defendants (unlikely in this case, but surely in another), there might be 5 or 6 different places to look. And depending on how the query was run, the RECAP 'R' logo would not appear.

This is kind of a problem. Not sure what to do about it. Add some kind of aliasing support to the recap server? Though...that doesn't help people who have bookmarked the archive.org URLs.

Integrate fixes

Issue by janderse
Thursday Apr 11, 2013 at 00:33 GMT
Originally opened as freelawproject/recap-server#25


To integrate:

  • Update ParsePacer.py to handle relative links.
  • Remove unused commented lines from ParsePacer.py as requested by Dhruv
  • Fix unit tests and breakage from removing secrets
  • Split up alltests.py into separate unit test files.
  • Parse dockets where parties are spread across multiple tables

janderse included the following code: https://github.com/freelawproject/recap-server/pull/25/commits

[CLOSED] Parties incorrectly parsed in Swartz, others.

Issue by johnhawkinson
Saturday Apr 13, 2013 at 14:08 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/26


There's some irony in reporting bugs in RECAP's handling of United States v. Swartz.

The parties section of http://ia700504.us.archive.org/29/items/gov.uscourts.mad.137971/gov.uscourts.mad.137971.docket.html misses several of the parties. It shows the 6 attorneys representing the defendant (Swartz). But it does not show the 3 attorneys representing the Plaintiff (USA), nor the 2+1 attorneys representing 2 intervenors.

I think this is a longstanding breakage; sorry for not reporting it earlier.

Here's the HTML saved by Firefox from PACER: https://gist.github.com/5378539

[CLOSED] Appellate docket parser ignores non-documents

Issue by johnhawkinson
Wednesday Apr 03, 2013 at 04:25 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/22


The docket report should include all docket items, not just PDF documents.
Did a query for all docket events from 1/1/2013 on
http://ia601701.us.archive.org/17/items/gov.uscourts.ca2.12-3200/gov.uscourts.ca2.12-3200.docket.html

and got back the HTML here:
http://pastebin.com/RiEMD8aP

Which included:
03/11/2013 148 CASE CALENDARING, for the week of 05/06/2013, PROPOSED.[871308] [12-3200]

e.g.
Screen shot 2013-04-03 at 12 24 38 AM

but the docket.html from archive.org skips from 146 to 150.

MASSIVE mess in the Malibu Media Dockets

Issue by simality
Tuesday Oct 08, 2013 at 03:13 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/41


Malibu Media is a copyright troll responsible for a massive amount of ongoing litigation. This litigation is not recapping correctly. There are documents that PACER has down as being recapped that RECAP has no record of. There are RECAP dockets longer than their associated cases. There are RECAP dockets with documents for multiple cases.

Its a huge mess.

I've seen everything that I described above but it wasn't until a few minutes ago that I started documenting it for a bug report. Therefore I only have proof of my first claim and my last claim.

Proof:
Docket number 8-13-00506 as it looks on PACER (this is the history page)
http://www.scribd.com/doc/174335122/8-13-00506-aw-PACER.
Docket number 8-13-00506 as it appears on the Internet Archive.
http://www.scribd.com/doc/174336689/8-13-00506-aw-RECAP

As you can see, the PACER version of the docket has quite a few more recapped documents than recap itself.

And that's all the bug I have energy to document....

Goodnight.

Full appellate docket not parsed, only initial preview

Issue by johnhawkinson
Wednesday Apr 03, 2013 at 03:46 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/21


http://ia601702.us.archive.org/7/items/gov.uscourts.ca1.11-1805/gov.uscourts.ca1.11-1805.docket.html

is Redfern et al v. Napolitano, being argued before the First Circuit tomorrow morning (2 Harvard Law students sued the TSA in re their full body scanners).

Appellate ECF gives me the last 10 docket entries first, then a button to see the full docket. Having done both, the archive.org docket shows me only the last 10, but fills in the first N with blanks/zeroes.
So it looks like the materials were misparsed on upload?

I haven't done any debugging. RECAP 0.9.1in Firefox.

[CLOSED] Things are all kind of broken?

Issue by johnhawkinson
Tuesday Apr 15, 2014 at 00:28 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/44


I feel like RECAP has been busted for me for a while.
I haven't had a chance to sit down and debug it.
Firefox 28.

But, say, retrieving recent entries in http://ia600503.us.archive.org/2/items/gov.uscourts.nyed.308557/gov.uscourts.nyed.308557.docket.html gives my nyed-NNNNNNN.pdf -type filenames, and the docket doesn't get uploaded, etc., etc.

Hrmm, I see someone manged to upload a file on 4/2, so maybe it's mostly just me. I dunno.

[CLOSED] Error message "query: too many url args" is wrong

Issue by zestyping
Saturday Jan 26, 2013 at 21:50 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/3


The server reports "query: too many url args" whenever the "json" parameter has a value that is not valid JSON syntax. This has nothing to do with how long the parameter is or how many URLs are specified; it should be reported as a JSON parsing error.

To reproduce this problem:

% curl -d json=abc http://dev.recapextension.org/recap/query/
query: too many url args

[CLOSED] Appellate Parser Should Capture Useful Metadata

Issue by thinkcomp
Tuesday Apr 02, 2013 at 04:24 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/14


At the top of the "General Docket" page for a case (also known as TransportRoom?servlet=CaseSummary.jsp) I see things like:

Court of Appeals Docket #: 12-73415 Docketed: 10/23/2012
Harwinder Sing-Grewal v. Eric Holder, Jr.
Appeal From: Board of Immigration Appeals
Fee Status: IFP
Case Type Information:
1) agency
2) review
3) San Francisco Northern Ca
Originating Court Information:
District: BIA-1 : A089-474-561
Date Filed: 10/23/2012
Date Rec'd COA:
10/23/2012

Can we capture all of this? Lots more useful information here.

[CLOSED] CAND's 3:13-cv-00815-SC doesn't seem to function in RECAP?

Issue by johnhawkinson
Thursday May 09, 2013 at 16:19 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/27


Carl Malmud's case, 3:13-cv-00815-SC Public.Resource.org v. Sheet Metal and Air Conditioning Contractors' National Association, Inc. in ecf.cand.uscourts.gov, doesn't seem to work with RECAP.

Neither the docket nor the files seem to be successfully uploaded.
See https://gist.github.com/johnhawkinson/5548532 for logs.

Doppelganger cases with no available documents (was: "ECF docket number parsed wrong in Swartz")

Issue by johnhawkinson
Monday Jun 10, 2013 at 23:04 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/31


Well, that's a trip. I downloaded docket item #128 today in United States v. Aaron Swartz (ecf.mad's 11-CR-10260), and it came up as

gov.uscourts.mad.137970.128.0.pdf

That is BIZARRE!

It is docket ECF docket # 137971 , not 137970!!

Needless to say, it does not show up at
http://ia600504.us.archive.org/29/items/gov.uscourts.mad.137971/

I'm not sure how this could have happened, but something's horribly wrong...

[CLOSED] Error message "query: too many url args" is wrong

Issue by zestyping
Saturday Jan 26, 2013 at 21:50 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/3


The server reports "query: too many url args" whenever the "json" parameter has a value that is not valid JSON syntax. This has nothing to do with how long the parameter is or how many URLs are specified; it should be reported as a JSON parsing error.

To reproduce this problem:

% curl -d json=abc http://dev.recapextension.org/recap/query/
query: too many url args

appellate character coding error

Issue by johnhawkinson
Friday May 31, 2013 at 22:33 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/30


Perhaps a UTF8 double-conversion botch?
http://ia601709.us.archive.org/6/items/gov.uscourts.ca1.12-1236/gov.uscourts.ca1.12-1236.docket.xml

includes:
document doc_num="00106536535" attachment_num="0"><pacer_doc_id>00106536535</pacer_doc_id><date_filed>05/31/2013</date_filed><long_desc>OPINION issued by Juan R. Torruella, Appellate Judge; Michael Boudin, Appellate Judge and Rogeriee Thompson, Appellate Judge. Published. *Judge Boudin heard oral argument in this matter and participated in the semble, but he did not participate in the issuance of the panel's opinion in this case. The remaining two panelists therefore issued the opinion pursuant to 28 U.S.C. § 46(d). 12-1236</long_desc>

And there is an A-circumflex (Â) after "28 U.S.C. " that should not be there.

Docket report upload to RECAP when following ECF email link silently fails

Issue by joannaskao
Wednesday May 29, 2013 at 18:49 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/29


Uploading a docket report to RECAP after following a link like https://ecf.mad.uscourts.gov/cgi-bin/DktRpt.pl?137970, rather than going through the Query tab and entering a case number in PACER silently fails. I get a notification saying that the report was uploaded to the public archive, but it doesn't actually get uploaded (I went back and reaccessed the page using the Query tab afterward to upload the file I wanted).

Tuppello v. Hamburg docket error

Issue by sjschultze
Friday Apr 05, 2013 at 14:42 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/24


Jhawk sez:

RECAP totally screws up the docket report
for Tuppello v. Hamburg's opening case, 1:05-cv-00366-ERK-VVP in
ecf.nyed; That's the opening docket number for the Plan B / morning
after pill case that took over this morning's news.

Everything's blank at
http://ia600805.us.archive.org/26/items/gov.uscourts.nyed.239933/gov.uscourts.nyed.239933.docket.html

Subdocuments on appellate courts need to be tested further

Issue by sjschultze
Tuesday Jun 11, 2013 at 17:57 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/32


Original issue by Dhruv was on the old recap server repo:
"The behavior isn't consistent and is worth investigating a bit more"

Response from ziorufus was:
"Could you give some example pages that return errors?"

I know that Dhruv is very busy and unlikely to respond in the near future. I'm not sure if there's more testing that can be done even without more comments from him. I too have experienced inconsistent uploading of subdocs on appellate courts, but I haven't documented it well enough to provide a detailed bug report. :(

ca3 weev pdfs show up under gov.uscourts.ca3.None.

Issue by johnhawkinson
Saturday Sep 21, 2013 at 23:32 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/39


weev's ca3 appeal is docket 13-1816. Most but not all documents show up at

http://ia601700.us.archive.org/17/items/gov.uscourts.ca3.13-1816/

but some of them show up at

http://ia601702.us.archive.org/35/items/gov.uscourts.ca3.None/

this is consistent, in that if you run the PACER docket report (this link will charge you money): https://ecf.ca3.uscourts.gov/cmecf/servlet/TransportRoom?servlet=CaseSummary.jsp&caseNum=13-1816&incOrigDkt=N&incDktEntries=Y
then you get some 'R' icon links like this:
http://www.archive.org/download/gov.uscourts.ca3.13-1816/gov.uscourts.ca3.13-1816.003011395511.0.pdf
but some defective ones like this:
http://www.archive.org/download/gov.uscourts.ca3.None/gov.uscourts.ca3.None.003011347514.0.pdf

appellate timestamps in local time not UTC?

Issue by johnhawkinson
Monday Sep 23, 2013 at 22:14 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/40


I'm under the impression that all the RECAP-generated timestamps we see are supposed to be in UTC. See entry No. 3 at http://ia601009.us.archive.org/34/items/gov.uscourts.ca2.13-3524/gov.uscourts.ca2.13-3524.docket.html which I just uploaded:

09/23/2013
3
0
MOTION, to stay, on behalf of Appellant City of New York in 13-3088, 13-3524, FILED. Service date 09/23/2013 by CM/ECF. [1048966] [13-3088, 13-3461, 13-3524]
2013-09-23 18:10:14
0d596c4f601421b1dcad2117fcd09513d6826ce0

That 18:10:14 timestamp is US/Eastern, reflecting the docket report I ran four minutes ago. It should instead be 22:10:14Z.

[CLOSED] In query responses, "timestamp" key is misnamed and in a bad format

Issue by zestyping
Saturday Jan 26, 2013 at 21:56 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/4


Responses to /recap/query include the "timestamp" field. However, this field does not contain a timestamp at all; it contains a date.

Also, the date is in mm/dd/yy format, which is a poor design choice. Two-digit years should have died over a decade ago. Dates transmitted over the wire should be in Unix timestamp (seconds since epoch) or in RFC 3339 format.

Add Vagrant for easy reproducible server dev environment setup

Issue by FiloSottile
Wednesday Apr 03, 2013 at 13:55 GMT
Originally opened as freelawproject/recap-server#23


To start a dev VM do vagrant up
You'll have the RECAP server running on 10.42.42.42:8000
Config: Database recap_dev - User recapper - Pass recap
It will run directly your codebase, and log in your debug.log
Access the output of the server from root's screen via vagrant ssh

I plan to add also a PhpMyAdmin to the mix.


FiloSottile included the following code: https://github.com/freelawproject/recap-server/pull/23/commits

[CLOSED] Appellate casenums need to be coerced and uncoerced consistently

Issue by dkapadia
Saturday Mar 23, 2013 at 20:04 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/9


Appellate cases have casenums of the form YY-NNNN, but our database represents casenums as an int.

We could change the datatype of the column to be a varchar, but since the casenum is predictable, we think it's lower risk to just coerce and uncoerce the casenum in the places where we use it.

Ideally we would abstract this some how so we don't have a ton of 'if appellate' statements littered through the codebase

[CLOSED] In query responses, "timestamp" key is misnamed and in a bad format

Issue by zestyping
Saturday Jan 26, 2013 at 21:56 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/4


Responses to /recap/query include the "timestamp" field. However, this field does not contain a timestamp at all; it contains a date.

Also, the date is in mm/dd/yy format, which is a poor design choice. Two-digit years should have died over a decade ago. Dates transmitted over the wire should be in Unix timestamp (seconds since epoch) or in RFC 3339 format.

ca4 13-4625 docs show up under None?

Issue by johnhawkinson
Friday Nov 08, 2013 at 20:28 GMT
Originally opened as https://github.com/freelawproject/recap-server/issues/42


So, if one looks at the Court's docket for In re: Under Seal (aka Lavabit):

https://ecf.ca4.uscourts.gov/cmecf/servlet/TransportRoom?servlet=CaseSummary.jsp&caseNum=13-4625&incOrigDkt=N&incDktEntries=Y

We see nice [R] icons next to things, including

0/30/2013 47 [RECAP] RESPONSE/ANSWER by Under Seal and Under Seal 2 in 13-4625, 13-4626 to notice requesting response [43[RECAP]]. [13-4625, 13-4626] Jesse Binnall

But that doesn't show up at the archive.org docket:
http://ia601009.us.archive.org/14/items/gov.uscourts.ca4.13-4625/gov.uscourts.ca4.13-4625.docket.html

Inspection of hte [R] icon makes it clear why:

<a class="recapIcon" href="http://www.archive.org/download/gov.uscourts.ca4.None/gov.uscourts.ca4.None.47.0.pdf" onclick="return false;"gt;

gov.uscourts.ca4.None? Oops.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.