stefanCCS

This happens also, if only one block is used, which has a timeframe for more than one year.

**It is even worse :-(** Even, if you create independently - one after the other - a block per year, the process generation behaves wrong, and only creates processes for...

A small good news: The meta.xml of the "year" process (number 64 of above) looks ok:  -> so, maybe "only" the process naming creation works wrong.

@Kathrin-Huber : I will do this check, but I would like to do this with the expected bugfix release 3.4.4. When do you expect, this will be available?

Hi @solth @Kathrin-Huber , I have checked it again, and it looks like there is still something wrong. I have created this sub processes via calendar function (2 newspaper issues...

And even more strange: If I just create one episode in 2021 --> all named with 2022! 

ElasticSearch has changed license conditions. Last "good" version (in the meaning of license condition) is 7.10.*. But, of course this version is not maintained anymore. Therefore, in my opinion KITODO.Production...

btw: I can confirm that this issue here does not occur, when I use an ElasticSearch Server in Version 7.10.2

> Even the error messages says: "Elasticsearch version 6 or more is required" which let me assume that OpenSearch is providing an information which ElasticSearch is assuming that the remote...

Additional information: I have tried out to use OpenSearch with a "compatiblity-switch": `compatibility.override_main_response_version=true` This changes the version number given by OpenSearch from its own number (e.g. "1.2.0", or in newest...