Add "datastore" app and move storage functionality from "cataloging"

[GoogleCodeExporter]

Rather than one "cataloging" app, I want a "catalog" app that acts as a
simple datastore and an "editing" app that presents editing interfaces on
the data.  The idea, for now, is that both "editing" and "discovery" will
speak to the datastore via Jangle (http://jangle.org/).

Original issue reported on code.google.com by gsf747@gmail.com on 6 Apr 2009 at 8:04

[GoogleCodeExporter]

On second thought, I'm thinking "datastore" and "cataloging" are better names 
than
"catalog" and "editing".  There's a pretty good sense of what the "cataloging" 
app
would entail, whereas "editing" is more ambiguous.  Also, "datastore" 
emphasizes the
dumb, no-ui-just-data-in-and-out nature of that app better than "catalog" would.

Original comment by gsf747@gmail.com on 7 Apr 2009 at 10:04

[GoogleCodeExporter]

Original comment by gsf747@gmail.com on 7 Apr 2009 at 10:05

• Changed title: Add "datastore" app and move storage functionality from "cataloging"

[GoogleCodeExporter]

reffed in r370

Original comment by gsf747@gmail.com on 7 Apr 2009 at 10:18