OwlBoard/diagram-parser
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Deprecated in favour of newer 'dgp2' software.
This repository has been archived on 2024-11-02. You can view files and clone it, but cannot push or open issues or pull requests.
4 Commits 2 Branches 0 Tags 677 KiB
Python 100%
e1cdb6fb17
Go to file
Fred Boniface e1cdb6fb17 Update 'README.md'
2023-08-05 15:20:36 +01:00
src Add 'src/main.py' 2023-08-05 15:03:35 +01:00
.gitignore Initial commit 2023-08-05 14:56:20 +01:00
LICENSE Initial commit 2023-08-05 14:56:20 +01:00
README.md Update 'README.md' 2023-08-05 15:20:36 +01:00

README.md

diagram-parser

This is an experimental project and is not yet used as part of the OwlBoard stack.

Aims

The aim of diagram-parser is to simplify the addition of PIS codes that are not yet in the OwlBoard data source. The planned implementation is as follows:

  • diagram-parser is subscribed to an email inbox (IMAP/POP3)
  • Formatted train-crew schedule cards are sent to the inbox (DOCX - Maybe PDF alternatively - format) and loaded by diagram-parser
  • List of existing PIS codes is loaded and a list of non-existent codes is compiled (0000-9999)
  • If a code is found both in the diagram and on the list of non-existent codes, a Gitea issue is opened providing details of the code.
  • Once the program has run and extracted only the relavent details, the email is deleted and the file is closed and not stored.
  • The evantual aim is to avoid any manual searching of the DOCX files.

The current process of adding new codes involves being made aware of them face to face, or finding them myself and manually finding and adding them to the data source.

Points to Remember

  • Emails received should be verified.
    • A pre-authorised key in the subject field, any emails not matching the key should be discarded.
  • Attachment formats may vary slightly.
    • The format of the attachment should be checked and any errors handled gracefully.

Main external dependencies (Expected)