Holiday booking system for a social club who rent 5 holiday units. Members - secure login - book online - at school holiday time, only one week can be booked - non school hols more than one week is OK - weekly bookings are Mon to Mon and can be booked 12 months in advance - weekend bookings are Fri to Mon and can be booked 1 month in advance - Easter bookings are from Mon to Easter Tues then Tues to the following Mon. School holiday rates for these 2 weeks - a calendar for each unit that shows dates when unit is booked, this will be inserted in a html page that I build for each unit - online payment processing for credit cards through StrataPay ([url removed, login to view]). - an availability overview page. The member would select a particular month, up to 12 months in advance, and one page will show all units with their availability. Admin - keep tally of member's past bookings (they have a rule that you can't book two peak periods in one year or consecutively, ie school holidays) - member registration approval / edit / delete - booking approval / edit / delete - view payment info, ie deposits due and paid and balances due - admin able to override system and make a unit unavailable without payment showing (to allow for cleaning/maintenance) - each unit has a different booking rate for 1 week, weekend and holiday bookings The process will be 1. Member requests booking online - unit can't be booked if 'unavailable' 2. Email notification to admin, where it is approved/denied. If approved, an email goes to member requesting a deposit be paid thru StrataPay. 3. Email notification to member 35 days before holiday date, reminding final payment is due. 4. Upon final payment, holiday unit manager is emailed with booking details. There are about 500 members and some of these make up the admin group, so on the signup approval in admin, a check box for admin priviledges. Site access. The home page should be the only viewable page unless you are logged in.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
Linux, php, MySQL