Martin Czygan

Thanks for the review and please let me know, if there's a way to make them less tough. The set is basically a random shuffle of citation strings from crossref.

@kermitt2 - would it be better, if I prepare another batch?

Thanks for the bug report! I'll prioritize the improved error reporting, which I meant to implement for some time now. Apart from that, I do not see any error (and...

Some related discussions in: * https://github.com/elastic/elasticsearch-py/issues/241 * https://github.com/elastic/elasticsearch-py/pull/704 and: * http://jijeshmohan.github.io/post/compress-http-request-in-go/

Great point. While reading https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-routing-field.html#_making_a_routing_value_required I think a custom routing value would not simplify things - they should be used at index and query time, etc. The way I see...

Sorry for catching up with this so late. Currently it is not possible, but is sound like an interesting addition.

Interesting idea. I did not have a use case for it and cannot implement / test it at the moment, but I am open to PRs anytime.

Today, I discovered https://www.repostatus.org/ - maybe useful for setting expectations?

> CrossRef - has API but no official regular bulk dump [We](http://ub.uni-leipzig.de/) have been working with the [crossref API](https://github.com/CrossRef/rest-api-doc) (for a [search infrastructure project](https://finc.info)) since early 2015 and we found...

> Are you hosting the data anywhere - can you share it? No, at the moment, we only use the crossref data for building an index for a couple of...