Recreation Properties back end property registration
| Recreation Properties Project edit | |
| |
Contents |
Back End Property Registration
- Project: LDS Church Recreational Properties Management Website
- Sub Project: New Registration of Recreational Properties, Sites, and Contacts
- Author: Joseph Lamb
- Date: February 20, 2010
Glossary
| Term | Definitions |
|---|---|
| Agent Stake Property Manager (ASPM) | The person called by the Agent Stake President to administer recreational facilities. |
| Agent Stake President | The stake president in charge of the property. This can only be one. This stake can be demoted to Sponsoring stake. |
| Sponsoring Stake(s) | There can be one or more. These stakes have prime functional use. For example, these stakes get to use the facility for Girls Camp if that is the prime function. These stakes can be replaced with non-sponsoring stakes. These stakes will be promoted to Agent stake. |
| Area Authority | The Area Authority that is in charge of the Sponsoring Stake. |
| Recreational Property | The property that contains sites and amenities for group to schedule, pay and use. A recreational property itself will not be scheduled; it is only a container. |
| Sites | Are under the Recreational property. Sites can be scheduled. Sites have amenities. There can be an unlimited set of amenities (rock wall, fire pit, tables). Groups will schedule and use sites. |
| Groups | One or more individuals that will use a site. Groups have one name, telephone, address, and number of individuals. Groups may have ward and stake affiliations. |
| Sites Usage States | A site can be set for 4 different states
|
| Amenity | Any attribute of a site that would be noteworthy to describe. Amenities are not scheduled. They include bathrooms, fire pits, and water sources. |
| Activity | A scheduled event that an individual or group can participate in. An activity can have one or many activity sessions. An activity may or may not contain a limit to the number of participants. Examples of activities include Lake Reservations, Lectures, Service Projects, Campfire or Rifle Range. Each activity may or may not contain one or more artifacts (documents that are necessary to provide to the group participating in the activity, e.g., Permission slip, Pack list, Volunteer sign up sheet, Maps). |
| Activity Session | A date and time-frame (start and end) when an activity is held. A session may or may not contain special remarks (e.g., Special Speakers, conditions or information). |
Project Scope
The new site (Recreation Properties Application) is the method that an Agent Stake Representative can use to set up a camp for use.
This subproject will be a back end administrative function. This site will be accessed by Agent Stake Presidents and the Agent Stake Property Manager (ASPM). This site can also be accessed by the Area Authority.
A new Facility will need to put in all the amenities, i.e. camps, cabins, swimming, pictures, boating, maps and directions, prices, and use schedule. The ASPM will set up their contact information and on-site property caretakers.
A Recreational facility will contain sites, contacts, and amenities. A site could be anything that will be scheduled like a cabin or pavilion. Sites will contain amenities like a rock wall, fire pit, and tables. A Site is where groups will stay. A group can be one or more individuals. Groups will be able to schedule the sites for use. One form will collect all the data.
The ASPM can set the recreational properties usage schedule for all sites, or the ASPM can set the schedule for individual sites. The ASPM will use the 4 site states of the property/site. Each site state can be set visually with a calendar. The ASPM will be able to set the site states also by data ranges. The ASPM will also set site states by recurring events, such as every Sunday is a None day. The ASPM can override the current reservation with another one.
Registering a new Recreational Property will also include a page to set up Sponsoring or participating stakes. There will be an unlimited number of sponsoring stakes. This will be one web form. Unit numbers will be used so the CDOL (Church Directory of Organizations and Leaders) and CMIS (Church Member and Leader Services data will always be current. There will be a check box for the agent stake.
In general, all business rules will be stored procedures. The Web Site interface will only be to display and set values. The adding and deleting of Recreational Properties, Sites, Users, and Photos will all be controlled by stored procedures.
This Registration process will be a Web Interface that will support Microsoft Internet Explorer, Firefox, Chrome, and Safari web browsers. The Operation Systems will be OS neutral (Linux, Windows, whatever).
Requirements
Add Property Details
Using the Coda Application with Recreation Properties will allow for full integration with the CDOL (Church Directory of Organizations and Leaders) and CMIS (Church Member and Leader Services data.
Description: This will be the main page after a log in for the Assigned Property Agent. The page will not allow others to access Properties, Campgrounds (camps) or campsites that are not assigned to them. This page will have a form to gather the information listed in the requirements table below (ADJUSTMENT NEEDED: reflect resources that can be scheduled, e.g., campsites, extra stoves, ropes course). This page will contain links or buttons to add new resources and assign contacts.
There will be a button on this page to "delete" all the resources and other associated information tied to the unit number of the property. The button will deactivate (appear deleted to the end user) all the campsites, contacts, amenities, billing, and other such information. This button will be used ONLY in testing. An undo button will allow for a re-activation of previous deactivated resources and information. In the live setting inactive information will be hidden and not used but will not be deleted by Agent Stake President or Agent Stake Camp Coordinator.
On the left side of the screen will be the summary information. The left pane will show the Campsites, Contacts, and Amenities. There should also be a preview button to show what the opening page will look like to the users who will schedule it. If you click on one category (Campsites, Contacts, and Amenities) the categories will expand. The link underneath will open up a page displaying the information.
From this page, the Agent stake will be able to view posts about user experience. There will be a check box to allow users to write posts or not.
It is conceived that the User who registers the new site will first add contacts. Then the users will add the Sites. Amenities will be added with only a prior site added. There will be a general property reservation fee. This page will also allow that to be set.
This page will allow the setting of the Property State. Again the Property States will be Prime, Mixed, Others, and None. Each state will have a color that associates it with the Property State. Prime will be blue. Mixed is Purple. Other is Red. And None is Gray. The Calendar widget will show a month at a time. The ASPM will set the state on the Calendar Widget. There is also a range. Here the user will set the prime function date as a range for start date to end date. The times on the range start and end date will be from 12:00 (noon). For example, if the ASPM picks June 1 to August 8 for girls camp, then the time recorded in the database tables is 2010-06-01-12:00:00.000 for the start time. This means that a new group can start using the camp at noon also.
| Req. # | Description | Data/Type (length) | Attributes |
|---|---|---|---|
| 1. | Property Unit Number | ||
| 2. | Agent Stake | Unit Number | |
| 3. | Map Info | Coordinates | Embedded |
| 4. | Recreational Satellite image | Image | Can overlay site and amenities |
| 5. | General Rules | Text | |
| 6. | Mission Statement | Text | |
| 7. | Add Photo button – Main photo | This will allow users to add photos. This will be a link to a page. | |
| 8. | Add New Contacts | Button or link to add new contacts | |
| 9. | Add New Sites | Button or link to add new sites | |
| 10. | Add New Amenities | Button or links to Amenities to a site. A site must exist before Amenities | |
| 11. | Add Posts | This check box will allow users to add post about their experience at the site. | |
| 12. | Localization | Site can change language file | |
| 13. | Change Language | Button to change the default language. | |
| 14. | Cost for Prime Function per day | This is the cost for one day reservation for Prime user (i.e. YW) | |
| 15. | Cost for Non Prime Function per Day | This is the cost for one day reservation for non Prime user (i.e. YM) | |
| 16. | Notices | Text. Use this space to display on the web site special news to potential users | |
| 17. | Cleaning fee | Amount for cleaning Fees | |
| 18. | Security Fee | Amount for Security Fees | |
| 19. | Calendar Widget Date and Time | Ability to set prime function dates and times. |
Add Contacts
Description: This Web page will add contacts who use or administer the sites.
Note: Most of this can be populated from the CDOL (Church Directory of Organizations and Leaders) and CMIS (Church Member and Leader Services data. There is no reason to store the data twice.
On the left side of the screen will be the Property Summary and navigation links listed in the Property Page.
| Req. # | Description | Data/Type (length) | Attributes |
|---|---|---|---|
| Member Number | Int | Required for autofill | |
| 1. | User First Name | Name | Required |
| 2. | User Last Name | Name | Required |
| 3. | User Address | Address | Required |
| 4. | User City | City | Required |
| 5. | User State | State | Required |
| 6. | User Country | Country | Required |
| 7. | User Postal Code | Postal Code | Required |
| 8. | User Email | ||
| 9. | User Home phone | Telephone | Required |
| 10. | User Cell Phone | Telephone | |
| 11. | Add Photo button | This will allow users to add photos. This will be a link to a page. | |
| 12. | Calling | Text | Populated from Church DB |
| 13. | Ward | Text | Populated from Church DB |
| 14. | Stake | Text | Populated from Church DB |
| 15. | Localization | Change Language | |
| 16. | Add and close Button | Add the user and close the form | |
| 17. | Save and Add Another | Add the user, clear the form and add another. | |
| 18. | Delete User | Delete the current user, blank the form. Before delete, request verification of actions. |
Add Resource
Description: These are the requirement for adding a Resource. A Resource must be associated with property. A Resource is anything that needs to be scheduled.
The left side will have the Category navigation system.
| Req. # | Description | Data/Type (length) | Attributes |
|---|---|---|---|
| 1. | Resource Name | ||
| 2. | Max Number of People | ||
| 3. | Calendar Widget | Set the State | |
| 4. | Add Photo button | This will allow users to add photos. This will be a link to a page. | |
| 5. | Amenities | ?? | |
| 6. | Rules | Text | |
| 7. | Cost for Prime Function per day | This is the cost for one day reservation for Prime user (i.e. YW) | |
| 8. | Cost for Non Prime Function per Day | This is the cost for one day reservation for non Prime user (i.e. YM) | |
| 9. | Security Fee | ||
| 10. | Cleaning Fee | ||
| 11. | Localization | Change Language | |
| 12. | Add and close Button | Add the Site and close | |
| 13. | Save and Add Another | Add the Site, clear the form and add another. | |
| 14. | Delete User | Delete the current Site, blank the form. Before delete, request verification of actions. | |
| 15. | Description |
Add Photos
Description: This page will add any photos to a Property, Site, or User.
| Req. # | Description | Data/Type (length) | Attributes |
|---|---|---|---|
| 1. | Add and close Button | Add the Site and close | |
| 2. | Save and Add Another | Add the Site, clear the form and add another. | |
| 3. | Delete User | Delete the current Site, blank the form. Before delete, request verification of actions. | |
| 4. | Description | ||
| 5. | Upload button | Button to find file on the local system. |
Database Tables
Note: Needs modification.
Rec_Property
Note: adjust based on Coda Application.
| Column Name | Type | Description | Foreign Key |
|---|---|---|---|
| Rec_prop_name | Name | Name of Property | |
| Rec_prop_Number | Integer | Unique Number | |
| Rec_Address | Address | ||
| Rec_City | City | ||
| Rec_State | State | ||
| Rec_Country | Country | ||
| Rec_Postal_Code | PostalCode | ||
| Rec_Agent_Stake | TextShort | ||
| Rec_Map_Info | TextShort | ||
| Rec_Sat_image | Text | XML link to files | |
| Rec_General_Rules | TextLong | ||
| Rec_Mission_Statement | TextLong | ||
| Rec_Main_Photo | Text | XML link to files | |
| Createdtadstp | Date | Time when the record was created | |
| Modifiedtadstp | Date | Time when the record was last updated | |
| Rec_Post | Char | Y/N | |
| Rec_Cost_Prime | Money | Required | |
| Rec_Cost_NonPrime | Money | Required | |
| Rec_Notices | Text | ||
| Rec_Security_Fee | Money | ||
| Rec_Cleaning_Fee | Money |
Rec_Site
| Column Name | Type | Description | Foreign Key |
|---|---|---|---|
| Rec_Prop_Num | Integer | ||
| SiteName | TextShort | ||
| SiteDescription | TextLong | ||
| SiteRules | TextLong | ||
| SitePhotos | Text | XML link to files | |
| SiteNumber | Integer | Unique | |
| SiteAmenities | Text | ||
| SiteLastClean | Date/Time | ||
| SiteState | Text | Open/Closed |
Contacts
| Column Name | Type | Description | Foreign Key |
|---|---|---|---|
| Con_FirstName | Name | ||
| Con_LastName | Name | ||
| Con_Address | Address | ||
| Con_City | City | ||
| Con_State | State | ||
| Con_Postal | PostalCode | ||
| Con_Country | Country | ||
| Con_Home_Tel | Telephone | ||
| Con_Cell_Tel | Telephone | ||
| Con_Email | |||
| Con_User_Ward | Text | ||
| Con_User_Stake | Text | ||
| Con_User_Calling | Text | ||
| Createdtadstp | Date/Time | ||
| Modifiedtadstp | Date/Time | ||
| Con_Photo | Text | ||
| Rec_Prop_Number | Rec table |
Rec_MasterCalendar
| Column Name | Type | Description | Foreign Key |
|---|---|---|---|
| Rec_Prop_Number | Integer | Rec table | |
| Start_Date | Date/time | ||
| End_Date | Date/Time | ||
| Prop_state | Prime, None | ||
| Createdtadstp | Date/Time | ||
| Modifiedtadstp | Date/Time | ||
| SiteNumber | Integer | Rec_Site |
Appendix
String, Database Columns and Values
Note: needs to be localized.
| Type | Value | Format |
|---|---|---|
| Date/Time | Date/Time | YYYYMMDD 24HH:MM:SS |
| Name | Varchar 30 | |
| Address | Varchar 30 | |
| City | Varchar 50 | |
| State | Char2 | |
| Country | Char2 | |
| PostalCode | Varchar 9 | |
| LongText | Varchar 1000 | |
| ShortText | Varchar 100 | |
| Telephone | Varchar 12 | For US DDD-DDD-DDDD |
| Varchar 30 | Must have @ | |
| Money | Local |