Loris Sauter

Hi There With the hope to help @jbaiter to find and fix the culprits faster, here are some findings we had debugging what goes wrong when using IIIF 3.0: *...

I'm not entirely sure whether this is proper IIIF v3 usage, please bare with me, but adding a `seeAlso` on each canvas with an `id` pointing towards an external OCR...

Thanks, @jbaiter for your review. I will work on the requested changes during this week and especially try to come up with a dedicated IIIF v3 collection JSON for testing...

In our [application](https://github.com/dres-dev/DRES) we want to separate the [internal](https://github.com/dres-dev/DRES/blob/feature/xodus-storage/doc/oas.json) and [client-side](https://github.com/dres-dev/DRES/blob/feature/xodus-storage/doc/client-oas.json) openapi specs since third-party clients do not have to know about most of the internal calls. Yet, having openapi...

We did so by excluding the routes in the swagger-ui they shouldn't appear. Since one of the two openapi definitions is a subset of the other one, it was fairly...

Unfortunately there is no further information than a generic core dumped message. I did check in the user's home or the working direktory and none of the usual error logs...

Also, I would like to add that in certain use cases, it is desirable to have multiple instances of Cineast running on the same machine. At times the feature set...

This is a very good idea! Currently, the way to generate the OAS, one starts locally a Cineast instance and downloads the OAS from there. There is (or was at...

@silvanheller Indeed, ots nothong more than `./graldew generateOpenApi`.

This is partially addressed in #137 as @ppanopticon kindly provides a newly introduced flag for JSON improt / export. The culprit are fully qualified column names (including schema and entity,...