I am looking for a .NET Web Developer to completely redesign an existing Web Site Portal, including Database Design and minor application development.
The existing Web Site is written in ASP with a SQL Server 2005 backend. The existing deployment will serve as a baseline on what to improve on in regards to looks and functionality.
An application or script will need to be written to import fixed-length text files into the Database.
An application or script will need to be written to send out emails based on whether certain events happen based on information in the database.
The Web Site will need to be professional looking. It should not consist of any components that require add-ons such as Flash or Java. It should be easy to customize, i.e.; to insert a logo and change any accent colors. This would be in the form of config file or database field(s).
Logos will not be any larger than 750w X 80h. They will be displayed on top, left justified.
The Web Site will need to be compatible with at least Internet Explorer 7+, Firefox 10+, Chrome and Safari.
The Web Site will be hosted on Windows Server 2008 R2 and IIS 7.5.
The new Database will be hosted on SQL Server 2008 R2 and Windows Server 2008 R2.
An import application or script will also need to be written to import fixed-length test files. This will need to be able to be run from a command line so it can be scheduled.
The Database will be populated using fixed-length files exported from a Mainframe.
There are parts of the records that can be duplicated so the Primary Key will need to be auto-numbered.
The SQL DB will need to be designed as required by the functionality of the Web Site. There will be sample data provided that mimics the data that will be imported nightly.
Users will need an extra field to add their own unique identifier (Customer Number / File Number / Contract Number) to each record.
The new Database will eventually need existing records be imported from older Database. This will be an optional task and can be attempted later on in the project. An existing Web Site and DB will be provided for reference.
There will be two types of Users; Administrators and Users.
** Users will be associated with a particular field in the imported data.
Users will connect to the web site (https) then authenticate with a username and password maintained within the SQL Database.
Once logged in, if there are Maintenance Requests that have not yet be marked as completed by an Administrator, a CSS popup will be displayed show a summary of not yet completed Maintenance Requests.
Once the user dismisses the Maintenance Request popup, the user will be presented with a summary list of new records, associated with their user account, added within the last 24 hours. The summary list will only show a few fields from the record.
The user will also have an option to view records that fall between dates, by searching on one or more fields, or by showing all records.
Users will need to be able to click on a record from the list to show the full details, which will be formatted in a more structured view other than just a list.
Users will need the ability to export multiple entire records, in list format, into a Tab Delimited text file or an Excel Spreadsheet.
Users will need the ability to Print the details of a Record. This should be either a CSS popup or a new Print Friendly page.
Users will need the ability to request changes (Maintenance Requests) to each record. They will have 4 options they will be able to request maintenance on.
Option 1 - Change record to w (simple check box, no further info required)
Option 2 - Change record to x (simple check box, no further info required)
Option 3 - Change record to y (simple check box, a mailing address will be entered)
Option 4 - Change record to z (simple check box, no further info required)
This information will be recorded to the DB along with the user who submitted it, date and time.
There will need to be a menu item that allows the Users to view previuos Maintenance Requests. Need a way to differentiate between completed and open Maintenance Requests.
** Administrators will have the same view and query features as Users. They will not be able to make Maintenance Requests.
A routine, script, or an application will need to be created for sending email alerts to Administrators for any Maintenance Requests not marked as completed. This will be ran once per day.
Once an Administrator logs in they will be presented with Popup box (like a CSS popup) informing (nagging) them of outstanding Maintenance Request submissions, if they exist. Once they acknowledge the Popup they will be presented with a summary of Maintenance Requests.
The Administrator will click on each record and be presented with the Details of the Maintenance Request.
The Administrator will manually change the records in the Mainframe using the info on the site as reference. Once the change is complete there will need to be a check box for the Administrator to check to confirm that the Maintenance Request change was made. This will remove it from the nag list.
Administrator Maintenance Request Completion history will need to be kept. There will need to be a menu item that allows Administrators and Users to view previous Maintenance Requests that have been Completed.
Administrators will need to be able to add new users, set initial password and reset existing passwords.
** There will need to be a page dedicated to User Management for Administrators.
The User Management will be a list of users. The Administrator will either click on an existing User and a CSS popup will display the User Properties. There will also be a button for creating new a User.
** Users will need to be related to a field in the records to identify which records are theirs. This may be more than one value. This does not apply to Administrators.
There will need to be a check box which signifies whether or not the user is an Administrator.
There will need to be a check box which signifies whether or not the user receives an Email Alert that there are new records.
There will need to be a check box which signifies whether or not the user receives an Email Alert that there are new Maintenance Requests (Administrators Only).
There will need to be a check box which will disable logons for the user.
There will need to be a field for the User's Email Address.