| This project has been viewed 1010
times and was posted by percaroe from United States. |
|
| Start date : 14 Mar. 2008, 12:34 |
End date :28 Mar. 2008, 12:34 |
There is 1 registered bid. |
| Project number : 236460 |
Project category:Software Database development |
| This is the first project that this owner has posted on Freelance Programming. |
Description :
Project Goal(s): To build a graphically and visually dynamic website that effectively promotes the YSC to all prospective membership groups. To build a website with multiple layers of user-friendly functionality that (1) makes it easier for members to participate in club activities and (2) makes it easier for executive members to administer club business.
Sub goal: Two partially complete YSC website currently exist. If possible, we would like to build a new website from or upon one or both of these existing platforms.
Objectives:
1. Create static content and design for the website that (1) is contemporary, visually dynamic, culturally relevant and that (2) promotes and provides information about the club to prospective and current members
2. Build an events engine that regularly posts upcoming events to the website and allows general users to post and edit events.
3. Create three unique booking systems for the club’s Clear Lake facility, Lake Tahoe Facility and City/Outdoor Activities/Other Events.
4. Create a forum for membership postings with member login
5. Create a photo database and a system for uploading photos with member login
6. Build a membership engine for processing new and renewing memberships
7. Build a membership login function to support engines, booking systems, forum and photo database noted above
8. Create a live membership database to synch with engines and functions noted above
9. Build a comprehensive backend to support the live database, engines, reservation systems and user friendly administration functions
Requires an understanding of: PHP 5 (Object Orientated Programming Experience)
JavaScript and AJAX frameworks (preferably Dojo Toolkit) RDBMS (Relational Database Management System), Photoshop and relational database structures.
|
Deliverables :
1. Event Engine
1. Predesignated Templates
1. Single day event
2. Multi-day event
3. Clear Lake Non-party weekend
4. Clear Lake Party weekend
2. Demographics for Form
1. Event title (long):
2. Event title (short):
3. Recurring event tag:
4. Start date:
5. Start Time:
6. Number of nights:
7. Price (member):
8. Price (guest):
9. Complete event description:
10. Brief event description:
11. Capacity:
12. Guest per member limit:
13. Home page priority:
14. Advance reservations required?:
15. YSC membership required?:
16. Contact person:
17. Online RSVP's begin on:
18. Online RSVP's end on:
19. Online cancellation deadline:
20. Additional Demographics must be allowed to be placed here.
2. Central Database (CDB)
1. membership database which defines
1. Name of primary, spouse/ children
2. Phone (Phone and Cell)
3. Address
4. Membership number
5. Member since
6. Email
7. Newsletter preference
8. Expiration dates
9. Comments field
10. Many more may come, must be dynamically modified
2. CDB must align with various event DB’s via PHP scripts based on rules specified below.
3. Update Profile
1. All emails offer an update profile
2. Button on website that initiates an email to update profile
4. Event databases (spec below) (tbd by admin.) is this one or three Booking engine?
1. Booking Engine
2. Clear Lake (spec below)
3. Tahoe reservation system
5. SF events/ Outdoor events
6. New Membership Process
1. Editable online form that automates an email to Renee and sends form to database
2. Renee checks form and when appropriate initiates a phone/ email member to confirm details
3. Renee (or proxy) will adjust status to approve
4. CC form online which waits to charge until status to approve (how hard is this?)
7. Renewal Process
1. Allow and encourage membership updates via the web
2. Check dates when reservations are made for events (CL/ Tahoe/ SF/ Events) and if dates fall within set parameters (30 days until membership expiration or membership past due). (Pop-up when one is expired that only allows renewal page)
3. Allow one/ three/ five year options
4. Allow to change status or family or single
8. Payments
1. Checks against central database for membership status; will offer membership renewal if within time frames (30 days until renewal or past)
2. Allows payment via credit card
3. Send confirmation email as receipt
4. Generate reports for specific events and aggregate
9. Allow for a report to mail merge to address label system to send physical mail
1. Separate people with a note in merged tag to designate membership status
3. Clear Lake Specifications:
1. Name (Primary/ Spouse/ Children) / Guest Name (s)
1. System must have unique identifier (Username/ password) to access reservation system (Note: do we allow each member to have a unique email address? When spouse signs up does the response go to spouse or to the primary email address?)
2. System must allow Member or Member spouse to sign up for events, but only allow defined number of guest per member attending.
3. All payments must be made by Member.
4. Must be able to allow variable child pricing separate from adult
5. Must have a checkbox that links to a liability waiver with an unchecked checkbox.
6. Must have start and end dates for signups on all events, except weekday stays.(Note- is this a separate event or one big event- how hard is this?)
2. Phone (Phone/ Cell)
3. Email
1. Allow for email confirmation
4. Event Name
5. Date Options- 2 day/ 3 day/ weekday/ variable day
1. YSC has several options for the Cabin- partial day, one day, two day, three day and weekday. Each option variable must be accessible when form is created and for members to choose per individual.
2. Arrival Time/ Date per individual
6. Boat Donation Structure
1. Rate structure TBD by EC (this is in flux)
7. Chores (this is a wish list item)
8. Age Range
1. Notification that party weekends are not available/recommended for certain age ranges- with a pop-up window or in a confirmation page (this could also be grayed out for party weekends)
9. Car Pool
1. People who need are displayed in the events page (location /email/ desired departure time/ phone)
2. People who have and how many seats (location /email/ desired departure time/ phone)
3. Ability to modify reservation
10. Boat Docking
11. I will pay by check at Clear Lake
12. Reporting
1. Must allow an easy to access / print membership list that can be used by reservationists and cabin master
2. With all above fields: name/ number/ payment/
3. Must show payment for Cabin Master
4. Ideally has a field for chores
5. Boat Pre-payment field by trip or per hour (TBD by EC)
13. Current (Johan) System lacks:
1. allows any user in the world to reserve for Clearlake there is no reservation cutoff time
2. does not distinguish between single and family members
3. does not apply children's pricing
4. does not determine pricing for partial weekend attendees
5. does not inform the cabin master that membership dues need to be collected
6. does not allow one to modify or cancel their reservation
7. does not facilitate carpooling
4. Tahoe Reservation:
1. Name (Primary/ Spouse/ Children) / Guest Name
1. System must have unique identifier (UN/ password) to access reservation system
2. System must allow Member or Member spouse to sign up for events, but only allow defined guest per member attending.
3. All payments must be made by Member.
4. Must be able to allow variable child pricing separate from adult
5. Must have a checkbox that links to a liability waiver with an unchecked checkbox.
2. Phone (Phone/ Cell)
1. This will allow for announcements via SMS or call.
2. Announcements may be tied to 511 for road/ weather announcements (forward looking statement based on 511 roadmap).
3. Email
1. Allow for email confirmation
4. Room Options- allow room reservation
5. City Events / outside events:
1. Name (Primary/ Spouse/ Children) / Guest Name
1. System must have unique identifier (UN/ password) to access reservation system
2. System must allow Member or Member spouse to sign up for events, but only allow defined guest per member attending.
3. All payments must be made by Member.
4. Must be able to allow variable child pricing separate from adult
5. (ie. Lucia)
6. Must have a checkbox that links to a liability waiver with an unchecked checkbox.
7. Must have start and end dates for signups on all events
2. Email
1. Must allow email confirmation as a receipt.
3. Cell
1. This will allow for announcements via SMS or call.
|
Ownership :
we just want access to the code if we need to modify in the future
|
Support :
if stuffs broken we'll need it fixed
|
|
 | File name : YSC Spec sheet website 030508.doc | | File size : 60.5 KB | | Description : YSC Website |
|
