Rainer Simon

Try out what we can do with [ElasticSearch GeoHash grid aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/search-aggregations-bucket-geohashgrid-aggregation.html) (using the `representative_point` field as input), while we need to wait for a geo-aggregation that supports shapes.

Some form of mechanims that collects all issues that occured during the import (like [malformed properties](https://github.com/pelagios/peripleo2/issues/53)), so we can presents to the user, E-mail to the data publisher, etc. Needs...

This is more of planning issue (that will later be split into a range of implementation tickets). Anyways: we'll need a (public) validation endpoint where people can test their datasets...

The `requestCache` parameter in Elastic4s doesn't really seem to have much effect. (Perhaps if we start trying with more data.) But we should think about caching at some point, in...

E.g. to avoid object dates in the future

Make sure we can handle ground plan overlays in the data model. Should work for: - (JPG) image files - Pre-tiled image sets In terms of the model, use the...

Make sure we have everything in place (conceptually & data-model-wise) so we can deal with iDIG dumps in the future.

E.g. Bing, or perhaps configurable tile URLs? (Google probably not an option due to Terms of Service.)

When suggesting to auto-annotate identical toponyms in the text annotation area, Recogito looks for exact matches of "[placename] ". E.g. when annotating "Sardis", Recogito would suggest all occurrences of "Sardis...

In the text annotation are, it is currently not possible to annotate toponyms that cross "intentional" line breaks (i.e. those that are present in the source text, as opposed to...