Enquiry basics page

Wireframe: enquiry-basics

The basic essential information about any enquiry is the name given to it by the user, and some kind of explanation. The explanation of what is wanted in this enquiry will both keep the user focused, and potentially provide input for some automatic suggestion of criteria questions.

I initially enter, or later change, the name and description of my enquiry.

• forming enquiry
• enquiries of type

• Button to submit changes
• If location not defined, pop-up to ask if location is significant
  • if yes → enquiry location
  • if no, pop-up to ask if location is significant
    • if yes → enquiry times
    • if no → forming enquiry
• Links to move on with no change
  • if enquiry was already there → forming enquiry
  • if enquiry hadn't been started → enquiries of type

• Reminder of the nature of the chosen enquiry type
• Explanation of what the name and description are for

From ETypeCode:

• ETypeLabel
• ETypeDescrip

Derived from current EnqID:

• Current EnqName
• Current EnqNote

• New EnqName → web storage on device
• New EnqNote → web storage on device

If the user is proceeding, via a “submit-type” button, then a new EnqID is created and stored on the device

One could use the text area input cleverly to suggest initial questions or templates.

Should the private notes be completely private, or shown to contacts? I think the latter, to encourage openness. RegenCHOICE wants to discourage deliberate deceit.