Edited wiki page GSoC2014Ideas through web user interface.
diff --git a/GSoC2014Ideas.wiki b/GSoC2014Ideas.wiki
index 1f1db7c..ab27edb 100644
--- a/GSoC2014Ideas.wiki
+++ b/GSoC2014Ideas.wiki
@@ -36,6 +36,36 @@
*Probable Mentor:* Mario Ferraro
+== User data dashboard and dependencies ==
+
+The project would be to implement a simple dashboard that would list all artifacts associated with the specified user or profile. It would look somehow like a tree (or a graph, to be more precise). A very simple example is outlined below:
+
+ * userA
+ * profileA
+ * proposalA
+ * commentA
+ * proposalB
+ * commentA
+ * commentB
+ * commentC
+ * projectA
+ * codeSubmissionA
+ * evaluationA
+ * profileB
+ * commentA
+etc.
+
+It would help us understand what the exact layout of our data design is and what exactly has to be processed so that data is not broken after an account is deleted. It looks relatively easy, but it definitely is not. There are at least two open end questions:
+
+ * how to present the data
+ * how to collect the data so that it does not break down when a user has a lot of artifacts, for example comments.
+
+Another part of this project would be to generate a graph of reverse references of models. It would give us visualization of what dependencies between the models are.
+
+*Relevant Skills:* AppEngine, Python
+
+*Probable Mentor:* Daniel Hans
+
== Resource Hosting ==
Running a program on Melange involves distributing a lot of documents and serving a lot of content - from user images to translated contest rules and everything in between. Melange doesn't yet have a subsystem that makes resource ingestion, hosting, and distribution easy for both users and feature developers. It should.
