Repository navigation
Release: 0.2.0
Updated to amos 0.2.3, whose loaders
replace the "cases" section of a project's settings. Settings written for
0.1.0 need the changes below.
Added
- Loaders, a genre of
amosloaders (CaseLoader) in the newloaders
module:load_court_listenerdownloads (if asked), parses, and codes
CourtListener cases;load_lexis_nexisdivides, parses, and codes
Lexis-Nexis cases; andload_casesloads a table saved bysave_cases.
Named first in the wrangler, a loader makes the project's data, so a
project needs noitem. Loaders work through the project's clerk: sources
are found (and downloads saved) in its input folder, and a "save"d table is
kept in its interim folder. The label is checked after the coders run, so
it can be a column that a coder makes, and the dataset's history records
the loader and each coder.
Changed
- Requires amos 0.2.3 (and pandas 3).
courtpy.Projectis nowamos.Projectitself, which runs a workflow with a
loader without anitem.codemoved to thecodersmodule (it is stillcourtpy.code).- The example study and the documentation use
sk_logit, scikit-learn's
logistic regression, because amos 0.2.3 gave the namelogitto the
statsmodels model (which needspip install amos[statistics]).
Removed
- The "cases" section of a project's settings,
courtpy.build,
courtpy.collect, and theinterfacemodule. Move the settings of a
"cases" section to a "load_court_listener_parameters" (or
"load_lexis_nexis_parameters") section, add the loader to the start of the
wrangler's techniques, and rename "folder" to "source". Relative paths are
now in the clerk's input folder ("save" in its interim folder) rather than
its root folder.