Wireframe: show-results

This is a vital step in the central line of RegenCHOICE where, when an enquiry gives 1 to 9 results, the enquirer looks at those results and decides to “save” some or all of them, into the pool of candidates for that enquiry.

This list of results gives me a feel for what kind of results come at this moment from this enquiry. If I'm happy with the enquiry and the look of the results, I can just accept these to add to my list of candidates for this enquiry. If I have second thoughts, or don't like the look of the results, I'll go back to the enquiry.

• Forming enquiry followed by processing

• Go right back → link to Enquiries of type
• Accept all as candidates → Candidates
• Go back → link to Forming enquiry
• See a Contact that fits this enquiry

Needs enquiry-information. Key is EnqID; CanNum and QID are multiple, not key.

• Enquiry type ETypeCode → ETypeTitle
• Current enquiry EnqID EnqName EnqNote
• results from processing step, and for each fit enquiry
  • The QTitle of your wanted question
  • Some way of telling if any of the results are already on the contacts list
  • The answer given CanAns
  • if closeness is required and COORDS used, may be sorted by CanELocFit
• for each contact who fits the enquiry
  • their CanNum, CoName and/or CoNick

• if button to add is chosen, add all the corresponding uninvited parties to the list of candidates, assigning new CanNums, with ContactStatus of UNINVITED.

Checking for duplicate uncontacted candidates can be done when they are added to the candidates list.

Results need to filter out anyone who has broken contact. And if the results contain someone that is currently still in contact, this must be flagged.

People can prevent contact by:

• Blocking the person → Contact page
• Deactivating the enquiry; changing their wants or answers so they no longer match
  • → Forming enquiry

Breaking contact has its own process.

Numbering of candidates where contact is not agreed

Looks like a good idea to have fixed numbers for candidates, to allow recognition across different enquiries. Propose: sequential numbering of candidates as they come up in one's list, or as they issue invitations if they have not appeared in one's own list. This means that RegenCHOICE has to keep a personal list of candidate numbers, tied to system IDs.

A nice consequence of this is that two users cannot cross-reference their candidate IDs to find anything about a particular candidate pre-contact. When two enquiries from same candidate match one from enquirer

This is really annoying, because it is plausible. On this page, not really a problem, as the same candidate can be listed more than once.