History of YellowpagesPackage
^NOTICE: This package is in development and not ready for live use. It is only available for bitweaver release R2. If you would like to help in developing this package you can check out module _bit_yellowpages from cvs. Talk with Will or Lugie on IRC about contributing code.^
!Tables Schema
This section is an attempt to clarify how the database structure will look running the listings package. This is a rough draft, and I will omit some things like id_seqs for now, and names of these things should change to meet bitweaver specifications.
* __liberty_content__
** tracks user ownership of the listing
** holds title of thing listed
** holds general description to accompany the listing
** etc, magical liberty structure
* __listings__
** holds content_id on liberty_content
** provides "type" of listing
** provides "rank" of listing
** more
* __listing_types__
** numerical value (linked in listings)
** types to be determined by admin
*** person
*** business
*** item
*** historical site
*** personal...
* __listing_urls__
** holds associated listing id
** url to link to
** title for url
* __listing_addresses__
** holds associated listing id
** title of address (what the location is to them)
** city
** state/province (perhaps we can check user country to figure out what to call this)
***need codes
**country
** postal code (this is a universal term)
***international
***index for fast search
**24hrs boolean
* __listing_hours__
**day (1-7)
**start time
**end time
**note for special cases - this should go somewhere else or be day 8?
!Brainstorm Discussion:
!!Schema
Street Number
Street Name
City
State/District/Region <-- how is this handled internationally, what are they called?
Country
Zip
Phone number <-- how to have multiple phone numbers? unlimited?
Fax number
Email Address <-- again how to have multiple
Listing URL
Cross Streets
!!!Other details only some kinds of listings have - how to deal with these?
Related Links
Hours
Price
Type <-- person, business, historical site, etc ?
!!Administrative
* Ability to switch user associated with listing (for editing purposes)
* Ability to turn on or off __rel="nofollow"__ SEO in all external links (perhaps this should be added to liberty)
!!Customer (Businesses/Things Listed)
* Masks email addresses behind web-based form or by some advanced robot-proofing method?
!!End User
* more...
!!Rankings
Put this type of stuff in another package or else liberty or an existing package
** provide numerical values for type of listing (linked in listings)
** adds a price to become a listing of this type
** provides sort order information for displaying pages with multiple listings
** associates optional information with each listing type (features which get turned on and off). This table simply defines whether or not these things are shown/available based on the rank of listing being viewed/edited/created.
*** web URL (numerical value determining the maximum)
*** attachments
**** images
**** audio
**** video
**** other files (pdf, spreadsheets, archives, etc)
*** addresses (numerical value determining the maximum)
*** phone numbers (numerical value determining the maximum)
*** email addresses (numerical value to determine maximum)
*** start date
*** end date
*** more... (possibly a way to admin-define these fields?)
!Tables Schema
This section is an attempt to clarify how the database structure will look running the listings package. This is a rough draft, and I will omit some things like id_seqs for now, and names of these things should change to meet bitweaver specifications.
* __liberty_content__
** tracks user ownership of the listing
** holds title of thing listed
** holds general description to accompany the listing
** etc, magical liberty structure
* __listings__
** holds content_id on liberty_content
** provides "type" of listing
** provides "rank" of listing
** more
* __listing_types__
** numerical value (linked in listings)
** types to be determined by admin
*** person
*** business
*** item
*** historical site
*** personal...
* __listing_urls__
** holds associated listing id
** url to link to
** title for url
* __listing_addresses__
** holds associated listing id
** title of address (what the location is to them)
** city
** state/province (perhaps we can check user country to figure out what to call this)
***need codes
**country
** postal code (this is a universal term)
***international
***index for fast search
**24hrs boolean
* __listing_hours__
**day (1-7)
**start time
**end time
**note for special cases - this should go somewhere else or be day 8?
!Brainstorm Discussion:
!!Schema
Street Number
Street Name
City
State/District/Region <-- how is this handled internationally, what are they called?
Country
Zip
Phone number <-- how to have multiple phone numbers? unlimited?
Fax number
Email Address <-- again how to have multiple
Listing URL
Cross Streets
!!!Other details only some kinds of listings have - how to deal with these?
Related Links
Hours
Price
Type <-- person, business, historical site, etc ?
!!Administrative
* Ability to switch user associated with listing (for editing purposes)
* Ability to turn on or off __rel="nofollow"__ SEO in all external links (perhaps this should be added to liberty)
!!Customer (Businesses/Things Listed)
* Masks email addresses behind web-based form or by some advanced robot-proofing method?
!!End User
* more...
!!Rankings
Put this type of stuff in another package or else liberty or an existing package
** provide numerical values for type of listing (linked in listings)
** adds a price to become a listing of this type
** provides sort order information for displaying pages with multiple listings
** associates optional information with each listing type (features which get turned on and off). This table simply defines whether or not these things are shown/available based on the rank of listing being viewed/edited/created.
*** web URL (numerical value determining the maximum)
*** attachments
**** images
**** audio
**** video
**** other files (pdf, spreadsheets, archives, etc)
*** addresses (numerical value determining the maximum)
*** phone numbers (numerical value determining the maximum)
*** email addresses (numerical value to determine maximum)
*** start date
*** end date
*** more... (possibly a way to admin-define these fields?)