Prototype workflow to use AI to extract judgment details #2100
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
longhotsummer
force-pushed
the
extractor
branch
from
f1bd68d
to
e8f0726
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Once configured, the user goes to /admin/peachjam/judgment/upload/ and uploads a file. It calls a Laws.Africa API which returns metadata for the judgment. The judgment is created and the user must make any edits.
https://www.loom.com/share/b9037635acb7491195a9915191745d7a
Also:
CITATOR_API_KEYsetting will be merged intoLAWSAFRICA_API_KEYinstead which covers all Laws.Africa APIs