@dkayiwa it was a pleasure working with you and @ibacher on getting this issue done. It was a long time but I think it was totally worth the effort. So I am looking forward to continue the work on other issues.
In term of that new ticket I think I totally understand the need. We would like to configure in a more flexible way what filters should be used. E. g by giving a string as global properties like this one:
“org.apache.lucene.analysis.core.LowerCaseFilterFactory, org.apache.lucene.analysis.standard.ClassicFilterFactory, org.apache.lucene.analysis.miscellaneous.ASCIIFoldingFilterFactory”
I am just not sure where the gap in the approach of @bistenes lies as he already developed code and rather seemed in failing to make it being overwritten by a module. I am not sure how to work with an open-mrs module. Do you got an idea where I can read about it? And where the global properties should be overwritten in a module context? I assume there exists a standard approach.