Ticket #180 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

Context help will reduce bad data entry

Reported by: chrisl Assigned to: thomase
Priority: critical Milestone: Geo Control
Component: GeoEntity Version: Beta
Keywords: Cc: sgillies

Description

The data entry forms, such as the one for creating a Geographic entity, have plain text entry fields. When entering data, there is no immediate help on the syntax. This means that data entered is likely to be erroneous and may cause problems with the software. While review is always needed, some support and checking at point of entry

For example, should a location be in dms or decimal degrees? 52N23, 1W14 or 52.23 -1.14 or, as seems to be the case, a space separated list of three floats, the last indicating altitude. Today I made a typo, missed out a space, and got a defective entry that gave errors; took me a couple of minutes to figure out how to delete it, since the error prevented its page being created by the system.

Similarly for fields which use a constrained vocabulary, there is a need to offer contextual help at the point of entry. For a short controlled vocabulary, a drop-down would suffice.

In some cases this information is on other pages of the site; the trick is to find them when needed. At minimum, each data field could have a link to another page describing any constraints on its syntax.

Change History

10/06/06 09:49:52 changed by thomase

  • cc set to sgillies.
  • owner changed from sgillies to thomase.
  • component changed from Portal to GeoEntity.
  • milestone set to Geo Control.

02/19/07 11:03:16 changed by thomase

  • status changed from new to closed.
  • resolution set to fixed.

We have a rudimentary contributory help system in place. It may need refactoring later, but it works now.