-
Notifications
You must be signed in to change notification settings - Fork 3
Submission Server
Rick Eversole edited this page Mar 31, 2014
·
5 revisions
This page discussed ideas for the submission server. Focus here is on the public view (no login required) private view is elsewhere.
What needs to be done:
- Permit user to select a file from their local system and upload file
- Drag and drop of file would be a nice modern feature. Document on page if implemented/supported
- Permit user to cut-n-paste the log directly.
- Entry text box should be scrollable and support sizing. Refer to CQ WW for example.
- Validate the submitted file against base requirements.
- Tell user when format is wrong, and how to correct (ie. if ADIF tell user to submit Cabrillo)
- Display a list of submitted logs
- Operational Callsign
- QTH
- Marker to indicate if log deemed legal/acceptable *Club?
- Display time until log submission closes
- Require Callsign to submit
- Ask for optional email
- Ask for contest specific items
- California QSO Party
- T-shirt ordering?
- YL
- Youth entry
- Provide a feedback form
- Let user designate as "checklog"
Questions?
- at this point do we make minor corrections to logs or defer?
Data tables needed. (Not Railified ... not convention over configuration)
ID | Name | RulesURL | several configuration fields indicating things like YL/Youth supported | maybe embed the header footer into the database? |
---|
ID | ContestInfoID | StartDate | EndDate | DueDate |
---|
ID | ContestID | CallSign | LogFile | LogType | Accepted |
---|
Used by middleware and reporting
ID | ContestID | AcceptedLogID | NormalLogFile | Score | CategoryPower | ... other Cabrillo 3.0 category fields for scoring/reporting | YL | Youth |
---|