An annual Australian regional wine show needs an online entry system that stores entry details into a database and also interfaces with a payment system. The entry system should be added to the existing web site. This website is hosted on [url removed, login to view] and is maintained using WordPress. The hosting service supports both MySQL and MSSQL databases. The supported scripting options are PHP 5 & 7, ASP, ASP.NET, Perl/CGI and Python.
The organisation has a PayPal merchant account to handle payments.
I expect to be able to award the project around 15 August 2017.
The desired project start date is 1 September 2017.
The solution should be available for testing by 29 September 2017.
Your proposal should provide for support (for the administrator only, not the Entrants) in the first month of going live.
The following general description of the entry requirements is provided for information only. The attached Scope document should be referred to as the definitive list of the work required to complete this project. This Scope document lists the requirements in two groups - Administrator functionality and website functionality.
The show is based on classes, where a Class is based on variety and vintage. An Entrant will typically be entering for only one Exhibitor and an Exhibitor will typically only have one Winery, but some Entrants have multiple Exhibitors, and some Exhibitors have multiple Wineries. A Winery will typically have more than one Entry, and each Entry is a single wine in a single Class. The entry fee depends on the Class. The number of Entries will be less than 500 each year. The number of bottles to be delivered for judging also depends on the Class. See the attached preliminary database schema.
From the perspective of an Entrant, an 'entry' is a transaction with one or more Entries and a calculated total entry fee. The 'entry' is only valid after payment is received. The Entrant should get acknowledgement of payment.
Once an Entrant has created login details (email based), they should be able to come back and add entries. The Entrant details should be persisted and lost password functionality provided. A csv file of entries produce after the closing date is needed. Administrator(s) access is required including an administrator report of entries.