This area provides a means for adminstrators to configure MKAdmin itself.
Several different configuration records provide configuration information for different tabs, and in some cases, sets of tabs.
Each record has a user-readable Display Name, and a Configuration ID which is used to locate the record. The latter, once assigned, should be be changed unless you know exactly what you are doing.
Additional fields are interpreted as MKAdmin configuration directives, as described in the configuration documentation. For example, adding a field called fieldList with the value zurl will result in the Z39.50 URL being included in checklist pages.
When keys from Torus records are used as configuration elements, they have underscores replaced by periods. This means we can use XML-acceptable fieldnames such as field_displayName_name to get useful configuration-element names like field.displayName.name. (This requirement is an unfortunate consequence of our implementation decision to store Torus record using XML tags for keys, which greatly limits the repertoire of characters that can be used.)