Default values in kitodo_opac.xml

[andre-hohmann]

The catalogue search during the creation of a new process could be more comfortable, if it was possible for "Catalogue" and "Field" to define default values.
As most users are working with one catalogue and are searching for an identifier, the manual configuration is not necessary, but after a while quite annoying.

The target state:

The current state:

The current way to the target state:

[matthias-ronge]

Likewise, it is annoying to have to manually close the catalog import every time, if no catalog is used in the project. I would like to see such presets in project settings (if dialog should show / which OPAC should be selected) [→ extracted to #4252] and OPAC settings (which search field is selected; see also #3407).

[solth]

@andre-hohmann, @subhhwendt Configuring these default values via the kitodo_opac.xml file would set them as global defaults, not on a per-project-base. If that sufficient, I would suggest to implement it in this fast and clean way to add the default value functionality in the short-term, independet of more complex and extensive reworks of the whole OPAC import in the future. It should hopefully already ease some of the pain that comes from working with the current catalog import mask.

In the long run, I would propose to rework the whole OPAC configuration and move it from the current XML configuration file to dedicated Java classes that can be configured via the Kitodo.Production GUI, if #4322 gets approved. Then we could configure these default values for each project individually and wouldn't have to worry about XML syntax and available configuration options anymore.

[solth]

Alternatively we could use the existing configuration in kitodo_projects.xml to set default catalogs for projects individually, but that would prevent the intended removal of that configuration file (see #3777)

[andre-hohmann]

I absolutely agree with you. Currently, it is sufficient that one catalogue and one search field can be set as default.

In my opinion, we should not use the kitodo_projects.xml to solve this issue. If #4322 gets approved, we can search for an comprehensive solution.