submission form and backend

Summary: The purpose of this submission form and backend is to keep track of Unique Device Identifiers (UDID) that are found on every Apple iOS device, a 40 character alphanumeric code. I run a small website that is active each June, after Apple’s World Wide Developers Conference. This website allows Apple enthusiasts to submit their iOS device’s UDID (like a serial number) so that they can pass Apple’s online activation and use the latest iOS beta. The current website: [login to view URL] — Customers will be submitting their UDID to the Admin — Admin will then register this UDID with Apple — Admin will add this UDID to the Admin’s online records — Customer will be able to check the status of the UDID within the Admin’s online records After many years without a backend system, it is time to improve the website’s submission form, and provide a way for customers to check their UDID and my admin records. For an example of this, please see a current competitor who has a good submission form and verification check: [login to view URL] I am very comfortable with HTML and CSS, and changing PHP as needed, but I will need someone who can write the JS and PHP required, implement the code within my site, and make any MYSQL changes as required. I would like this completed within 3 days. I would also like someone who can continue to improve and modify the backend over the month of June as required. ### A. Backend / Database Requirements: A1. There will be a secure sign in for the Admin: [login to view URL] The password and user can be hardcoded, if this would be secure and easy to change at the source. A2. Once admin has securely signed in, the Admin will be able to add multiple UDID records to the Admin’s database using a simple form. The form will either allow submissions via: — CSV upload; or — pasting in multiple records (one record per line, 100 lines maximum) via text field. A3. All uploaded/submitted records will be visible to the Admin in a simple list. Individual records can be removed from this list after confirmation dialog box. ### B. UDID Submission Form. B1. On the Admin’s homepage, there will be a form with: — a 40 character text field — a Register button — a Check button B2. The form, through javascript, will validate the UDID entered into the text field. All valid UDIDs: — must be 40 characters long – must only contain the following 22 characters: 0123456789abcdefABCDEF B3. If the Customer enters a UDID, and then selects the Check button, 2 messages will be displayed just below the form. Message 1 will be displayed based on the javascript check described in section B2: — “This is not a valid UDID. Learn how to find your UDID.” — “This is a valid UDID.” Message 2 will be displayed based on the Admin’s records described in section A: — “This UDID has not yet been registered with Apple.” — “This UDID has been registered with Apple.” B4. If the Customer enters a non-valid UDID, and then selects the Register button, the javascript check will return the error message in section B3 if required. B5. If the Customer enters a valid UDID, the form will forward the UDID to a simple PayPal payment form that included the UDID record within the payment notes. For an example of this, please see a current competitor: [login to view URL]