ASP.NET Web-based File Application

This project is a web-based file application and it should be implemented based on ASP.NET MVC4 Web application and MS SQL (using local database is acceptable). No UI design, database design are required. It is simple and straight and all information and structure will be described and provided below. Only coding work is required. It should have a user management system that has a table to stores username, password, email, role, registration_date and last_login_date. When you use Visual studio 2010 to create a new ASP.NET MVC4 Web application project, it should have this function already. Just adding some extra columns. User can change password. Registration is not for public. Two user types are required, Admin and common user. Admin is able to add new user whereas common user cannot. A login page may required if there isn't any. Apart from UMS, the main functions of the website is/has (1) a page to manually download XML file from URL. User enters XML URL and clicks download button, then the XML is downloaded and stored in local folder (e.g., APP_DATA). The table in database should stores filename, file_url, file_size, file_format, user_account_ID (current logged in user), download_datatime, download_duration, download_method (default: manual). On this page, it should also list the last 10 downloaded file information (e.g., filename, file_format, file_size, download_datatime, download_method, download_duration). Also the user should be able to sort the list by each column and to change how many rows of latest records he can view (maximum 100 rows). Pagination is also required. Additionally, a validation is required when the file is downloaded. The table mentioned above should also have a column (e.g., valid) to store whether the file is well-formed or not. (2) The XML file is used to store a large number of mobile apps in <item> elements. The format is similar to RSS. When validating the XML file, the sub-element inside <item> should be parsed and stored in a table. Some example of those information are app_title, app_description, app_price and etc. Developer will receive a sample of the XML file. The table stores these app properties should have the following columns - user_account_id, file_property_name. Duplicate property is not allowed to store. (3) Two tables are required to store standard XML fields and groups. One stores product_title, product_group_id. The other table stores group_name. (4) A page called 'Mapping' where user can map their app property/field to standard fields. For example, left side page shows user's app properties and right side displays standard fields to be mapped. For example user should be able to map the app_title (left) to product_title (right). Developer may need to design how it should be presented to the user, e.g., using drag/drop (e.g., drag and move textfield up and down) or other approach (can be discussed later). A table is required to store the mapping result, where includes standard_field_id, file_property_id, user_account_id. Note: every table should have primary key and foreign key links to other table, which are ignored in the description above.