Change analyzer

One approach to solving #73: making `keyword` the default analyzer. This way, new fields are just indexed literally, no tokenisation or turning into lower case, so the normal term match filter can be used.
The nice thing about this approach (compared to #89) is that it is simple and predictable, a search filters for exact matches. Examples:
`search?myfield=Alice` will *not* return annotations with myfield value `alice`
`search?myfield=bla` will *not* return annotations with myfield value `bla bla`

Yes, it boils, but the ES documentation is a bit enigmatic on this.
Look at the description of the [keyword analyzer](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-keyword-analyzer.html)

"Note, when using mapping definitions, it might make more sense to simply mark the field as not_analyzed" - Thanks ES :)