Rewrite ETL readme and use consistent data types in tests

Per the discussion in #852 this updates the ETL readme to make the string data type much more explicit, and it also now specifies the lower-case. Some rationale for inverting this map is also included.

Note that I have not tested any of these tests yet, can travis verify the correctness of them or do I have to set up all of these environments to check them?