Arved Solth

Yes, you are right, this was changed in #4642, in order to display file names in the metadata editor structure tree. The reason why this does not pose such a...

Please resolve conflicts

Duplicate of #3860 Yes, this is still bugged and not intended behavior. The main problem I see is that even if we "unlock" a process through all the other links...

> I have no knowledge on JSF unfortunately but the way to proceed here using browser events seem to be OmniFaces viewScope annotations: > > https://stackoverflow.com/a/40552152 https://stackoverflow.com/a/9986442 https://showcase.omnifaces.org/cdi/ViewScoped @BartChris the...

Maybe the available resolution options in the gallery could be linked directly to the available filegroups in the projects settings? So if one thumbnail folder is configured with image width...

Once we add proper documentation about which version of ElasticSearch/OpenSearch is officially supported, this issue can be closed, since #4896 already represents OpenSearch support as a feature request.

I guess the best solution would be to add another search interface type "Custom", which does allow freely adding search fields but does not impose the restrictions that real OAI...

> This sounds reasonable. The custom importer probably requires a mechnism to customize import behaviour as descibed here as well: #5259 #5259 and #5049 will be fixed separately from this...

> @solth You could try > http://search.ub.uni-koeln.de/portal/usbportal/connector/unapi?id=inst001:805615&format=oai_mods Thanks for the link. This does not seem to be valid OAI syntax, though, because in OAI the id parameter is always called...

This issue was fixed by #5313 @BartChris if I understand correctly, implementing #5257 for **custom** type import configurations would solve the issue you reported and enable you again to query...