The purpose for creating TagMail stems from a need to organize email communicationacross functional departments of an organization. For example, at my current employer, the Sales department organizes their communication by quote thread or project. This is performed manually by the user at the time of the email reading. However, requirements, negotiated terms, or clarifications may be embedded in a diverse email stack, and are generally in an unpredictable order. In order to better capture the nature of this communication, I propose the following:
An email client with the following requirements
a. Web accessible
b. Database repository of email communication
c. Associative tagging of emails
d. Tag filtering
e. Automatic Tag propagation across email accounts
An email bot with the following requirements
a. Automatic scan of a designated account
b. Tag parsing and storage
c. Tag sort, filtering, and retrieval
To create an email client with the capability to automatically scan an email account (ex. data@company.com), parse the email for tags, and store the email in a common repository for web access. Additionally, an email client which is repository aware shall be created to allow for standardized tagging and formatting of emails without the requirement for special server processing.