option to configure which fields are shown on harvest config

[pvgenuchten]

in certain deployment scenario's certain harvester options are not relevant, for example

would be good then to hide them, to not over complicate the configuration options

[fxprunayre]

You mean remove category list/menu from everywhere in the UI when no category is defined ? Same when no XSL transformation. This would avoid to add additional config options for everything and engage people to configure the catalogue with more care (eg. remove category if you don't use it). Or do you need to be able to define this on a per harvester basis ?

[pvgenuchten]

our use case is that we want to deactivate the xsl transformations (in a pan organisational setup, applying generic xsl is less relevant) but i can imagine others may want to set validation to true always (and hide the option here) or indeed deactivate categories (makes sense to hide it on a higher level) we could also consider to hide it by css, if the table row would have a unique id

[PascalLike]

Two options here:

• Improve usability by splitting the harvester configuration into two sections: one with basic settings and one with advanced settings (general approach, so what is basic and what is advanced must be agreed)
• @pvgenuchten suggestion to add CSS ids to every field so it's possible to manage with a custom CSS (This makes things easier for tailormade developments)

It would be good to have unique ids on any field, to facilitate the development of integration tests...

[PascalLike]

I think this can be closed @pvgenuchten