Projects tagged ‘information_retrieval’ and ‘python’

NLTK — the Natural Language Toolkit — is a suite of open source Python modules, linguistic data and documentation for research and development in natural language processing, supporting dozens of ... [More] NLP tasks, with distributions for Windows, Mac OSX and Linux. [Less]

The "xappy" python module is an easy-to-use interface to the Xapian search engine. Xapian provides a low level interface, dealing with terms and documents, but not really worrying about where terms ... [More] come from, or how to build searches to match the way in which data has been indexed. In contrast, "xappy" allows you to design a field structure, specifying what kind of information is held in particular fields, and then uses this field structure to index data appropriately, and to build and perform searches. [Less]

webXcreta sucks down the latest entries for the currently most popular blogs on the Intarweb. It then parses each weblog entry using natural language processing (NLTK) and figures out what words are ... [More] verbs, nouns, adjectives, definite articles, etc. Next, it creates weighted values based on how high-ranking each blog is (higher ranking blogs have a greater influence over sentence count, word order, and vocabulary). The reassembled bits get spit out and posted here. [Less]

Xappy2 is a redesign and expansion of the Xappy project. STATUS: we're just setting the project up at present - it's not yet in a state to be used. Whereas Xappy consisted of only a python module ... [More] providing a higher-level interface than Xapian, Xappy2 consists of three parts: xappy2.core: python module built on top of xapian, similar to xappy, but with some API improvements. xappy2.server: a search server built on top of xappy2.core, providing a REST API to xapian. xappy2.client: clients (in various languages) for xappy2.server. Note: all the code in the Xappy2 repository is under the MIT license (unless specifically noted otherwise). However, parts of it currently depend on Xapian, which is currently licensed under the GPL. This means that, at least, you will need to comply with the terms of the GPL when distributing xappy2.core and xappy2.server. Whether you need to comply with these terms when distributing xappy2.client (which only depends on xapian via the REST API) is questionable. [Less]