The Strategy of Scripting with the Lex Machina API
Writing scripts with the Lex Machina API have a recognizable design pattern
I have written a number of scripts that access the Lex Machina API. Some of these were for testing, some for demo and some for proof of concepts for current and potential customers. As I look at the structure of them, almost of all of them fit into a distinct pattern.
The logic I have authored has these phases:
Optional search (input text, search for judge, party, etc) or possibly looping over a list (all state or federal district courts) Using either that input and/or hardcoded values, do a query for cases Take the resulting list of cases and look them up one by one Extract values from individual cases for use.
