Changes between Version 21 and Version 22 of OnyxExportOntology

Timestamp:

01/31/11 10:07:00 (14 years ago)

Author:

jeff.lusted

Comment:

--

OnyxExportOntology

@@ -372 +372 @@
 With the above principles, I've been finding a few minor weaknesses (one may be irrelevant) and a fairly major omission. But nothing that cannot be corrected.
 
-==== Qw
+==== Weakness One ====
+This is from the consent stage:
+{{{
+  <variable name="mode" valueType="text" entityType="Participant">
+    <attributes>
+      <attribute name="stage" valueType="text">Consent</attribute>
+    </attributes>
+    <categories>
+      <category name="ELECTRONIC"/>
+      <category name="MANUAL"/>
+    </categories>
+  </variable>
+}}}
+Most categories are much more complicated than the above, particularly in a questionnaire stage, where they spawn a lower variable (like tobacco_any.N in the !RiskFactorQuestionnaire where the N is described within the previous tobacco_any variable as a Category). But the above choices (ELECTRONIC and MANUAL) are a bit like stand alone enumerations. At present for categories this simple, the choices are being overlooked and are not collected, which represents a loss of information.[[BR]]
+I suggest we collect this type of information by creating a lower level construct. I'm not sure what to call it, but I'm not concerned about the name provided its not misleading. What about <enum>? We can always change our minds later.