^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 wjames5 or Lugie on IRC about contributing code.^

!ToDo's
* Create tpls that match table schema
* How to verify hours data for each day in BitYellowPages
** loop through for days 0-6 ?
** require edit cycle for each day ? <-- easiest to build

!Tables Schema
This is the data tables schema for the yellowpages package. This does not include some things like id_seqs which will be derived as appropriate.

!!Non-YellowpagesPackage Tables
* __liberty_content__
** tracks user ownership of the listing
** holds title, description, body text
** etc, magical liberty structure
*__geo__
** adds global position data
**joined on liberty_content
* __categorization__
+ will rely on pigeonholes or a duplicate of pigeonholes that is exclusive for listings use.
!!YellowpagesPackage Tables
* __yellowpages_group_kings__
**group_id (keyed to a pigeonhole)
**king_content_id (a primary listing of a group of listings keyed to a content_id)
* __yellowpages__
** content_id (keyed to same on liberty_content)
**yellowpages_id (pretty)
**parent_id (optional - a content_id)
**description
** url
** email
** im_id (chat id)
** im_type (chat network)
** address
** city
** state/province (check what other countries and services call this)
***need codes
**country
** postal code (this is a universal term)
***international
***index for fast search
*__yellowpages_persons__
**yellowpages_id
**firstname
**lastname
* __yellowpages_hours__
**yellowpages_id
**day_id (0-n joins on yellowpages_days
**start_time
**end_time
**twentyfour (boolean)
**note (every day can have its own note? this is handy for holidays but over kill for the others.)
*__yellowpages_days__
**day_id
**day_title
++defaults: 0:Monday - 6:Sunday, 7:Holidays (generic), 8:Christmas, etc
* __yellowpages_phones__
** yellowpages_id
** phone_type
** phone_number


!Brainstorm Discussion:
!!Schema
Cross Streets -- should this be added or derived using a geo db

!!!Other details only some kinds of listings have - how to deal with these?
Related Links <-- maybe another field in meta
Price <-- for something like restaurants prolly want a separate package
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?)

!Feature requests
*filtering of search results by geo locations and the possibility of browsing the entries based on geo locations (mainly for entries that can have a location associated - companies, institutions etc.)
*possibility of fulltext switching to global internet fulltext search (read: fulltext via google for instance)
*the ability of setting any entry "Featured", which would bring it up in the browsing listings and searches
*item rating and comments
Page History
Date/CommentUserIPVersion
03 May 2007 (00:59 UTC)
schema tweak - move phones to new table
Will68.174.111.4732
Current • Source
Kozuch194.108.143.10831
View • Compare • Difference • Source
Kozuch194.108.143.10830
View • Compare • Difference • Source
Kozuch83.208.125.1429
View • Compare • Difference • Source
Kozuch194.108.143.10828
View • Compare • Difference • Source
Kozuch194.108.143.10827
View • Compare • Difference • Source
Will68.174.111.4726
View • Compare • Difference • Source
Will68.174.111.4725
View • Compare • Difference • Source
Will68.174.111.4724
View • Compare • Difference • Source
Will68.174.111.4723
View • Compare • Difference • Source
Will68.174.111.4722
View • Compare • Difference • Source
Will68.174.111.4721
View • Compare • Difference • Source
Will68.174.111.4720
View • Compare • Difference • Source
Will68.174.111.4719
View • Compare • Difference • Source
lugie70.224.212.20918
View • Compare • Difference • Source
lugie70.224.212.20917
View • Compare • Difference • Source
Will68.174.111.4716
View • Compare • Difference • Source
Will68.174.111.4715
View • Compare • Difference • Source
Will68.174.111.4714
View • Compare • Difference • Source
Will68.174.111.4713
View • Compare • Difference • Source
WaterDragon145.116.228.3412
View • Compare • Difference • Source
Will68.174.111.4711
View • Compare • Difference • Source
Will68.174.111.4710
View • Compare • Difference • Source
Will68.174.111.479
View • Compare • Difference • Source
Will68.174.111.478
View • Compare • Difference • Source
Will68.174.111.477
View • Compare • Difference • Source