Rainer Simon

There are several ways in which the time histogram can be optimized (cf. issue #104, #26, #28). Another problem, however, is that our materials are starting to cover an enormous...

The various crosswalks for different types of content (places/people/objects/etc.) and formats (RDF, GeoJSON, etc.) and flavours (JSONL, single GeoJSON FeatureCollection, etc.) is beginning to become a bit of a mess....

The current selection design works well if only one or several (point) locations are selected. But what about: - selection of many points (currently looks horrible) - selection of polygon...

From Valeria: "[...] it is reasonable to assume that people that are looking for things in Alexandria/related to Alexandria will use it as search term. However, I think it is...

AFAIR, Pleiades adds makers (pleiades:1234->is_duplicate_of->pleiades:4321) when records are duplicates. Make sure we make use of these markers in the import process.

My personally most hated feature in v.1 - exploration mode - seems to have actually been used ;-) We need to have an equivalent. Hopefully something which is a bit...

We may need a strategy for when the controls area exceeds the screen height. This is less of an issue om desktop. But on mobile things get dense. E.g. when...

The time histogram is currently computed using a scripted aggregation: ```groovy f = doc['temporal_bounds.from'] t = doc['temporal_bounds.to'] buckets = [] if (!(f.empty || t.empty)) for (i=f.date.year; i

Currently a place reference is accepted as soon as it resolves. That means an object may refer to another object as a Place. We should make sure this is prevented...

The harvester currently downloads the response body, irrespective of the HTTP response code. We should make sure we only download for __HTTP 200 OK__.