Added web interface workflow.
diff --git a/GSoC2010DataSeeder.wiki b/GSoC2010DataSeeder.wiki
index 3a0e564..c3d8d72 100644
--- a/GSoC2010DataSeeder.wiki
+++ b/GSoC2010DataSeeder.wiki
@@ -150,6 +150,28 @@
 Usage: ./data_seeder.py <configraution.json>
 }}}
 
+== Web interface workflow ==
+
+The web interface is the starting point for any seeding operation, either local or remote. It should allow the user to have full control on defining all parameters for the seeding operation, while maintaining flexibility for future updates. The end result should be a JSON configuration file as defined above which can be either uploaded directly to the server or downloaded to be used with the offline scripts.
+
+=== Steps for configuring the seeding operation ===
+
+  # The user is presented with a number of models which can be seeded and selects one or more models to seed.
+  # For any specific model, an AJAX request is made to retrieve a list of that model's properties. For each property, an AJAX request is made to retrieve the available data providers for the property type (e.g. string, number, reference, date/time etc.)
+  # The user selects the number of instances to seed (this will be done by actually configuring a number data provider).
+  # For each model property that the user wants to seed, selecting a data provider will make an AJAX request to retrieve the parameters required to fill for that specific data provider. The user then fills in the data provider parameters (some might be optional).
+    * an auto-complete option for some parameters would be nice or even pretty much required in some cases (e.g. searching for an existing model).
+  # Reference properties are treated as a special case. Depending on the data provider, the user might be provided with a new model to seed. The user will repeat step 2 for this model.
+  # Available back-references for the chosen model are presented to the user. Related nested models will be configured by repeating step 2. The nested model's reference to the parent model will be ignored since it will be overwritten by the back-reference.
+
+=== UML Use Case diagram ===
+
+*TODO!*
+
+=== Mockup ===
+
+*TODO!*
+
 = Meetings and Agendas =
 
 == Wednesday May 12, 2010 8:00 in UTC ==