Comment 1 for bug 1716473

I support hiding the unneeded fields. In our case, we usually are hiding fields that never, ever get used by the library. Things like circ as type (our circ policies are based on circ mods), floating, and quality. Fields that are rarely used still remain visible.

Another compromise might be to implement something similar to the patron editor where there is a toggle to display suggested and all fields. An added benefit to this method is it provides consistency between the two interfaces.

I also wanted to add a note that I another thing we miss is the ability to configure these settings for the entire org unit. In the web client, these settings are stored for the workstation, which requires each cataloger to make sure they are configured correctly.