Project Milestones

The goal is to have all major development and integration done by midterm evaluation.

So far, the idea is to support for UTF-8 in full text searching, advanced syntax on search terms (Boolean operators, keyword matching), batch and real-time indexing, relevance ranking and non-text attributes support.

This project can also be a very powerful tool to other ideas that are proposed for Tryton. I believe historical time-line, e-commerce integration and email integration will benefit a lot from this full text search capability. I plan to discuss constantly with the other students and mentors how to make this tool capable of indexing the modules that will be developed on this GSOC

Start of Program (May 24)
· Analyze current implementation of searchable fields, the functions associated with search and how data is indexed;
· Evaluate design changes between versions in order to support all the 3 versions that Tryton supports (in May 24th, it will be 1.8, 2.0 and 2.1);
· Discuss with my mentor and the core development team what are the functionalities expected from this module;
· Put together all ideas, feature requests and setup milestones for each feature in a project management system publicly accessible;
· Discuss with other students implementing Email Integration and Historical Time-line;
· Specify the architecture design with mentor/core developers;
· Start Coding !
Midterm Evaluation (July 12)
· All major (critical) functions should be completed, with unit test / doctest and a complete set of English Documentation generated using sphinx documentation;
· Start performance testing and tuning;
· Start the Code Review process so this module can be distributed as Tryton Module;
· Develop the necessary changes for advance search GTK Interface;
· If core developers find it useful, I plan to “bundle” Sphinx Search Server with “NESO”, so new users can have a simple test environment to experience the potential of the full text search;· Discuss with mentor and core team the priority of the additional / optional functions and improvements in order to make sure I can complete them by the deadline
Final Evaluation (Aug 16)
· Coding for all functionalities in the roadmap are now completed, have complete unit tests, are reviewed by core team and fully documented;
· I plan to add a wiki page on the Tryton Code Snippets Wiki describing the basic usage, design patterns of this module, which will then link to a page containing all sphinx documentation;
· Any request from mentor and core team will be accommodated;

Comments

  1. laurenApril 10, 2012 at 7:49 AM

    A nicely outlined plan I must say.But the execution also matters a lot.I hope that it happened the way you thought it to be as approx one year have passed.Did it?
    Lauren
    sap project system

    ReplyDelete

Post a Comment

Popular posts from this blog

How to install Sphinx Search with libstemmer support on Unbuntu 10.04

I have made a little recipe to install Sphinx Search with libstemmer (for added number of languages) on Ubuntu 10.04 Lucid with postgres support and no MySQL support. Here is what needs to be done as the root user on your Ubuntu linux terminal: 0-) Before we start, we need to make sure all Sphinx dependecies are met: aptitude install -y python-software-properties apt-add-repository ppa:pitti/postgresql aptitude update aptitude install -y postgresql-server-dev-9.0 build-essential 1-) Get the current version of sphinx and uncompress it. cd /opt wget http://sphinxsearch.com/files/sphinx-2.0.1-beta.tar.gz tar -xvzf sphinx-2.0.1-beta.tar.gz 2-) Get libsnowball / libstemmer to add more languages to the stemming process and uncompress it wget http://snowball.tartarus.org/dist/libstemmer_c.tgz tar -xvzf libstemmer_c.tgz' 3-) Copy all files from libstemmer to the sphinx directory so they can be compile together cp -fa libstemmer_c/* sphinx-2.0.1-beta/libstemmer_c/ ./configure --prefix=/etc/
Read more

Draft Version of Tryton_Sphinx integration

I have made a draft version of the module to connect Tryton to Sphinx Search server. This module currently gets all the objects from the Tryton.pool.Pool and make any field that was originally selected by the author to be indexed (an searchable) on the database also searchable on Sphinx Search, with the benefit of full-text indexing on char and text fields, while making other fields available as attributes. I choose to implement this way in order to maintain compatibility with the current modules developed for Tryton 1.8, 2.0 and the future Tryton 2.2, in a manner that no module developer should make any additional effort in order to make their module compatible with the new search methodology if the Tryton. I have pushed my code to a github repository, along with the basic instruction on how to download, install, create the sphinx configuration, index the Tryton Pool ojects and run a searchd daemon in order to listen to incoming search queries. https://github.com/dfamorato/try
Read more

Project Abstract

This project proposes implementing full text search of records and attributes in Tryton using Sphinx Search Sever ( http://sphinxsearch.com/ ) in a pythonic implementation. The idea is to improve Tryton search capability to a more flexible, scalable and powerful option. I propose to use Sphinx Search Server because it is very fast (C++ language), can work in multiple OSes and has windows binaries (which might be included with NESO), it is very scalable, has proven success cases, we can implement in a pythonic way using SphinxAPI (which eliminates the need to install and support Apache Tomcat if we use Apache Solr), because it supports 2 of databases used by Tryton (PostgreSQL and Mysql), maybe can also support SQLlite3 through xmlpipe (if needed) and also supports NoSQL databases and future integrations (like MongoDB and CouchDB). My commitment is to submit fully functional code, using a wiki or project management system to keep track of ideas and milestones (Google Code or Assembl
Read more