#299- severity flagging with keywords#300
Open
Cubix33 wants to merge 1 commit intofireform-core:mainfrom
Open
Conversation
Author
|
EXAMPLE SCREENSHOT when transcript contains "He was in a fire". : [1] Received request from frontend.
[2] PDF template path: ./src/inputs/file.pdf
[3] Starting extraction and PDF filling process...
🚨 [URGENT]: High-severity keyword detected -> 'fire'
----------------------------------
[LOG] Resulting JSON created from the input text:
{
"SEVERITY_FLAG": "HIGH",
"Employee's name": "John Doe",
"Employee's job title": "managing director",
"Employee's department supervisor": "Jane Doe",
"Employee's phone number": "123456",
"Employee's email": "jdoe@ucsc.edu",
"Signature": "<Mama\u00f1ema>",
"Date": "01/02/2005"
}
--------- extracted data ---------
----------------------------------
✅ Process Complete.
Output saved to: ./src/inputs/file_URGENT_20260319_200349_filled.pdf
|
6 tasks
This file contains hidden or 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
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.
Closes #299
Added a check that will automatically flag a warning sign if the transcript contains any important keywords such as 'fire', 'hazmat', 'danger'. That way, the admins will automatically know what reports to look into first, and which one to prioritise, or maybe even categorise as important in storage for further future use and reference, and better lookup.