Question information structure

infoarch/question-info.html

Whether wanting or answering, there is only ever one focus Q at once. In fact that is the criterion that separates distinct questions. This can be implemented most simply as a large text file (JSON, or just a simple text format?) or in a normal relational database. Either way, we want a tool that can (securely) read from and update this store.

Static Q information, held in the GMS

• QID: global, typically a long number.
• QTitle: @lang, mandatory; Q title used for link text
• QDesc: @lang, optional; description: further Q elaboration / explanation
• QRelB: Boolean: is this a relational question or not?
• QStruct: one of 6 codes — see the question-struct index
• QDetails: virtual field with everything else about the Q, depending on QStruct:
• AORBQ — A/B preferences
• LEVLQ — levels with no scheme
• LIKSQ — single-pole Likert scale
• OPTSQ — option lists
• RANGQ — position/range on a metric
• TRIPQ — A/B with explicit mid-point

FACTQ — factual questions need no further details

• for each super-Q or controlling Q
• QID of super-Q
• answer or range of answers to super-Q enabling this Q
(this presumes that we can find possible sub-questions from the listings of super-Qs)

Information only relevant to question maintenance and revision

The revisions are envisaged as being mainly to the text fields, or other mistakable things. This may not be something to implement at first; it is essential only for gradual improvement of the system, not its initial working.

• QAuthor: the GUID of the original author of the Q. Note that GUIDs are not available to users.
• QOwner: the GUID of the current owner of the Q — that is, the person responsible for its maintenance.
• QTitNew: revised title of Q, @lang
• QDscrNew: revised explanation of Q, @lang
• QItemShoNew: revised short item text @lang
• QItemLoNew: revised long item text @lang
• for preferences between alternatives:
• QPr1New: revised QPref1 description of one @lang
• QPr2New: revised QPref2 description of other @lang
• for positions in a metric only:
• QSmaNew:revised QSMax possible value
• QSmiNew:revised QSMin possible value
• for level questions only:
• QSchNew: revised level scheme
• how do we do previous and newer versions, exactly?

Answers about Qs (not part of Q structure itself)

• good enough to use
• confusing / ambiguous / unhelpful
• polarizing or otherwise dangerous; should not be allowed

Answer readiness

For all Qs, readiness to answer is kept, in QAccept – see answer-info

Relevant interface pages

Distributed throughout, but particularly:

• Edit a question