Then there was this “flickrj” library, the latest version of it seems to have changed in someways how the authentication class works, or may be Flicker API changed, so updated that also. The earlier (Mihai’s) branch had a API Key, but I replaced with another Non-Commercial API key that I for from Flickr.
Almost all the environment is setup, and the project compiles without any errors. SO does that means it work…? No, don’t think so. Now my next taxk for the comming week would be to working on that.
I have got this great guy Nathan from CC as my GSoC mentor, who pings me and asks for project updates, so hope to give some trouble to him as well, as I’m certain I’d encounter more in the comming days… 
I have to use SVN+SSH and I’m not sure about what OS would be better for me. Though Ubuntu was my primary OS, I had to switch to a Vista box which I share with my family as my laptop got burned internally. I’ll have to work hard on this project and get my second payment to get a new laptop…
I have sent my SSH keys to my mentor Nathan, and he will be enabling my SVN access, and now I feel I’m really lagging in my project which I have to catch up in some way.
I’m planing to have some form of a deliverable by June 15th. Lets hope for the best…!
]]>After these concersations I have the following as a status update:
- I’ll be working with a previously written codeduring the last GSoC.
- I’ll be given access to the Creative Commons SVN, for which I have to give my SSH public key.
- My first task would be getting the plug-in up to compatibility with OOo 3.
- Nathan suggested me using NetBeans and a NetBeans plugin that can help start OOo plugin development.
So now I’ll have to get those SSH keys generated (seems I forgot how I did that couple of years back ) and send those to my advisor, then only I will be able to get the SVN access.
In the man time I’m going for a conference in Istanbul, Turkey from 9th to 15th May, so will have to start on this after coming back.
Hope to keep this blog updatd…. So just ping back and see… if I keep my words…
This is the first time I’ve applied for GSoC and I got selected with one of the the two proposals I sent, both to Creative Commons.
I’m looking really excited about this and looking forward to start working on this project.
]]>| Title: Ontology Add-in for OpenOffice.org | |
| Student: Nimalaprakasan Skandhakumar | |
| Abstract: | |
| Ontology Add-in for OpenOffice.org will enable the annotation of OOo documents based on terms that appear in Ontology. This will be similar to the Microsoft created a plugin for Microsoft Word 2007 helping one insert links to ontologies curated by Science Commons. | |
| Content: | |
| Project Abstract (1 paragraph, high level overview):
Ontology Add-in for OpenOffice.org will enable authors to easily add scientific hyperlinks as semantic annotations, drawn from ontologies, to their documents and research papers. Ontologies are shared vocabularies created and maintained by different academic domains to model their fields of study. The goal of the add-in is to assist scientists in writing a manuscript that is easily integrated with existing and pending electronic resources. The major aims of this project are to add semantic information as XML mark-up to the manuscript using ontologies and controlled vocabularies (from the National Center for Biomedical Ontology) and identifiers from major biological databases, and to integrate manuscript content with existing public data repositories. This Add-in will make it easier for scientists to link their documents to the Web in a meaningful way. Deployed on a wide scale, ontology-enabled scientific publishing will provide a Web boost to scientific discovery. This project is focused on researchers and software developers in domains utilizing ontologies– as well as publishers, archivists, and early adopters in the scientific, technical, and scholarly publishing fields. This add-in would simplify the development and validation of ontologies, by making ontologies more accessible to a wide audience of authors and by enabling semantic content to be integrated in the authoring experience, capturing the author’s intent and knowledge at the source, and facilitating downstream discoverability. As part of the publishing workflow and archiving process, the terms added by the add-in, providing the semantic information, can be extracted from Word files, as they are stored as custom XML tags as part of the content. The semantic knowledge can then be preserved as the documented is converted to other formats, such as HTML or the XML format from the National Library of Medicine, which is commonly used for archiving. The full benefit of semantic-rich content will result from an end-to-end approach to the preservation of semantics and metadata through the publishing pipeline, starting with capturing knowledge from the subject experts, the authors, and enabling this knowledge to be preserved when published, as well as made available to search engines and presented to people consuming the content. As for the workplan this will me mainly focusing on porting the openly available Microsoft Word 2007plugin, thus we will not have to start from scratch. This will require not only just porting the code, but will also involve customizing for OOo falvour and will also invoive using the OOo 3 SDK for the development. What risks to completion exist and how do you plan to mitigate them? Issues when porting from MS Office 2007 to OOo Writer can be an issue, but I hope I will be able to handle this as its mosly relied on XML standards and the code is available openly. Another issue would be related to getting access and using Ontolog, I will be able to get more help realated to this from the staff at our university and other researchers at our university. Have you posted this on cc-devel (mailing list) or #cc (IRC) for feedback? Yes, I have discussed about this with developers on cc-devel, and got some feedback from them. Why I’m suitable for doing this?
Contact Information Email: [email protected] |
Related Links: ]]>
| Title: Creative Commons Add-in for OpenOffice.org Updates | |
| Student: Nimalaprakasan Skandhakumar | |
| Abstract: | |
| The Creative Commons Add-in for OpenOffice.org allows license information to be embedded in OpenOffice.org Writer, Impress and Calc documents. In addition to embedding the license in the document metadata it provides a visible notice in the document. This project is targeted on updating the current plugin to incorporate code base changes and also to add some new features such as multi-language support and support for OpenOffice.org Draw. | |
| Content: | |
|
Project Abstract (1 paragraph, high level overview): The Creative Commons Add-in for OpenOffice.org allows license information to be embedded in OpenOffice.org Writer, Impress and Calc documents. In addition to embedding the license in the document metadata it provides a visible notice in the document. This project is targeted on updating the current plugin to incorporate code base changes and also to add some new features. This would also include upgrading the user interface and providing multi-language support. This update will also enable support for this plugin to be usable in OpenOffice.org Draw. Project Details (technical details if available, work plan): As this project is providing a update for the existing plugin the first task would be to updating the codebase to the latest OpenOffice.org 3 SDK. This would be of advantage to the plugin as we need to keep up with the latest SDK. The next update would be to do the updating the existing features. The main update would be with the License selection UI. This could be modified to have mouse over help balloon messages showing the basic meanings of each license selection. This can also be further enhanced to display license information when opening CC licensed documents. This will be helpful in the user perspective. Internationalization would be the update that I have great love towards in all and with this we will be able to prepare the code for translation. This would include writing scripts to integrate PO files prepared by translators and making the plugin to be available with multi-language support. OOo Draw is another wonderful software in the OOo suite and one I use very often, and I belive haing the plugin supporting Draw will be benificial to many. Specially it could be handy when the output of Draw are used in website and others. Also one another addtion to the plugin which many seems to be looking foward is add support for CC0. CC0 is like the “no rights reserved” option license and once the creator or a subsequent owner of a work applies CC0 to a work, the work is no longer his or hers in any meaningful legal sense. The current version of the plugin doesn’t seem to be having this licence and I belive including this also would make the plugin more complete in the CC aspect. What risks to completion exist and how do you plan to mitigate them? There are few possible risk factors involved in this project, and I believe I will be able to handle those is a positive manner. One of the important factors would be in moving to OOo 3 SDK, where it might require some existing codebase, but I am certain I can handle this with my perior experience in OpenOffice.org development. Also the internatiolaization requires making the plugin codebase to support different language specific aspects, and I have had first hand experience in these with my previous involvement in Firefox, OpenOffice.org and WrodPress localization project. Also the timeframe would be another concern as this projects has many distict tasks, but I will be able to employ my project management experiences with this to make it doable in desired timeframe. Have you posted this on cc-devel (mailing list) or #cc (IRC) for feedback? Yes, I had couple of threads discussing about this with developers on cc-devel, and I was also able to have few chat sessions on #cc where I was able to get some feedback from other developers there. Why I’m suitable for doing this?
Contact Information Email: [email protected] |
Related links: ]]>
-Nimal a.k.a. TalkOut
]]>