share code between frontend & datahub (stop code duplication)

[GoogleCodeExporter]

I've been putting this off... and now it's time: there's a number of
algorithms that need to live in both the frontend/ and datahub/ and
we haven't selected a method to share code between them.

why not reloc datahub under frontend?  datahub isn't a frontend, and
it's scary to me, to require that it adhere to frontend/ requirements,
whatever they are.  Obviously, we can 'give in' and do this.

what sorts of algorithms are shared?
 - Base fieldnames/mappings, customer ID, location +1000 hack, etc.
 - gspreadsheet parser (frontend checking tool)
 - autocomplete file reader/writer
 - mergekey / dedup code (for when we dedup in the pipeline)

labeling this as critical because otherwise the copied code will start
to diverge, esp. parse_gspreadsheet-- which now lives in two places.

ideas welcome!

Original issue reported on code.google.com by adam.sah on 11 May 2009 at 3:42

[GoogleCodeExporter]

Original comment by adam.sah on 12 May 2009 at 5:01

• Added labels: Geo

[GoogleCodeExporter]

Original comment by adam.sah on 13 May 2009 at 6:59

• Added labels: Crawler-Pipeline

[GoogleCodeExporter]

Original comment by adam.sah on 26 May 2009 at 5:28

• Added labels: CrawlerAndPipeline

[GoogleCodeExporter]

Original comment by adam.sah on 26 May 2009 at 7:49

• Removed labels: crawler-pipeline

[GoogleCodeExporter]

downgrading priority since it's not strictly a launch blocker.

Original comment by adam.sah on 8 Jun 2009 at 3:36

• Added labels: Priority-High
• Removed labels: Priority-Critical

[GoogleCodeExporter]

ain't gonna happen... deferring...

Original comment by adam.sah on 11 Jun 2009 at 1:56

• Added labels: Milestone-Release2.X
• Removed labels: Milestone-Release1.5

[GoogleCodeExporter]

Original comment by adam.sah on 17 Jun 2009 at 6:53

• Added labels: Maintainability

[GoogleCodeExporter]

Original comment by adam.sah on 28 Jun 2009 at 4:25

• Added labels: Milestone-Roadmap
• Removed labels: Milestone-Release2.X