Benjamin Geer

> we were planning this for the end of july. That would be great. No reason we can't test with both kinds of texts.

I downloaded 50 large books from [Project Gutenberg](https://www.gutenberg.org/). Each is at least 500 MB, many are over 1 MB. The current plan is to use [knora-py](https://github.com/dhlab-basel/knora-py) to create a simple...

This limitation is part of the current design of Gravsearch. In any case, it only makes sense to order by single values, not by multiple values. Is there a 1:1...

My suggestion was just a workaround, because as I said, if we do implement something like this, it will take time, and it sounds like you need a solution quickly....

If there can be more than one `Author` per `BibliographicReference` (or perhaps, more than one name per `Author`), how would you decide which name to use as the sort key?...

(a change to your ontology, or a change to your Gravsearch queries)

> Actually, we also have a `hasSequenceNumber` property for Author which allows to sort several authors in the right order OK, but I'm not sure it's possible to do that...

@gfoo OK, thanks, now I understand. If there is always a way to select only one value, then I think this becomes much easier to implement (otherwise I think we...

Also there doesn't seem to be any coverage information for this PR: https://github.com/dhlab-basel/Knora/pull/1011

> It is, but it is here: https://app.codacy.com/project/dhlab-basel/Knora/dashboard Is there something there about coverage for particular PRs? I can't find it. And when I follow the Codacy/PR Quality Review links...