Wireframe: forming-enquiry

This is the main engine of the whole system, where the user's requirements are expressed.

This is one of the vital, central pages of RegenCHOICE. This is where a single enquiry is prepared for trial. The same enquiry works either for active search, in which users change what they want, and answer more questions, until they find correspondence; or an enquiry that is standing, waiting, where users record what they have and what they want, and leave them on the system in the hope that an active search will correspond.

I see details of an existing enquiry, manage it, and try it out.

If I have any existing candidates fitting this enquiry, or anyone has invited me to contact, based on mutually fitting enquiries, I can:

• go straight to a list of existing candidates without (re)trying the enquiry — these are removed if any changes are made to requirements.

In any case, I can choose:

• to go and change the basic details (name and description)
• to go and change the location details
• to go and change the timing details
• to change the enquiry as a whole from active to inactive of vice versa
• to change a requirement into just considering want or vice versa
• to go and modify a current requirement or add a new one
• to try this enquiry if I decide it is ready to try
• to unmute an answer that is currently muted
• to keep this enquiry standing and go somewhere else

See the page destinations below.

Many pages lead here, as this is a central point of activity. (to be checked, may be inaccurate)

• A Candidate
• All Candidates
• All Enquiries of type
• This Enquiry basics
• This Enquiry location
• Invitations across all enquiries
• My answer
• My answers
• My answer enqs
• New question
• Show results
• Unanswered question

• Leave unchanged, back → Enquiries of type
• Choose to go and revise:
  • → Enquiry basics
  • → Enquiry location
  • → Enquiry times
• Try the enquiry. → processing → No results | Many results | Show results
• Add a requirement for this enquiry → add question
• For each currently required question, link to
  • → What I Want in enquiry for that question (or change it)
• Promote a considering want to a requirement → reload page
• Demote a requirement to a considering want → reload page
• Remove a considering want → reload page
• If on, leave as a standing enquiry; if off leave off. In either case, link to:
  • → Enquiries of type
  • → Enquiries overview

• Choose to answer a suggested question → Unanswered question
• Unmute an answer, if muted → reload page

• Turn on or off enquiry → reload page
• Delete the whole enquiry → confirmation pop-up → Enquiries of type

See enquiry-info and e-type-info

• EnqID (the key field)
  • Later, we can add question dependencies
• ETypeTitle ← ETypeCode
• EnqName: the short name of this enquiry
• EnqNote: description of what is looked for with this enquiry
• EnqLID: the chosen location for this enquiry, or “anywhere”
  • LocName
  • if ELocB, the max distance EMaxDist
• EnqTimes: the times open for this enquiry
  • ETimeStr: times presented as a string
• EnqActB: whether the enquiry is active / turned on or inactive / turned off

These numbers need to be hidden as soon as anything is changed

• number of contacts related to this enquiry, if any
• number of candidates who have invited contact
• number of candidates who have been invited to contact

Questions in this enquiry — EQList

• divided by EQGrade into required and considering
  • QID
  • QTitle
  • dependent questions

Answers muted in this enquiry (from EQMuteB)

• QID
• QTitle
• MyAVal

Changes in:

• EQGrade
• EnqActB

Need to be careful about question dependency.

A user may not want certain answers to be taken into account for an enquiry. A question can be globally refused; but here it is more a case of answering a question in some contexts but not others. Here we list the currently muted answers for this particular enquiry, and allow them to be unmuted before trying. They can be muted again when it is known which questions from other users are significant for this enquiry, but the muting needs to be done on another page, maybe:

• candidate
• my answers

What is currently illustrated with up and down arrows in the wireframe needs to move the questions in the obvious way (in the direction of the arrow!)

An enquiry is essentially a list of requirements for how the other person must answer a set of questions. If the user has not thought of any particular requirements – like, they just want to meet someone, anyone will do – it is possible to place an enquiry straight away with no requirements.

More likely, the user has certain ideas in mind about the characteristics of the other party they are looking for.

The user can then go on to list other requirements of the other party. This will naturally depend on the type of enquiry, and more precisely on what is being looked for. The enquiry questions are chosen from the complete set of available questions, omitting any ones that are not allowed for the type of enquiry, or perhaps the age of the user.

There are in principle several possible ways of finding more questions to ask. One is to go with the system's suggestion of the most popular questions to ask. Another is to have a question-finding dialogue where the user types in a few words into a text box, and the system gives a list of most relevant questions.

2024-11-15 I'm not sure whether to allow people to respond immediately to candidates or to try the enquiry first. Maybe going to a list of candidates should be put on the enquiries of type page?