-
Notifications
You must be signed in to change notification settings - Fork 3
Upload Log Scenario
Rick Eversole edited this page Apr 2, 2014
·
3 revisions
There are two scripts for how a user will upload a log depending on how modern his/her browser is.
- Contestant goes to upload web page.
- Page offers an area for drag-n-drop, a button to click for upload, or a button/link to text entry panel for cut-n-paste.
- User indicates log in one of the three methods and Java script uploads the file in the background using AJAX approach.
- Server infers as much about the entrant as possible from the log and sends information back the the client via AJAX.
- On the same page, indicate that the log has been received.
- A form appears to request the entrants category, email address, t-shirt size, YL, youth, etc. The initial value for these is determined by the uploaded file.
- Note: T-Shirt entry needs to allow multiple T-shirts in differing size. Important for Multis. Also we need a general way to handle the T-Shirt issue. Maybe all we really do is optionally send the user to a separate system after "sumbit" is pressed. In 2009, I had lifted the "100QSO limit" to get a T-Shirt. We just want to promote contest so no reason to limit who can get them.
- The user fills in and/or confirms by pressing a submit button.
- The server checks the log and provides a new page indicating issues it found with the log and the information entered by web form.
- important that feed back include instructions for the logger used when it is possible to determine that.
- At this point the log entry is completely done. The contestant might choose to fix errors in the log and resubmit.
The sequence of steps is pretty much the same, but they system does not use an AJAX approach. Every step in the process requires a new page.