Interface Concept: Large Forms

MPDL

=Introduction=

Large forms can be improved using different methods. Since large forms are mostly complex to handle it is important to approach with methods step by step to avoid problems concerning following specialities:


 * 1) Dependencies
 * 2) Fields can only be filled if corresponding fields were filled
 * 3) Fields depend on selections
 * 4) Dynamic aspects
 * 5) Forms must be added manually before they can be filled
 * 6) Additional Forms of one criteria can be duplicated and removed
 * 7) The whole form (length, metadata) depends on a precondition
 * 8) The form can only be filled in steps
 * 9) Integrity
 * 10) One or more input values must be validated

Properties, subject to change in large forms are:


 * The amount of input fields
 * Minimizing user input
 * Comfort of providing data
 * Orientation
 * Help on why input is mandatory/needed/useful
 * Protection of work spent on the form
 * Making the form pleasant (at least its look and feel)

=The Amount of Input Fields= An approach should not mean to simply rip single fields off but to have a closer look what user input is needed, when it is needed and to what extent it is really needed instantly. Practically the following steps are required:


 * Identify mandatory fields
 * Sorting fields by relevance
 * Grouping fields by similarity
 * Sorting fields by order of input (e.g. an address is usually not entered prior to a name)

Furthermore it makes sense to provide more categories than mandatory and optional:


 * mandatory criteria
 * necessary criteria
 * useful criteria
 * optional criteria

With the preconditions above the form can be broken up in parts that are persistently displayed and parts called on demand by the user.

=Minimizing Input= Users do not like to fill long forms, especially when the same information is requested redundantly (e.g. Publishing date requires to enter the year 6 times, publishing info and publishing info of source can be the same).

Following questions are subject to this: Do we provide fields that can be filled easier or faster?

Minimize input using defaults and templates
Objects are sometimes filled repeatedly with the same informations: Creator, Organization, Place, ...

Following questions are subject to this:
 * 1) What fields can be predefined with 'personal settings'?
 * 2) What information is important to have it down pat (persistent and independent from submission)?
 * 3) Are there publications you would use as templates?
 * 4) Is it useful to have more than one template?
 * 5) Is it useful to choose between metadata from different templates?

=Providing Data Comfortable=

Input Assistance
Several mechanisms can be used by interface development to make input more comfortable:


 * Multiselect-Boxes
 * Autosuggest
 * Auto copy

Following questions are subject to this: What selections should be visible more explicitly? Which fields can be used to harvest data for an autosuggest? Which fields can be filled by 'auto copy' (and changed later if necessary)?

=Orientation= Forms can be structured in groups. Positions of labels can be aligned for fast recognition. As this is more a design task (Gestaltung) it should be an optional question if the scientist wants to comment on that.

=Help on Why Input is Mandatory/Needed/Useful= There are different expectations between librarians and scientists for submission. At least scientist want to have their publications retreived easily.

Following questions are subject to this: Do you wonder why specific fields are necessary? Do you think you would give input if it is clear to you? Do you like to know more about the input (e.g. Sequence No.)?

=Protection of Work Spent= It is a technical issue. Techniques like DOM storage/Application storage.