Skip to main content

Data Hub

Project description


  • Datahub is a tool that allows faster download/crawl, parse, load, and visualize of data. It achieves this by allowing you to divide each step into its own work folders. In each work folder you get a sample files that you can start coding in.
  • Datahub is for people who found some interesting data source for them, they want to download it, parse it, load it into database, provide some documentation, and visualize it. Datahub will speed up the process by creating folder for each of these actions. You will create all the programs from our base default template and move on to analyzing the data in no time.

6 Rules for Data Privacy

  1. Sensitive, and possibly inaccurate, information may not be used against people in financial, political, employment, and health-care settings.
  2. All information should not be forcing anybody to hide or protect them self against improper information use that significantly limits persons ability to exercise his/her right to freedom of association.
  3. Implement a basic form of information accountability by tracking identifying information that identifies a person or corporation and could be used to held that person/corporation accountable for the compliance.
  4. There should be no restriction on use of data unless specified by laws and these privacy rules.
  5. Privacy is protected not by limiting the collection of data, but by placing strict rules on how the data may be used. Data that can be used in financial, political, employment, and health-care settings cannot be used for marketing and other profiling. Strict penalties should be imposed by for the breach of these use limitations. Actions that involve financial, political, employment, and health-care settings decision must be justified with reference to the specific data on which the decision was based. If the person/corporation discovers that the data is inaccurate, he or she may demand that it be corrected. Stiff financial penalties should be imposed against the agency that does not make the appropriate corrections.
  6. Achieve greater information accountability only by making better use of the information that is collected, retaining the data that is necessary to hold data users responsible for policy compliance. Build the system that encourages compliance, and maximizes the possibility of accountability of violations. Technology should supplant the rules because users are aware of what they are and because they know there will be consequences, after the fact.

Install DataHub

The best way to get started with datahub is to install it in the following way. Setup virtualenv which will keep the installation in a separate directory:

virtualenv --no-site-packages datahubENV
New python executable in datahubENV/bin/python
Installing setuptools............done.

source datahubENV/bin/activate

Create DataHub based project

Datahub is a paster template so you run it as follows:

paster create --list-templates
paster create -t datahub

You should see something like this:

paster create -t datahub

Selected and implied templates:

 PasteScript#basic_package  A basic setuptools-enabled package
 datahub#datahub            DataHub is a tool to help you datamine(crawl, parse, and load) any data.

Enter project name: myproject
  egg:      myproject
  package:  myproject
  project:  myproject
Enter version (Version (like 0.1)) ['']: 0.1
Enter description (One-line description of the package) ['']: my project
Enter long_description (Multi-line description (in reST)) ['']: this is long description
Enter keywords (Space-separated keywords/tags) ['']: datahub dataprocess gov
Enter author (Author name) ['']: myname
Enter author_email (Author email) ['']: myemail
Enter url (URL of homepage) ['']: mywebsite
Enter license_name (License name) ['']: gpl
Enter zip_safe (True/False: if the package can be distributed as a .zip file) [False]:
Creating template basic_package
Creating directory ./myproject
  Recursing into +package+
    Creating ./myproject/myproject/
    Copying to ./myproject/myproject/
  Copying setup.cfg to ./myproject/setup.cfg
  Copying setup.py_tmpl to ./myproject/
Creating template datahub
  Recursing into +package+
    Copying README.txt_tmpl to ./myproject/myproject/README.txt
    Recursing into crawl
      Creating ./myproject/myproject/crawl/
      Copying Readme.txt_tmpl to ./myproject/myproject/crawl/Readme.txt
      Copying to ./myproject/myproject/crawl/
      Copying to ./myproject/myproject/crawl/
      Copying to ./myproject/myproject/crawl/
      Copying download_list.txt_tmpl to ./myproject/myproject/crawl/download_list.txt
      Copying harvestman-+package+.xml to ./myproject/myproject/crawl/harvestman-myproject.xml
    Recursing into hdf5
      Creating ./myproject/myproject/hdf5/
      Copying READEM_hdf5.txt_tmpl to ./myproject/myproject/hdf5/READEM_hdf5.txt
      Copying to ./myproject/myproject/hdf5/
    Recursing into load
      Creating ./myproject/myproject/load/
      Copying to ./myproject/myproject/load/
      Copying to ./myproject/myproject/load/
      Copying to ./myproject/myproject/load/
      Copying to ./myproject/myproject/load/
    Recursing into parse
      Creating ./myproject/myproject/parse/
      Copying to ./myproject/myproject/parse/
      Copying parse.sh_tmpl to ./myproject/myproject/parse/
    Copying process.sh_tmpl to ./myproject/myproject/
    Recursing into wiki
      Creating ./myproject/myproject/wiki/
      Copying REAME.wiki_tmpl to ./myproject/myproject/wiki/
Running /home/lucas/tmp/lmENV/bin/python egg_info
Manually creating paster_plugins.txt (deprecated! pass a paster_plugins keyword to setup() instead)
Adding datahub to paster_plugins.txt

Go into the myproject folder and start coding. The folder structure looks like this:

|-- myproject
|   |-- README.txt
|   |--
|   |-- crawl
|   |   |-- Readme.txt
|   |   |--
|   |   |--
|   |   |--
|   |   |-- download_list.txt
|   |   `-- harvestman-myproject.xml
|   |-- hdf5
|   |   |-- READEM_hdf5.txt
|   |   `--
|   |-- load
|   |   |--
|   |   |--
|   |   |--
|   |   `--
|   |-- parse
|   |   |--
|   |   `--
|   |--
|   `-- wiki
|       `--
|-- myproject.egg-info
|   |-- PKG-INFO
|   |-- SOURCES.txt
|   |-- dependency_links.txt
|   |-- entry_points.txt
|   |-- not-zip-safe
|   |-- paster_plugins.txt
|   `-- top_level.txt
|-- setup.cfg

Get stared with your data project


Crawl folder is where you crawl data. You have two choices as far as downloading. For each choice there are pre-build files, so just follow this:


With wget you can download the files if the list of files is not big. There is a download_list.txt that will hold the url you want to download. You can specify wild cards like *.zip, *.pdf, *.txt etc. is a shell script that calls wget and downloads files. By default it will only download files if they are newer then what you downloaded, and it will only download the missing parts. This saves your bandwidth and does not re-download the whole files each time.

The only thing you need to do is edit download_list.txt:

cd crawl
#Edit download_list.txt and add url of files you want to download
vi download_list.txt

You second options is harvestman, see docs.


Parse is where you parse the files. This is a gray area where you take control. This can be as simple as unziping a file, or writing a simple script to replace some names, or some extensive parsing program. It all depends on the project data. Add the code to, or write your own parser and add the running code to so that later you just run:



Load is where you load your data to the database. There is a file that has a sample database structure for 4 columns. You can use that file as your starting point. It has everything from defining new columns, to setting up database and reading over a csv file in parse folder and uplaoding it to database. Read the and files and make special not where it says [CHANGE]. These are the portion where you changed the namem, add columns, tell it where the file is. When all done, just run it:


Above all folders there is a file called This files has a build in structure to go into crawl folder and start, then go into parse and run, and then go into load and run script. With this file you control the whole process. When its all ready, a user can get your project, install any necessary programs and just simply run:


This will crawl, parse, and load the data.


Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for datahub, version 0.8.90dev
Filename, size File type Python version Upload date Hashes
Filename, size datahub-0.8.90dev.tar.gz (11.1 kB) File type Source Python version None Upload date Hashes View

Supported by

Pingdom Pingdom Monitoring Google Google Object Storage and Download Analytics Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page