Jason Thistlethwaite
32 lines
2.4 KiB
Markdown
32 lines
2.4 KiB
Markdown
I want a skill (or set of skills) that accomplishes the following:
|
|
|
|
## Context
|
|
|
|
We have found that using networked printers like HPs to scan various documents have them emailed to inboxes wired up to the Redmine Helpdesk plugin a very useful way to avoid losing paperwork and speed up finding it later. That has been instrumental on several occassions, where we've had the printer in my office configured to email scanned files to hr@ldrprep.com, where they get imported as tickets with the scanned document as a file attachment.
|
|
|
|
Even with that, to make it truly useful, somebody still has to typically do this:
|
|
|
|
1. Log into redmine and go to the hr project's issues.
|
|
2. Identify scanned document emails (usually the subject like says something like "Scanned document...")
|
|
3. Open the attachment to see what it is.
|
|
4. Edit the ticket and change the subject line so if we search later on, we'll most likely be able to find the ticket with the attached file.
|
|
5. Optionally, transcribe key points or info from the document and add them to the ticket.
|
|
|
|
## Goal: automate this process
|
|
|
|
|
|
- [ ] **Convert target ticket**: When passed a redmine issue id and asked to peform this action, the following should happen:
|
|
- Fetch the ticket and check if it has any PDF files attached to it.
|
|
- Download the PDFs and use OCR or similar technology to extract the main topics and entities mentioned within the document(s).
|
|
- Update the ticket by changing it's subject line to reflect what the attached documents are. If they're mainly about one particular person or company, the subject line should include those.
|
|
- [ ] **Scan project**: When asked, search/scan a specified Redmine project to locate tickets where this hasn't been done yet, and then do it for all of the tickets found.
|
|
- [ ] **Cron-usable skill**: Once this is done, I want to have it as a skill I could easily add to an agentic cronjob, what will enable it to scan/check a specified list of Redmine projects whenever it runs, and then automatically perform this action.
|
|
|
|
## Testing parameters
|
|
|
|
- The test instance of redmine located at `192.168.50.170` can be used to test functionality. It supports the same authentication info as the live redmine.
|
|
- The email aspect of this is not important at all. It would be fine to simulate it as follows:
|
|
- Create a new ticket simulating what an ideal target would look like
|
|
- Upload a pdf to it
|
|
- Then, run the relevant workflow against the test ticket to check results
|