Wine Show Blind Tasting Backend Portal
Budget: $1,500 – $3,000 AUD
I'm looking for a developer to build a backend portal for managing a wine show blind tasting event. This portal will allow wineries to enter their wines and judges to score and comment on the entries.
Key functionalities include:
For Wineries:
- Enter wine details: Wineries should be able to input all necessary information about their wines.
- Wineries need to have a way to monitor the status of their wine entries.
- Before they submit their entries, they can edit and delete as needed. Once entries have been submitted they are locked out of editing or deleting. Site admin can alter upon request though.
- After judging is complete, they can see the judging comment as well as points awarded.
- They are able to generate invoices for their entries and pay using Square.
- Manage profile information: Wineries should be able to update and manage their own profile information.
For Judges:
- Score wines: Judges will need a straightforward system for scoring the wines.
- Comment on wines: There should be a space for judges to leave comments on each wine.
- Judges can only see the current bracket of entries that they are judging to point and comment on.
- Entering results will look similar to judging sheets, for a bracket that may include 2 or more classes to be judged in the same bracket, these will need to be consecutively numbered with a gap between each class that matches the numbering on the judging sheet.
- View previous scores and comments: Judges should have access to their past scores and comments for reference but not able to edit older records, that will be the admin role.
For Committee:
- Able to start a new judging year at the push of a button. This will create required database tables to allow for the new year and update server-side code for the new year if needed.
- Add judges per year. Add and edit winery data. Add and edit committee data.
- Do reporting: Reports to include year comparisons, winery participation, entries per class, entries per winery, entries in bracket order for sorting prior to judging and other reporting query based.
- Generate entry labels for wineries to print off.
- Allow for record search and result posting to a show website.
- Able to printout judging sheets for a bracket that may include 2 or more classes to be judged in the same bracket, these will need to be consecutively numbered with a gap between each class.
- Admin management of all aspects of the modules.
- A separate area for the treasurer to have reporting and to view invoices.
The old system was built using Classic ASP, this system can be used for reference if needed. The information stored for the old system will still be used for historical records.
The portal will require a simple username and password authentication system. Please ensure you have experience in creating user-friendly interfaces and managing backend databases.
There is a deadline for this project, it has to be up and running by July 1 2025. Articulate in English is a must.
Key functionalities include:
For Wineries:
- Enter wine details: Wineries should be able to input all necessary information about their wines.
- Wineries need to have a way to monitor the status of their wine entries.
- Before they submit their entries, they can edit and delete as needed. Once entries have been submitted they are locked out of editing or deleting. Site admin can alter upon request though.
- After judging is complete, they can see the judging comment as well as points awarded.
- They are able to generate invoices for their entries and pay using Square.
- Manage profile information: Wineries should be able to update and manage their own profile information.
For Judges:
- Score wines: Judges will need a straightforward system for scoring the wines.
- Comment on wines: There should be a space for judges to leave comments on each wine.
- Judges can only see the current bracket of entries that they are judging to point and comment on.
- Entering results will look similar to judging sheets, for a bracket that may include 2 or more classes to be judged in the same bracket, these will need to be consecutively numbered with a gap between each class that matches the numbering on the judging sheet.
- View previous scores and comments: Judges should have access to their past scores and comments for reference but not able to edit older records, that will be the admin role.
For Committee:
- Able to start a new judging year at the push of a button. This will create required database tables to allow for the new year and update server-side code for the new year if needed.
- Add judges per year. Add and edit winery data. Add and edit committee data.
- Do reporting: Reports to include year comparisons, winery participation, entries per class, entries per winery, entries in bracket order for sorting prior to judging and other reporting query based.
- Generate entry labels for wineries to print off.
- Allow for record search and result posting to a show website.
- Able to printout judging sheets for a bracket that may include 2 or more classes to be judged in the same bracket, these will need to be consecutively numbered with a gap between each class.
- Admin management of all aspects of the modules.
- A separate area for the treasurer to have reporting and to view invoices.
The old system was built using Classic ASP, this system can be used for reference if needed. The information stored for the old system will still be used for historical records.
The portal will require a simple username and password authentication system. Please ensure you have experience in creating user-friendly interfaces and managing backend databases.
There is a deadline for this project, it has to be up and running by July 1 2025. Articulate in English is a must.