Skip to content

#299- severity flagging with keywords#300

Open
Cubix33 wants to merge 1 commit intofireform-core:mainfrom
Cubix33:severity-flagging-with-keywords
Open

#299- severity flagging with keywords#300
Cubix33 wants to merge 1 commit intofireform-core:mainfrom
Cubix33:severity-flagging-with-keywords

Conversation

@Cubix33
Copy link

@Cubix33 Cubix33 commented Mar 19, 2026

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.

@Cubix33
Copy link
Author

Cubix33 commented Mar 19, 2026

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEAT]: Real-Time Severity Keyword Flagging

1 participant