Changes between Version 33 and Version 34 of Onyx Export and Purge

Timestamp:

10/03/11 17:50:23 (13 years ago)

Author:

jeff.lusted

Comment:

--

Onyx Export and Purge

@@ -166 +166 @@
 === On Filtering using a Date ===
 
-A further experiment revealed that the filter illustrated below worked, selecting participants with a status of completed where the conclusion questionnaire end date was some time in January, and the participant hadn't been exported before. All the valueTables within the export config file had the same filter. It doesn't take much imagination to work out how to add a further condition to test for year.
-
+A further experiment revealed that the filter illustrated below worked, selecting participants with a status of completed where the conclusion questionnaire end date was some time in January, and the participant hadn't been exported before. All the valueTables within the export config file had the same filter.
 
 {{{
@@ -187 +186 @@
 }}}
 
+I suggest something along these lines would provide an incremental basis of exporting until the number of participants with completed status has dropped to a manageable extent.
+
+{{{
+    <valueset entityType="Participant" valueTable="Participants">
+      <entities>
+        <excludeAll />
+        <script type="INCLUDE">
+          <javascript><![CDATA[// Include any ValueSet that has 'COMPLETED' as a value for the 'Participant.Interview.Status' variable
+                               // and the conclusion questionnaire timeEnd is in May or June of 2010
+          ($('Participants:Admin.Interview.status').any('COMPLETED')).
+             and($('ConclusionQuestionnaire:QuestionnaireRun.timeEnd').year().trim().any('2010')).
+             and($('ConclusionQuestionnaire:QuestionnaireRun.timeEnd').month().trim().any('4', '5'))
+          ]]></javascript>
+        </script>
+        <script type="EXCLUDE">
+          <javascript><![CDATA[$('Participants:Admin.Interview.exportLog.destination').any('BRICCS.Participants')]]></javascript>
+        </script>
+      </entities>
+    </valueset>
+}}}
+
+Incremental changes to the above month condition on each export could include a further month and any participants from previous months that had since moved to completed status:
+ * month().trim().any('4', '5', '6') 
+ * month().trim().any('4', '5', '6', '7')
+ * month().trim().any('4', '5', '6', '7', '8') 
+and so on
+
+The EXCLUDE ensures those already exported will not be exported again. By the time an export got to include December 2010 it would be time for a rethink.
+
 === On Editing the Export Configuration File ===