{"id":1644,"date":"2013-07-13T14:13:47","date_gmt":"2013-07-13T14:13:47","guid":{"rendered":"https:\/\/notebooks.dataone.org\/?p=1644"},"modified":"2013-07-13T14:13:47","modified_gmt":"2013-07-13T14:13:47","slug":"documentation-integration","status":"publish","type":"post","link":"https:\/\/notebooks.dataone.org\/prov-model\/documentation-integration\/","title":{"rendered":"Documentation & Integration"},"content":{"rendered":"

I switched gears a little bit this week. Instead of focusing on developing new modules, I mainly worked on documentation and integration.<\/p>\n

For the IMIF package, a good help document is very important. Last week I used existing Python tools called pydoc to create documents for it. However, it’s not that flexible and the generated html help document looks not that \u201cprofessional\u201d. After talking with my mentor, we decided to create separate web pages for each module and the help document should be well organized, so we need a more flexible documentation tool. Finally I found a powerful tool called Sphinx. Many existing documents of python packages were created with this tool. It uses a new markup language called reStructuredText. After preparing documents for each module using this language, it automatically generated well-organized help documents with professional looking. I really love this tool. Just as one of slogan in its website says \u201cCheers for a great tool that actually makes programmers want to write documentation!\u201d<\/p>\n

The major work I’ve been working on this week is integrating the modules I developed with the visualization modules developed by a DataONE Postdoc and a previous summer intern. The integration include two parts: one is put them together and another one is to use them together.<\/p>\n

Putting them together is relatively easy. I merged their visualization modules into the IMIF package. In order to facilitate the users, I organized them into 4 different categories:<\/p>\n