552458 Electronic archiving managment system

Project based on archiving idea that combine between archiving and administrating office, project having three main things: 1. Interface: Screen interface allow the user to receive information*from all types of files that can have a screen to configure it. And using same settings installed on the computer: • Import e-mail, including attachments such HML, WORD and graphs files of all types. • Receiving and storing documents of all types (images, Word files, HTML, emails, video, images from a camera, etc.). • System receives documents from scanners, camera, disk file, E-mail (both individual boxes and what - Exchange) directly into the system's database. For the emails, user will keep using his email software, outlook or whatever, and when he would like to use one of the emails through our software will press a click and will convert it. 2. B. Database: Data that entered using the interface will stored in a database, after all the information that needed fulfilled, and suppose to be consist of all fields that help to retrieve the data later on, and date. Updating on file/s, will go according to software that execute it on the computer/workstation itself. Database Fields: Title Description Number Using of the Archiving numbering standard – Auto number. Title Allow the user to use name differ than its original name. Description Describe everything about the file, and will do a job of META, Link Where the file stored, Suppose to be stored according to structure that we gave to them. …etc We need the following windows that show: 1. Insert/ Update files. 2. Insert/ Update emails. 3. I think many things need to be do, but can't think of them, so maybe you can advice me. 4. Show many versions of file, according to the update. 5. Ability to search inside documents, while its not image. 3. D. Workstations – computers: Which is the computers that can use the software, and there is no special requirements for it. This computer can do: 1. Work as input unit. 2. Retrieve data. 3. Do transactions on any file. 4. E. Output The output of the software will be something that can do many transactions such as: 1. Sending emails: with attachments, and same letter with different name. 2. Sending faxes: consist of many papers and with different names. 3. Publish to Google docs. 4. Another transactions according to the organization, need to have something easy to build it. All of these specifications is still not clear, because I'm in development process, so I dont know if this things I need unless i can see final thing.