Edgewall Software

Changes between Version 6 and Version 7 of CookBook/Configuration/DocumentManagement


Ignore:
Timestamp:
Oct 20, 2015, 9:31:35 PM (4 years ago)
Author:
figaro
Comment:

Further cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • CookBook/Configuration/DocumentManagement

    v6 v7  
    11= Document management system
    22
    3 {{{#!box info
    4 **Note:** This page is under development.
    5 }}}
    6 
    7 Trac is perfect as a document management system when you treat documents as tasks. It is perfect for high volume fax incoming and processing. In one particular case 661,124(by 2012) documents/tickets( have been processed and the set up still works in production environments. (1,349,069 tickets by 2015)
     3Trac is perfect as a document management system when you treat documents as tasks. It is perfect for high volume fax incoming and processing. In one particular case 661,124 (as of 2012) documents/tickets have been processed and the set up still works in production environments. (1,349,069 tickets by 2015)
    84
    95The key features that we needed:
     
    2218
    2319Channels:
    24 * Email: email2trac plugin (follow link on [th:EmailtoTracScript] ). Multiple email accounts "support@example.com,incoming@example.com,underwriting@example.com. You control which milestone,component,and version each email is routed to. On main wiki page you provide links to each milestone. The message can be either an email or a fax (fax2email). All general tickets go to milestone Incoming. From there indexer moves to to appropriate milestone(processing types), version(per state or line of business), and component(type of document that might require special handling).
    25 * Faxes: Newer system, or cloud based fax2email get routed via email. If you have faxes, you can write 30line python code script that takes tif and uploads to trac using xml-rpc. In our case we converted tif to pdf, extracted created time,fax#,# of pages and created ticket with all that information. Every 30min all new faxes get uploaded.
    26 * TracScripts : these are custom scripts written by you that autoclose tickets using XML-RPC. As you automate some items that are processed by the system, you might be receiving email documents as a backup, automatic issuance, esignature confirmations,etc. Since these were already processed we wrote scripts that query (using xml-rpc) the open tickets, get contract_number and close them (while updating other info). What ever else is not closed gets looked at by somebody and processed manually in that department. Other scripts loop through open tickets, and if special accounts are found the tickets priority gets autochanges to critical, and move up in priority. Other scripts update tickets based on the contract#, pull data from other database and store info in keywords.
    27 * [th:TicketMoverPlugin] Since each department had a different milestone requirements each got a separate instance of trac. Common milestone for all is Incoming. [th:TicketMoverPlugin] allows you to move tickets between tracs when faxed to the wrong place.
    28 * Wiki: Using wiki you can create custom query on ManagementReport pages, that summarizes current open task list. CEO has direct access to that page and can check if department is falling behind and can add/hire additional people, or authorize overtime at first signs of backlog.
    29  
    30 
     20* '''Email''': email2trac plugin (follow link on [th:EmailtoTracScript]). Multiple email accounts "support@example.com,incoming@example.com,underwriting@example.com. You control which milestone, component and version each email is routed to. On main wiki page you provide links to each milestone. The message can be either an email or a fax (fax2email). All general tickets go to milestone Incoming. From there indexer moves to the appropriate milestone (processing types), version (per state or line of business), and component (type of document that might require special handling).
     21* '''Faxes''': Newer system, or cloud based fax2email get routed via email. If you have faxes, you can write 30-line Python code script that takes tif and uploads to trac using xml-rpc. In our case we converted tif to pdf, extracted created time,fax#,# of pages and created ticket with all that information. Every 30min all new faxes get uploaded.
     22* '''Trac scripts''': these are custom scripts written by you that autoclose tickets using XML-RPC. As you automate some items that are processed by the system, you might be receiving email documents as a backup, automatic issuance, esignature confirmations,etc. Since these were already processed we wrote scripts that query (using xml-rpc) the open tickets, get contract_number and close them (while updating other info). What ever else is not closed gets looked at by somebody and processed manually in that department. Other scripts loop through open tickets, and if special accounts are found the tickets priority gets autochanges to critical, and move up in priority. Other scripts update tickets based on the contract#, pull data from other database and store info in keywords.
     23* '''[th:TicketMoverPlugin]''': Since each department had a different milestone requirements, each has a separate instance of Trac. Common milestone for all is Incoming. [th:TicketMoverPlugin] allows you to move tickets between Tracs when faxed to the wrong place.
     24* '''Wiki''': Using the wiki you can create custom query on ManagementReport pages, that summarizes current open task list. CEO has direct access to that page and can check if department is falling behind and can add/hire additional people, or authorize overtime at first signs of backlog.
    3125
    3226If you think of your problems as "tasks" then Trac is suitable for use as a Document Management System.