Basic Digital Asset Extranet

I need to create a fairly simple extranet for clients to use to make available files to their customers. I've attached a detailed flowchart and table listing. It may look like a lot more than is actually there. Here are basics: **Phase I: Extranet and Admin ** The extranet is straightforward, and included in .zip file are screen shots. You'll be provided with .PSD files for these screens that you can use to build the basic sites and .CSS doc. The overall functionality is that we, on behalf of our Client, will upload a bunch of Word and PDF docs that we want to make extremely easy for our Client's customers to access and download. Therefore, in addition to storing the files and allowing them to be downloaded using point and click functionality, we'll store basic information about each file that can be displayed (see screens) so that the user can decide if it's something they wish to download. The admin application will allow us to upload the docs and create the basic information about the file. Additionally, we can add new sites (we'll create multiple sites for our Client with different assets loaded for each), categories (used for grouping the display of assets--in the example screens, you'll see categories like Print Ads and Parent/Student Tools) and programs to associate with the app (on the sample screens, see where it indicates what program it opens with). Again, this may look terribly detailed, but in fact, you'll notice that the basic admin functionality is identical across all categories of information so hopefully will be something you build once and use or replicate for each file type. (Continued in Deliverables) ## Deliverables (cont'd from Description) **Phase II: Add User Authentication and Tracking **Once the basic site is operational, we'll want to come back and add authentication on the front end to restrict access to the documents. Additionally, we'll want to track key events such as viewing assets and downloading assets. **Phase III: Reporting **There's nothing in the flowcharts about this, but we'll want just a basic report viewer that is accessible via the Web and enables the user to view transaction data restricted by various fields (e.g., date range, site, etc.) and sortable. ** IMPORTANT!** Phase I is extremely urgent. We need to have this fully operational by EOD US time on Thursday of this week. So this may be a good assignment for someone who's built a similar app in the past and can simply repurpose the code and make edits. Phase II can be completed next week and the reporting after that. Also, if you bid by Phase, then I'll release funds accordingly as each phase is completed (rather than having to wait to the end to receive payment for any of your work). ========================================= 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform PHP/MySQL (please don't ask if you can use Oracle or Microsoft or other platforms; we have only PHP/MySQL available to us on our server)