1. NETWORK VISUALIZATION ABHISHEK KUMAR (2011CS50272)

2. Contents  Objective  Major Tasks  Why can’t use infoboxes?  Solution models  Schemas and examples  Problem faced  Future work and projects  Conclusion

3. Objective To enhance mediawiki software to make it easy to create, visualize and edit relations between different wiki pages

4. Overall 5 Major Tasks  Understanding mediawiki [Aug-Sep]  Setting up a local Wikipedia [Sep-Oct]  Researching Infoboxes [Sep-Oct]  Writing an extension to make recursive queries [Nov]  Visualizing the data provided by extension [Nov]

5. Why can’t use Infoboxes?  Infoboxes are templates and templates can’t pass arguments to php code  We need to run php code for our recursive queries  Ideally extensions are used to for these tasks  Extensions work by creating custom XML tags  in our case

8. Schema Description

9. Parameters

10. Examples

12. Problems Faced  Mediawiki is a complex software. Understanding different components and flow was challenging.  Lack of documentation for mediawiki.  Very less support for bugs and errors. Google doesn’t help much.  Import_dump.php didn’t work initially.  Visualization took more time than expected.

13. Future work and projects  Extend this project to add more visualizations  More research on infoboxes: try parsing rendered text instead of raw wikitext.  Make extension mobile friendly and more user friendly.  Render multiple graphs by placing multiple tag blocks.  Draw correlations and causal relations using visualizations.  Add another layer of cache on the top. Save the graph data structure in media wiki database.

14. Conclusion  Wrote a mediawiki extension which successfully makes recursive queries to generate a graph data structure.  No other extension makes this type of recursive queries.  Visualized data using d3.js  Added few functionalities for the user.  Overall a very good learning experience.

15. Thank You. FEEDBACK AND QUESTIONS? 15