^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.^

!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, description, body text
** etc, magical liberty structure
*__geo__
** adds global position data
**joined on liberty_content
* __yellowpages_types__
** type_id (a number)
** type_desc (set by admin)
*** person
*** business
*** item
*** historical site
*** personal...
* __yellowpages_groups__
**group_id
**king_content_id (a primary listing of a group of listings keyed to a yellowpages entry/liberty_content entry)
* __yellowpages__
** content_id (keyed to same on liberty_content)
** type_id
**yellowpages_id (pretty)
** url
** url_title
** phone_main
** phone_mobile
** fax
** email
** 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_hours__
+ would it be better to break this out with cols like: start_time_1, start_time_2,... start_time_7
+ nice that this is separate - for example people types wont need hours.
**content_id
**day (0-7) ( day 0 for special cases and holidays )
**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_relationships__
+ this is for building relationships between listings. a listing could be a main office, repair center, kiosk, distribution center, etc.
**relationship_id for indexing and quick retrieval
**yellowpages_id - what listing is for the group
**group_id - the group this content is related to
**the title of this relationship

!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?)



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