To do list: - Interactive Bible Home Page www.bible.ca



Section I: The user side interface:

1. Any access to data by anyone requires the recaptcha thing. that way all the data will be unavailable to web crawlers. In other words, when a seeker wants to find a church, they must first pass the recapticha test. this places all searching behind the recaptcha. They will have to do recaptcha a second time for any data base changes or updates.

2. can you make the world map and map of usa larger? I cannot read the text although it is high resolution. The canada map is easily readable, but the usa map is too small. can you increase the pixel size for the screen before you remap the individual states for the data base? Maybe it is because I am using a widescreen 1680 x 1240 resolution setting on my video card.

3. see: they have a mouse rollover feature that we could add to the usa map. I really like the map I modified. I like the higher quality resolution, but with mouse rollover it would give direct feed back on where they will go when they click.

4. For the usa states, have the man places in the middle. I would suggest that you use a default search radius for the usa states as 100 miles. Perhaps 30 mile radius for states where many churches are like texas, alabama, florida, tennessee, kentucky, california, arkansas, Indianna. the rest use a 100 mile radius

5. Add additional search radius’: 150 miles. 500 miles, 800 miles, 1000 miles. The higher search radius is needed for europe and china, middle east etc.

6. When you click on the Canadian provinces, do a bit of extra effort for my country. There are so few churches. I have used photo paint to kind of give a general idea where the churches are located. In BC have the man (stick man that you can move) placed over Vancouver with a default search radius of 50 miles. In Alberta stick man equidistant in the middle of the three churches (a town called “Brooks alberta”) at a search radius of 150 miles.

7. Make sure churches/emails or hotlines are listed in alphabetical order based upon city.

8. Display only the closest 5 churches to the stick man in the inset info box at the right. Yes in tampa 20 churches will have an icon, but only list the closest 5 churches to the stick man. This is so that people do not try to get a listing of all churches in a state or in the country (if searching for 1000 mile radius)

9. When no church is found within the search radius the following message is displayed in the white box at the right: “Sorry, no Churches found in a 10 mile radius of (34.39105,-85.60822 )” Change this message to: “Sorry no churches found within a 10 mile radius of the yellow man. Either increase the search diameter to 50 miles or use the mouse to drag the yellow man to a new location.

10. menu at the top: Line 1: Help and Search Tips (larger text) takes you to: /directly/help.htm

line 2: Home, New Search:(directly beside place they type in address), You are searching for [drop down box], search radius from your home (miles): [drop down box]

11. Starting pages for. Remember there are actually three starting pages: 1. searching for a church, 2. searching for an email helper, 3. searching for a hotline: This text is on the start page: “Postal Code or Country or City, Country or City, Province, Country or Address, City, Province, Country” Change it to: “Type in your own address here: street, state, country”. Just above this: “Tell us where you live and we will find the closest church to you!

12. menu at the bottom: Use this text at the bottom of the page: “Update any church listing or Add a new church or Delete a church”. It is a single hyperlink that takes you to: /directory/update.htm on that page I will have an html page that will give further information and then direct links to what they want to do. (Delete the “contact us” link at the bottom of the page. Seekers will use this instead of the person in their own home town)

13. I would like to have a scale in miles on the map at the bottom of the map. this would be helpful.

Output data for SEARCHING FOR A CHURCH page:

This is the way the balloon callout gives text on the map:

Hamilton

126 Ottawa Street North

Hamilton, Ontario L8H 3Z1 Canada

Phone: (905) 575-4564

bible.ca/churches/hamilton-church-of-christ.ht

Directions Zoom Save to My Maps

Edit This Church

Change this to:

[petname]

street

city, state, zip

Phone in church building: [church phone]

url

assembly details

Sunday Bible study: [data]

Sunday Communion service: [data]

Sunday evening: [data]

Midweek Bible study:[data]

Note to david: blank data is not displayed. this is easy for url, if there is not url then it is blank, but service times is a bit more complex. We want to add the words: “Sunday Bible Study:” to the data record: “10:30 AM” But if they have no service times in the data base, then the words, “Sunday Bible Study:” should not be displayed.

display one contact if available: either 1 or 2 or 3, which ever is first. display name, email, phone number. (if one is blank, but two is filled in, then use 2. Use 2 only even if three is filled in.

photo

last update: (this will be helpful to members of the church wanting to know if the data is recent while on vacation saving a lot of time. They would chose a church with recently verified data over one that has never been verified.)

===================

Output data for SEARCHING FOR AN EMAIL BIBLE CORREPSONDENT page:

Email a member of the church meeting at:

street, city, state

[contact 1 name and email]

[contact 2 name and email]

[contact 3 name and email]

note to dave: the form would be that you simply display their name and when they click on the name of contact 1, it is a hot link to and email address. Also you display only those records that have a name and an email address attached to the name.

Many records do not have any contacts. When searching for email helpers the data base will not display a church record that has not contacts. If a church record has one name + email you will display that one contact regardless of if it is in contact 1 or contact 2 or contact 3.

Example 1: if a record is the following:

[contact 1 Mark Copeland]

[contact 2 steve rudd and bible@bible.ca]

[contact 3 david Duncan and david@]

you would not display contact 1 because it has not email address, but you would display contacts 2 and three. (you and I)

Example 2: if a record is the following:

[contact 1 Mark Copeland and mark@]

[contact 2 blank]

[contact 3 david Duncan and david@]

you would not display contact 2 because it is blank, but you would display contacts 1 and 3. (Mark and you)

Example 3: if a record is the following:

[contact 1 Steve Rudd]

[contact 2 blank]

[contact 3 david Duncan and david@]

you would not display contact 1 because, although mark gave his name, he did not supply an email address, do not display 2 because it is blank, but you would display contact 3 only. (you)

Example 4: if a record is the following:

[contact 1 Steve Rudd]

[contact 2 blank]

[contact 3 david Duncan and 903-489-4855]

The seeker would not even see the record at all, because contact one gave no email address and contact 2 is blank and contact three only gave a phone number. So this record would not even get a “email icon” on the map. Only those churches that can be reached by email will show up this way.

Output data for SEARCHING FOR A BIBLE TELEPHONE HOTLINE page:

Telephone a member of the church meeting at:

street, city, state

Call [contact 1 name] at: [phone]

Call [contact 2 name] at: [phone]

Call [contact 3 name] at: [phone]

Note to David:

You would display their name beside their phone number like this:

Example 1: if a record is the following:

[contact 1 Steve Rudd bible@bible.ca]

[contact 2 blank]

[contact 3 David Duncan and duncan@ 903-489-4855]

The output would be displayed:

Telephone a member of the church meeting at:

[street, city, state]

Call David Duncan at: 903-489-4855

Example 2: if a record is the following:

[contact 1 Steve Rudd bible@bible.ca 905-575-8437]

[contact 2 Mark copeland 949-959-8932]

[contact 3 David Duncan and duncan@]

The output would be displayed:

Telephone a member of the church meeting at:

[street, city, state]

Call Steve Rudd at: 905-575-8437

Call Mark Copeland at: 949-959-8932

===================

Section II. Data base Management:

1. We will begin sending out requests for email confirmation every three months. This is about how often I have done it in the past manually.

2. We need a total of four last updated fields, One for the record itself and one for each of the three contacts. The record last updated field, will be the last time someone hits either the “confirmed” button, or make changes I accept as moderator. The three contact records will be the last time a contact hits their hot link we send them. We send them an update request every three months. If an email address does not bounce, but has been “abandoned” because the person stopped using it but will never check it again, I must know.

3. There needs to be a way so that when I request people to validate their emails by replying, that I can get a listing of those emails that have not replied, or come back bounced.

4. Also need to find a way to send a ping out to each email, so when a bad one comes back for a local church, the server sends a second email out asking for a replacement email for the bad one that is attached to the contact. The email would say: The email address for David Duncan bounced: david@. Please click here and update the David Duncan’s new email address.

5. There needs to be a master admin page where I can output unlimited quantities of data in any way possible. For example, listing out all churches within a single state or country.

6. If someone hacks the system: Data can easily be manually restored by the archives of the data base that are emailed to me weekly. It is important that I can get a tab delimited file to import into access. No need for fancy exchanges between access and the data base. I just need a weekly tab delimited file. I also need a way to trigger this manually so I can start working at any time I need to without waiting up to six days to get the latest data.

7. I need to know how to download updates I make with access. I will export a tab delimited file and ftp it down to the webserver.

8. URL’s. David I was surprised to learn that I have now collected over 1000 church urls!!!!! Have the data base create a permanent page in the form of standard URL that lists all the church websites that I can have xenu go to in order to check which websites are invalid. This would be an administrative page only and not for public use, but inside use only. I could point xenu to that page and it would check every site! Or I could just click on each of them manually while watching Bill O’reilly. Very cool and easy!

Section III. Updating the Data base:

1. When someone wants to add a new congregation, they need to do a search first on a separate page to make sure they are not submitting a duplicate record. Instruct them that if they find their church, or an old one where they used to meet, they should click on the "update" link for that church and not use the "add new church" form. Of course many will not check to see their church is already listed and just add a duplicate. When they add the data, they are given other churches that are geocoded within 10 miles to see if their church is listed. or given a list of churches of the same city. if they click on that church, they can transfer the data to the existing record. Perhaps easier, the data base allows then to add a record and when they hit submit, if any of the data fields in "city", "church phone number" or "assembly address" match, it displays that data record and asks them if they want to append the data to the existing record they did not know existed, or create a new one.

2. Contact phone numbers and email address are not permitted to be duplicated and must be different from the church building phone number. No two email addresses are allowed to be the same. Many churches list their three contacts with the identical email address and even phone number. This is very counterproductive.

3. There needs to be a way to make sure that when data is entered wrong (namely email and home phone numbers) that it doesn’t allow them. Specifically, if they use a home phone number that is the same as the church building as their home phone number, a note saying: "You cannot use the phone number in the church building as a contact person, use their actual home phone number. If the church does not have a phone in the building, then leave it blank and only use personal home phone numbers." For emails: "You cannot use the same email more than once. Use personal and unpublished emails. Do not use email address that are on any websites. Email addresses like Info@ or webmaster@ are automatic targets of spam. Do not use them on bible.ca."

4. After someone has added or modified a new church, offer them the opportunity to add a second church without starting from the beginning. once they are in, copy the references data and their name phone and email into the second new church record they are creating. This would be slick and would facilitate people making updates easily while watching TV.

5. There also needs to be a place where preachers, who move every three years, can search for themselves. This would be a place where they type in their last name only and the data base would search all three contact fields for their name and display the records, with a hot link to modify it. Often one preacher will be listed at four different churches all over the place because he never removed himself from the last church.

6. I agree that tokens mailed out by the server will expire. But why not make it one hour. If they are really wanting to do an update, live on the fly, they should have immediately checked their email. You could state in the email: this will expire one hour after you requested it. If it is expired, go back and start over.

7. There needs to be a token that will not expire even if email address is invalid. Every three months I will be sending out an auto email asking them to click on this link to confirm. For trusted people already in the data base, I see nothing wrong with giving them a token that will last a year or so based upon their name. This way if their email address is changed and they saved the token, they can update their own email address after the old one has been killed. This is quite helpful.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download