Sources manager

[alexprengere]

A possible new feature would be to have a tool for managing sources.

Today there is no easy way to make persistent changes in sources or sources meta-data from the command line, or from the Python API. The only way is either:

• to contact the developer to add a new sources
• to edit the Sources.yaml configuration file (which is really easy)

We could have something like:

$ SourcesManager add sourcename file headers_infos [...]
$ SourcesManager list
$ SourcesManager remove sourcename

These operations would just be a way to change the Sources.yaml file from the command line, and provide a tool to copy the data (or not) to the Python site-packages. Note that today you can already use, on the develop branch:

• --help to get a complete source list
• --verbose to get the exact stuff you have to put in the Sources.yaml to make the source permanent when using $ cat data | GeoBase --verbose

We could also integrate zsh autocomplete update (handled by the Rakefile in completion/ today).

[alexprengere]

I just shipped this feature on the develop branch, though this was originally planned for the next release. But since join clauses have been implemented (see #10), it really makes sense to have a source manager tool right now.

I decided to keep only one tool, so you have to use the GeoBase main script to administrate the data sources.

$ GeoBase --admin
---------------------------------------------------------------
(*) status     : display short data source status
(*) fullstatus : display full data source configuration
(*) drop       : drop all information for one data source
(*) restore    : factory reset of all data sources information
(*) edit       : add or edit an existing data source
------------------------------------------------------- SUMMARY

[ 0 ] Command (status/fullstatus/drop/restore/edit): edit
[ 1 ] Source name : 
...

Then follow the instructions. There are a few suboptions to --admin. If you want to skip a few questions you can do things like --admin edit airlines.