^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.
@@ -14,21 +20,17 @@
* __categorization__
+ will rely on pigeonholes or a duplicate of pigeonholes that is exclusive for listings use.
!!YellowpagesPackage Tables
-* __yellowpages_groups__
-**group_id
+* __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)
-**group_id (optional)
**parent_id (optional - a content_id)
+**description
** url
-** url_title
-** phone_main
-** phone_mobile
-** fax
** email
-** im (chat id)
+** im_id (chat id)
** im_type (chat network)
** address
** city
@@ -38,16 +40,25 @@
** postal code (this is a universal term)
***international
***index for fast search
+*__yellowpages_persons__
+**yellowpages_id
+**firstname
+**lastname
* __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 )
+**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.)
*** 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