1. talesofthecocktail
1.1. rss
1.1.1. item coctail and culinary dream
1.1.1.1. link
1.1.1.2. comments
1.1.1.3. lunk
1.1.1.4. unhelpful categories
1.1.1.5. address in content / undetectable
1.1.1.5.1. limited automatic detection (jape)
1.1.1.5.2. need ui for identification corrections
1.1.1.6. time/date in content / undetectable (4h)
1.1.2. spirit of italy cocktail
1.1.2.1. title
1.1.2.2. link
1.1.2.3. link to comments
1.1.2.4. unhelpful categories
1.1.2.5. address in content / undetectable
1.1.2.6. time/date in content / undetectable
1.1.3. wordpress site organized around "posts"
1.2. parts (3 d)
1.2.1. parse address (1 d)
1.2.1.1. jape
1.2.2. ui for corrections (2d)
1.2.3. parse time (4 h)
2. infrastructure
2.1. basic setup (1d)
2.2. structure and styles (2d)
2.3. deployment (2d)
3. fudge factors
3.1. how complex an admin ui?
3.1.1. how many conveniences?
3.2. notifications?
3.3. familiarity with infrastructure?
4. theadvocate
4.1. Search Rss Feed
4.1.1. Kevin Hart at Baton Rouge River Center, Sat, Aug 11 8:00p
4.1.1.1. link
4.1.1.2. address/date in title
4.1.1.3. address geotagged
4.1.2. Bridal Show
4.1.2.1. location/date in title
4.1.2.2. link
4.1.2.3. geotagged address
4.2. parts (2d)
4.2.1. load rss
4.2.1.1. parse address (4h)
4.2.1.2. parse time (2h)
4.2.1.3. parse event title (2h)
4.2.1.4. solid event desc (4h)
4.2.2. identify link
5. offbeat
5.1. wordpress, story based
5.1.1. branford marsalis quartet
5.1.1.1. link
5.1.1.2. NOT event
5.1.2. courtyard kings
5.1.2.1. bacchanal wine
5.1.2.2. time date available
5.1.2.3. location linked and geotagged
5.1.3. problems happen maybe use html
5.2. parts (2d)
5.2.1. site
5.2.1.1. scrape html (6h)
5.2.1.2. identify time date (2h)
5.2.1.3. identify location (6h)
5.2.1.3.1. cache
5.2.1.3.2. follow and geolocate
5.2.1.4. good content (3h)