Need a new website/webapp created for customers to download files from.? We plan to host this website internally on our own IIS6 (windows 2003) server.?
Would like our? customers to log into the website with an Active Directory username and Password that we have setup, as well as providing their Client ID.? ? When the website page loads, it lists all files from their folder in ascending order.? The customer then has the option to click a button to “download all?? files, or they can place a checkmark next to select files and click a button to “download selected?? files.? Upon downloading the files, they are also moved into an Archive folder for the client on our server (so the customer doesn’t get confused and download them again).? The archive folder name would be client id + _archive (i.e. 29374832_archive) and can reside in the same folder share location.? The website will also need an Archive page link for the customer to be able to download old files from the archive folder if necessary.? (We then want to delete any files older than 45 days from the archive folder, but this can probably be accomplished with a script running each night as an NT Task that we can write.)
## Deliverables
We would like the site to have the following features.
? -internally, our users would drop files into a shared folder on our network for a customer.? The folder name would be the Client ID (i.e.? 29374832). (The Client ID is a numeric number that we already have defined for our customers. ? I believe it has a limit of eight characters but I will have to verify that.)
? -Our customers log into the website with an Active Directory username and Password that we have setup, as well as providing their Client ID.? ? When the website page loads, it lists all files from their folder in ascending order.? The customer then has the option to click a button to “download all?? files, or they can place a checkmark next to select files and click a button to “download selected?? files.? Upon downloading the files, they are also moved into an Archive folder for the client on our server (so the customer doesn’t get confused and download them again).? The archive folder name would be client id + _archive (i.e. 29374832_archive) and can reside in the same folder share location.? The website will also need an Archive page link for the customer to be able to download old files from the archive folder if necessary.? (We then want to delete any files older than 45 days from the archive folder, but this can probably be accomplished with a script running each night as an NT Task that we can write.)
We have over a 100 customers that will need to use this site, and I want to make is simple and easy for you to pull the correct files for the website and also for our internal users to figure out where/what files are.? so I envision as simple the folder structure to just have all the Client ID and Archive folders in a root shared directory and would look like this:
RootFolder ->29374832
RootFolder ->29374832_archive
RootFolder ->45342566
RootFolder ->45342566_archive
Etc……