eGroupWare Module Customization. If you are not familiar with the inner workings of eGroupWare, please do not bid on this project.
The goal of our document management solution is to be able to log in via a web based interface and scan documents and images which can then be categorized via multiple category assignments.
This module will be tightly integrated with eGroupWare and the myDMS module. It must open as part of the eGroupWare package and be transparently part of this application. It should not be allowed to be accessed independently of eGroupWare's username / password and login.
When the user presses 'add a document/image', they should be greeted with a twain type interface giving them:
1) a select box for resolution options (72, 96, 200, 300)
2) a select box for choice of color, grey scale, black and white
The 'scan now' button should be greyed out until they make their selections.
Once they click the 'scan now' button the document should be scanned and made visible in a seperate window. In this way they can move the document off to the side while entering the data required for it. Their UI should now give them an option to either 'rescan document/image' or 'advance to data entry for this document'.
If they rescan this will close the document and return them to the 'add a document/image' section of the UI. If they 'advance', this will display the data entry portion of the UI as covered below.
NOTE: All documents and images must be converted to a PDF document. This can be done at the time of the scan or at the time of submission however it is important that all documents end up as pdf files on the server.
A scanned documents should have the following data captured with it before being submitted to the database.
1) end date on document
2) date scanned
3) multiple category select box for future category based retrieval (requires admin area to add new category names)
4) document title
5) document type (invoice, statement, image) (requires admin area to add new document types)
6) a keywords field for searching later
7) conditional data input depending on categories selected in #5. For instance if the document type was 'Invoice', a layer insertion containing fields specific to invoices such as 'amount due', 'items purchased'. This section would require an admin area where the administrator could select a defined category and then add a new field, data type, length for the type of conditional data that would be required if this category was chosen.
In addition, you must allow for the end user to choose multiple categories and therefore have multiple sections of conditional data presented. It is important that this conditional data be intuitive to use and seamless in its appearence within the application.
After 'Submitting' the document to the DMS the data is posted to the MySQL database and the image is sent to the server via ftp and placed in a directory on the server. MySQL must have a corresponding data field containing the path to find this image later and of course all its associated category and keyword data as created above.
The retrieval side of this DMS must have the following retrieval features:
1) by date or date range
2) by keywords or title of document (checkboxes offering either or both to be searched would be best)
3) by categories (multiple categories can be selected via a scrollable select box)
4) by amount (must allow for amount range ie; 100.00 - 800.00, greater than, less than or equal to)
The user should be able to use any or all of the above search criteria at one time.
A list of fields should be offered that the report will display. For instance, 'end date', 'amount', 'type' etc.. so the user can view the type of report they want. If nothing is selected, at a minimum, the document 'type', 'title', 'date scanned' should be used.
The reports generated from the above retrieval must be hyperlinked to a one page layout showing this image or documents text as well as the categories and other information. A thumbnail of the image (if an image) or a pdf icon (if pdf). If the thumbnail or pdf is clicked on, the associated application should be set to open this document. If the viewer does not have Adobe pdf on their machine, it should prompt them to install it.
A [url removed, login to view], html file or some other file describing what tables have been created and for what purpose. This file should also describe anything relative to the useage or programming structure of the project that would not be otherwise considered obvious and intuitive to CompuMatter developers.