Rainer Simon

__Note:__ seems to be a client-side navigation issue rather than a problem with the query, as initially thought. The 'referencing' filter seems to get lost in the UI as soon...

Hi @ChiaraPalladino, unfortunately, not really. Peripleo is still in a protoype-ish state. We haven't developed it any further in the past two years, and had to keep maintainance to a...

Hm - it's a really good question. I'll forward this on to the rest of team via E-Mail as well. They're not too Github-native ;-) Simple things first: in principle,...

@Conal-Tuohy That could certainly be an option. But I agree that the cost/benefit ratio depends entirely on how complex the translation would be. The Pelagios model is really simple: hardly...

Ah missed the point of OC already being available as JSON-LD. Indeed - that makes the transfer OC->triple store straightforward. I agree there'll certainly be interesting uses for SPARQL'ing into...

The search API is now fully wrapped with legacy interop.

Place API is now also fully wrapped.

P.S.: gazetteers currrently making use of broadMatch are: Cyprus, Libya, DEFC.

Note: in case of `inscription` the response is 750kB, so delay might be due to sheer size - retrieval, entity resolution, JSON (de-)serialization, etc.

__Note:__ we need to check how "large" items influence the ranking. Since we're using an aggregation, there's no TFIDF etc. I.e. something like the Iliad could overshadow every other relation,...