Enquiry type information structure

See also:

• Explanation of enquiry types
• the static file of enquiry type information

The static file may well be kept on a central server, but in any case every local server should have a full copy, as it is not much information. Every change needs to be originated in the hub and promulgated to the local servers.

Static information

• ETypeCode – exactly one short unique identifier, 5 characters, for 7 enquiry types and one default:
  • SHREL
  • COBIZ
  • COLIV
  • IHELP
  • CLUBZ
  • PLAYZ
  • EMPLY
  • NOETY (means that the enquiry type is missing)
• ETypeLabel – a one-word label for the enquiry type, if needed, in all supported languages
• ETypeTitle – the names of the enquiry types in all supported languages.
• ETypeDescrip – the longer desciption of the enquiry types in all supported languages
• Roles – list of one or more pre-defined roles; for each role:
• RoleCode a single short unique code for the role
• RoleDesc a short description of the role, in all supported languages
• RoleLabel a helpful label for the role, in all supported languages
• For each of the questions that have been prohibited in the enquiry type:
• QID
• ETypeQProhiB – whether prohibited – default is yes, but if a prohibition has been retracted, that would be useful to have documented
• ETypeQProNote – explanation of why it is prohibited, or allowed again after being prohibited

Dynamic information

Global activity in each enquiry type could be tracked as follows.

Numbers of active enquiries in the enquiry type

Every time an enquiry is sent, the hub keeps a record of

• the global Enquiry ID
• time of enquiry

to answer the questions, how many enquiries are there in this enquiry type in the last: hour, day, month?

Keeping track of correspondences looks like too much effort and questionable value.