This issue is to lay out the roadmap for future devleopment. If you wish to contribute to this project and don't know where to start, consider working on one of the tasks mentioned here.

  • Add the ability to subscribe to more than one opensearch source. The current limitation of only one subscription source makes this module only a fraction as useful as it could be. Major issues are how to integrate dynamically generated tasks and sub-tasks into the existing q=search menu family and preserve the GET search terms functionality that the search module provides. It is difficult to change the number of args in the paths without breaking everything.
  • Once several sources can be subscribed, it will be necessary to think about how they are rendered. Two options that I favor are:
    1. each source as a sub-local-task
    2. all sources woven together

    The sub-local-task approach suffers from the issues mentioned in the first point, and the woven results raise questions regarding weighting. How does one sort the various results (and possibly detect duplicate hits as well)?

  • Document the opensearchclient_bindings hook. The idea is that the various opensearch RSS sources will have their own namespaces and extra information. Nutch is like this. The opensearchclient_bindings hook lets other modules register callback functions for handling these extra namespaces. An example will eventually be found in the Nutch integration module. Examples of other opensearch RSS feeds with custom namespaces would be helpful. Drupal could be one of these.

Comments

moshe weitzman’s picture

Status: Active » Fixed

i think has been largely implemented

Anonymous’s picture

Status: Fixed » Closed (fixed)