This package provides a datatype for mapping descriptions of legal problems
to NSMIv2 categories. It uses the Spot API developed by the
The Legal Innovation & Technology Lab at Suffolk Law School.
This package requires docassemble version 0.5.86 or later.
To use package, first obtain an API key for the Spot API.
Then put that API key into your Configuration:
spot api key: abbaabba1234abbaabba1234abbaabba1234abbaabba1234abbaabba
Then you can use spot as a datatype. For example:
question: |
What is your legal issue?
fields:
- no label: legal_issue
input type: area
datatype: spot
---
mandatory: True
question: |
% if legal_issue.result == 'Housing':
We can help you with that housing issue.
% else:
Sorry, we don't help with that.
% endif
In this example, the variable legal_issue will become an object of type
SpotResult. This is a subclass of DAObject. The user's original text is
available at legal_issue.source. The result is available at legal_issue.result.
When reduced to text, a SpotResult object returns legal_issue.result. If the
legal issue cannot not be determined, legal_issue will be None and an error
message will be written to the logs. The NSMIv2 code is available under legal_issue.id.
Only the first result is used for the .result and .id attributes. If you
want to inspect into the actual result returned by the API, you can find it
under legal_issue._full_result.
Metadata
Release files for docassemble.spot 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| docassemble.spot-0.0.3.tar.gz | 4.1 kB | Without provenance | Details for docassemble.spot-0.0.3.tar.gz |
Release files / docassemble.spot-0.0.3.tar.gz
| Download URL | docassemble.spot-0.0.3.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f615341138a39b03740206f339b64d92d751ab38ee075ecb1ea80e8f8bb08652
|
|
BLAKE2b-256 checksum How to use checksums |
0771bfdf1885966beb629d41cb6c05826bc5dcdff730ec759eee610b723021b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.9
|
Security for docassemble.spot 0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.