vdavez / permafrast

Until I have a better name

👋 I'm Dave Z! My pronouns are he/him, and I'm based out of Oregon, WI.

permafrast's Issues

The site does not work

:'(

Use extension for content type

E.g. .json returns json, no extension returns html etc

Make font responsive to mobile devices

Add XML endpoint

example .json link 403's

Seeing if I can track it down now.

Enable + Force SSL

@konklone, do your thing.

Feature: endpoint for case metadata

This endpoint (or endpoints) could offer:

• the actual text of the case
• a snippet of the text (maybe the first few paragraphs)
• names of the parties
• the holding
• the judges (and their votes)

Some of these might be much more doable than others (e.g. some might require AI...)

Not working :(

I tried a couple of URLs which ought to work. I got the citations from CourtListener.

• LVRC Holdings v. Brekka, 581 F.3d 1127 (9th Cir. 2009) - Tried https://permafrast.herokuapp.com/581/F.3d/1127 and got "Internal Server Error"
• United States v. Nosal, 676 F.3d 854 (9th Cir. 2012) - Tried https://permafrast.herokuapp.com/676/F.3d/854 and also got "Internal Server Error"

Was going to try to use these URLs for https://github.com/anseljh/casebot for the world's hackiest citation lookup bot.

Add Link to Github page to the Readme so it's displayed on homepage

Graceful Errors

The fastcase API gives an error unless the requested page is the first page in the opinion. If the requested page is not the first page, you get the following error:

{

    "GetPublicLinkResult": {
        "Error": null,
        "Success": true,
        "Result": [ ],
        "TotalResults": null
    }

}

http://permafrast.herokuapp.com/558/U.S./311.json

Would be good to have a graceful failure.

Title

Right now, the title of the document is always "Permafrast". Want to change it to be:

<title>Permafrast -- <%= out.full_citation %></title>

Create client-side form

The form would let you enter a volume, reporter, and page. This might be good for a separate project, though.

Cache Travis gems

http://docs.travis-ci.com/user/caching/

You can also explicitly enable it in your .travis.yml:
language: ruby
cache: bundler

http://docs.travis-ci.com/user/caching/#Fetching-and-storing-caches

Fetching and storing caches #

We fetch the repo's cache on every build, including feature branches and pull requests.
There is one cache per branch and language version/compiler version/JDK version/Gemfile location/etc.
If a branch does not have its own cache yet, it will fetch the master branch cache.
Only modifications made to the cached directories from normal pushes are stored.
Currently Pull Requests will use the cache of the branch they are supposed to be merged into.

Clearing Caches #

Sometimes you spoil your cache by storing bad data in one of the cached directories.

Caches can also become invalid if language runtimes change and the cache contains native extensions. (This often manifests as segmentation faults.)

Currently it is not possible to clear the cache via the web interface, but you can use our command line client to clear the cache:

Extract Fastcase API Access Into Standalone Ruby Gem