FTP Replacement

Client requested a solution for FTP replacement. Current workflow consists of customers uploading audio files to an FTP server. Employees then download the audio files, create transcriptions, and upload word documents. Some customers have automated the uploading of audiofiles by creating scheduled tasks. The client has specified the following requirements:

• user will receive a message about the status of the file upload
• administrator can search for transcription document that belongs to an audio file

In other words, track all inputs and outputs to the business process and handle errors gracefully. Also, most customers have better things to do than worry about uploading audio files, thus minimize the impact of the change.

FTP has some obvious disadvantages though, such as ease of use, security, etc. It would probably be easier to use HTTP instead, and log all file uploads and the relationship between audio files and word documents in a database. Is there a way to allow existing customers to keep using FTP, and still use a database on the backend?

Also, is anyone familiar with online services such as Onehub or Boltfile? They offer plenty of functionality and seem to be relatively inexpensive. I think they could offer a valuable alternative to developing a customized solution.

Robert Matousek
Medfuse
Medical Web Experts
View online demo