Changes between Version 22 and Version 23 of BluePrint/SocialMedia/GHC2013SocialMediaHITProcessing

Timestamp:

10/05/13 09:08:12 (11 years ago)

Author:

Pat Tressel

Comment:

--

BluePrint/SocialMedia/GHC2013SocialMediaHITProcessing

@@ -86 +86 @@
 http://booki.flossmanuals.net/sahana-eden/_draft/_v/1.0/building-a-new-application/ [[BR]]
 Copy it to {{{models/000_config.py}}} and add an entry for the hit module.
+
 === Add a database table for message processing tasks ===
 
-We want to add a table that joins to this to hold the data entered by a worker for a message.
-That table will need fields for:
+We want to add a table that holds the data entered by one worker for one message.
+The table will need fields for:
  * A foreign key reference to the msg_message table. Here is another table with such a reference:[[BR]]
    https://github.com/flavour/eden/blob/master/modules/s3db/msg.py#L1609
@@ -109 +110 @@
 set of results for each message. We want to include which worker did each task, so we can check
 the quality of their work and refer them to more training if needed.
+
+=== Track which messages have been processed ===
+
+We don't want to add fields to {{{msg_message}}} just for our module. But we need a way to tell when
+a message has been processed, so we can select unprocessed messages to give to users. Later, when we
+add more human intelligence task features such as sending the same task to multiple workers, we'll need
+somewhere to record how complete the work is for one message.
+
+So we may want to add a table that gets a record added when each message intended for processing arrives.
+The table should be defined in the same model file as the task table. It should refer to the {{{msg_message}}}
+record in the same way as above, and should have a boolean field for whether the message is processed.
+(Later, this can be changed to support processing by multiple workers, but for now, we can consider it
+done when one worker has processed it.)
+
+We don't want to enter all messages, just ones for our workers (e.g. incoming email for individuals
+should not be sent to workers). We'll need a way to recognize our messages, e.g. a Twitter direct message
+recipient or hashtag, or a particular SMS shortcode. There is a new and somewhat experimental feature
+for selecting out messages, which may be useful for this, but documentation is lacking. This will
+require consultation on IRC. IF we cannot use this, we can (temporarily) add specialized code in the
+{{{msg}}} module's incoming message handling to pick out the desired messages and create records for them.
+
 === Add a controller function to generate task pages for workers ===
 Look at:
@@ -124 +146 @@
  * Create a record in the (new) hit_task table (being worked on by the model team).
  * Return the standard form for the new record to the user.
+
 === Add a view that presents a task to the worker and submits their work ===