| |
|
|
Job Summary:
|
| |
| Job Type: |
Project |
| Budget: |
$ 1000-5000 |
| Required
Skills: |
,
,
,
,
|
| Attached
Files: |
(None) |
| |
|
| Status: |
Closed for bidding
|
| |
|
|
|
Buyer Summary:
|
| |
| Username: |
|
| Feedback Score: |
Rating: (No Feedback Yet)
|
| Award Reliability: |
3 posted 0 paid |
| |
|
| Location: |
UK, North West, United Kingdom
|
| Member Since: |
February 7, 2010 |
| |
|
|
|
| Invited Users: |
There are no invited users
|
Description
To design a website and database for an online poker staking website – Based on the design of online staking site www.SharkStaking.com:
More information about staking can be found here: http://en.wikipedia.org/wiki/Poker_staking
We will provide all written copy, logos, and website/database design guidelines. Shopfront
Part 1) A 10 page website built to our design, with text and logos designed by us. The above will include 3 pages which need to be altered as required via an admin website management system.
Backend:
Part 2) The application system. A form allowing players to apply for a stake. This form consists of a selection of text boxes, and image upload boxes.
When a player fills the form out they choose a username, and are assigned a randomly generated password (10 – 14 characters, case sensitive, including numbers) by the database. Filling out the application form makes the user a member of the site (usertype applicant). And they can log in and edit their application at any time. When applying they are assigned the usertype ‘applicant’.
Usertype admin can view all applicants. These will be displayed in a list which is organised by most recent applicant 1st
Admin can view applications, make internal notes on the application (only viewable by usertypes admin and coach).
Admin can send messages to the applicant via this application page, and will be able to receive messages from the applicant via this page. When a message is sent an email is generated to the applicant informing him that a message is waiting for him on the site. With a link to the correct page.
Admin can select from the following usertypes if he wishes to change the users usertype.
Admin, Coach, Applicant, Player, Pending, Rejected.
An email is sent to the user whenever his status is changed.
An offer form is on this page. This allows admin to offer a stake to the player. The above form consists of 10 text boxes each allowing 1000 characters.
When an offer is made an email is sent to the applicant inviting them to view the offer. Player cannot edit the offer. However he will have the option to accept or reject the offer. To do so player will select yes/no radio buttons for each part of the offer, and also digitally ‘sign’ the offer but typing ACCEPTED, and entering his name at the end of the form.
When an offer is accepted or rejected admin is emailed.
Part 3) The userpage
This page contains much of the details requested in the application screen, along with several other pieces of information. Some of this information is static, and some will be used for financial processing etc. A full list of required information will be provided as required.
Part 4)The financial management system.
This is based around three figures.
A) Stake This is the total stake held by the player
B) Makeup This is the total amount of additional stake provided to losing players
C) Total in account This is the total amount of money held by the player
Admin needs to be able to enter these figures against the player. Player needs to be able to enter total on account when reporting results (covered later)
The players will be entering the total amount in their accounts on another page (explained later). This will be weighed against the total stake and makeup to determine the players total profit and loss.
So. Player A has a total stake of 1000, and has entered 1200 in the results screen (below). This will show up on the players screen as 1200 total, 0 makeup, 200 profit.
Player B has a total stake of 1000, and has been given makeup of 500. He has also entered 1200 in the results screen. This will show up on his players screen as: 1200 total, 500 Makeup, 300 loss.
The results screen.
This consists of the following:
Box A: Total money on account Box B: Total VIP points on account Box C: A freeform txt box for player comments, 500 characters.
Hands upload: A button allowing players to upload txt files directly from their harddrive. They should be able to upload 100 at a time, and these should be stored against their site username. These should also be auto emailed to email address as specified on the users userpage, and be available for download by admin on the players userpage.
The player logs in, provides the above information, and the information then has to be accept/rejected by admin. When accepted the information is weighed against the database to provide a current profit/loss/makeup for this player.
When results are accepted or rejected the player is emailed to let him know that this has happened. The email should include the players current stake, makeup, and total on account (box A)
Admin should be able to adjust all the various financials types as required on a players userpage. Add and subtract makeup, stake, profit etc.
Part 5: Profit splitting
Admin will be able to split profit with players at anytime. On the profit split page all users will be listed, along with a radio button next to each if selected the player will be required to split profit. Admin can select any number of players or can choose ‘select all’
When a player is chosen for profit split the following occurs.
For players with no makeup
The system looks at the players current stake and current results. If results are higher than stake a split function is generated. This emails the player telling them the amount that they should transfer to admin. The figure is based on the total profit, and the agreed split % (this figure is entered by admin on the userpage).
So, player A has a total stake of 1500, 0 makeup, and accepted results of 1600. Player A has a profit split % of 50% (the % split is the % retained by the site).
The player is emailed requesting that they withdraw their share of profits and transfer our share of profits. For the purposes of the above example these figures would be \ for both.
For players with makeup.
The system looks at the players current stake and current results. If results are higher than stake + makeup a split function is generated. This emails the player telling them the amount that they should transfer to admin. The figure is based on the total profit, total makup and the agreed split % (this figure is entered by admin on the userpage).
So, player B has a total stake of 1500, 100 makeup, and accepted results of 1700. Player B has a profit split % of 40% (the % split is the % retained by the site).
The player is emailed requesting that they withdraw their share of profits and transfer our share of profits + makeup. For the purposes of the above example these figures would be:
\ to player
| | | | |