Free search engine marketing software for linux

iSearch engine project is an internal web site search engine.
Built to run as a CGI module, iSearch performs a searching for one or more character sequences ( terms ) within documents in a web site, without the needing of external indexing and filtering tools, like, for example, a database engine.
iSearch performs a real time elaboration of HTML documents in a web site, every time it is invoked. Documents are found, filtered from unnecessary parts, like HTML tag, and then inspected searching for the input terms.
iSearch acts under the directives set in its configuration file. You can set one or more starting search path, exclude file or directories from scanning, set your own output templates, and so on.
So if you want to add an internal search engine in your web site, iSearch is one of your possible solutions.
iSearch is written in C and the source code is based on Yed technology.
Main features:
- iSearch is a CGI module written in C, available for both GNU/Linux and Windows environment.
- iSearch latest release has been developed and tested within an Apache HTTP server. OS involved are Slackware GNU/Linux and Windows XP SP2, both on a i686 architecture.
- When invoked, iSearch scans recursively directories in a web site extracting files so-called documents. In every document extracted, iSearch performs a filtering to delete unnecessary information, like HTML tags. Then, the pure resulting text is inspected searching for the characters sequences received in input, so-called terms.
- A term can be a single word, but also a sequence of words enclosed with character "; in this latter case, the sequence will be treated as a single term ( i.e. "sowing the seeds of love" ).
- All documents containing all the terms will be output according to user templates and related environment.
- All terms are matched in boolean AND mode: only a document containing all terms is considered as a matched document.
- All terms are matched in case-insensitive mode.
Enhancements:
- The ID Input parameter is now optional.
- If omitted, it defaults to the first < root > element of the configuration.
- Handling of eventual error explanation string was added in displaying error templates, through the new token "%det".
- Its now possible to search for strings enclosed with quotation marks (").
- The source code has been totally reorganized.
- The < replace > element was added in the configuration file.
- This element contains a list of strings to replace or cut from documents to inspect.

Search::InvertedIndex is a manager for inverted index maps.

SYNOPSIS

use Search::InvertedIndex;

my $database = Search::InvertedIndex::DB::DB_File_SplitHash->new({
-map_name => /www/search-engine/databases/test-maps/test,
-multi => 4,
-file_mode => 0644,
-lock_mode => EX,
-lock_timeout => 30,
-blocking_locks => 0,
-cachesize => 1000000,
-write_through => 0,
-read_write_mode => RDWR;
});

my $inv_map = Search::Inverted->new({ -database => $database });

##########################################################
# Example Update
##########################################################

my $index_data = "Some scalar - complex structure refs are ok";

my $update = Search::InvertedIndex::Update->new({
-group => keywords,
-index => http://www.nihongo.org/,
-data => $index_data,
-keys => {
some => 10,
scalar => 20,
complex => 15,
structure => 15,
refs => 15,
are => 15,
ok => 15,
},
});
my $result = $inv_map->update({ -update => $update });

##########################################################
# Example Query
# -nodes is an anon list of Search::InvertedIndex::Query
# objects (this allows constructing complex booleans by
# nesting).
#
# -leafs is an anon list of Search::InvertedIndex::Query::Leaf
# objects (used for individual search terms).
#
##########################################################

my $query_leaf1 = Search::InvertedIndex::Query::Leaf->new({
-key => complex,
-group => keywords,
-weight => 1,
});

my $query_leaf2 = Search::InvertedIndex::Query::Leaf->new({
-key => structure,
-group => keywords,
-weight => 1,
});
my $query_leaf3 = Search::InvertedIndex::Query::Leaf->new({
-key => gold,
-group => keywords,
-weight => 1,
});
my $query1 = Search::InvertedIndex::Query->new({
-logic => and,
-weight => 1,
-nodes => [],
-leafs => [$query_leaf1,$query_leaf2],
});
my $query2 = Search::InvertedIndex::Query->new({
-logic => or,
-weight => 1,
-nodes => [$query1],
-leafs => [$query_leaf3],
});

my $result = $inv_map->search({ -query => $query2 });

##########################################################

$inv_map->close;

eSearch provides a Java-based search engine.
eSearch is a server side Java-based search engine which supplies basic search capabilities for Web use. Its basic capabilities can be extended to include intelligent agents and other expert-system behaviors.
Main features:
- Free and Open Source
- Written in Java, and therefore platform-independent
- Uses Lucene API for Text and Index operation.
- Supplies basic search capabilities comparable to other existing search engines, for both intranet and internet use.
- Allows the basic capabilities to be extended to include intelligent agents and other expert-system behaviours, with the end result of smarter searching than is possible with existing search engines.
- Scaleable to truly mind-boggling dimensions of collections and users.
- Can dynamically index multiple servers and sources simultaneously
- Have a powerful Developer kit that include eSearch TAG Library, Samples & Documentation.
- Powerful Administration Center that let you control all crawl & search operation in your enterprise.
- Extensible architecture. You can plug new component from third party.
- Can be easily integrated with any other Web Applications: i.e. ePortal, eContent, eForum, eFAQ, eHelpDesk.

MKSearch provides a Web metadata spider and search engine.

MKSearch is a metadata search engine that indexes structured metadata in Web documents instead of free text in the document body.

The data acquisition system conforms to the Dublin Core metadata in HTML recommendations, and supports other application profiles, such as the UK e-Government Metadata Standard.

It also indexes native RDF formats, including RSS 1.0. The system has five major components: a Web crawler, an HTML document validator and formatter, a set of custom indexers, an RDF storage and query system, and a public query interface, provided through a standard servlet container.

System composition

The MKSearch system is composed of several other free software components. Further details are provided in the MKSearch development plans.

JSpider
JSpider is a Java Web crawler engine that has pluggable interfaces that can be used to add custom processing and content handling. MKSearch uses custom SAX-based content handlers for extracting metadata from Web documents.

Sesame
Sesame is a set of RDF processing and storage APIs and applications that includes RDF data query facilities. MKSearch uses Sesame to store indexed metadata in RDF format and to search the repository via the public query interface.

JTidy
JTidy is a utility for correcting common HTML markup errors and is used to convert HTML documents to XHTML so they can be processed using SAX.

WWW::Search::Nomade is a Perl class for searching Nomade.

SYNOPSIS

use WWW::Search;

my $oSearch = new WWW::Search(Nomade);

$oSearch->maximum_to_retrieve(100);

#$oSearch ->{_debug}=1;

# Create request
$oSearch->native_query(WWW::Search::escape_query("cgi"));

# or Make an international search (on google db)
$oSearch->native_query(WWW::Search::escape_query("cgi"),
{ opt => 1 });

print "I find ", $oSearch->approximate_result_count(),"n";
while (my $oResult = $oSearch->next_result())
{ print "Url:", $oResult->url,"n","Titre:", $oResult->title,"n"; }

This class is an Nomade specialization of WWW::Search. It handles making and interpreting Nomade searches http://www.Nomade.fr, a french search engine.

This class exports no public interface; all interaction should be done through WWW::Search objects.

Search::QueryParser parses a query string into a data structure suitable for external search engines.

SYNOPSIS

my $qp = new Search::QueryParser;
my $s = +mandatoryWord -excludedWord +field:word "exact phrase";
my $query = $qp->parse($s) or die "Error in query : " . $qp->err;
$someIndexer->search($query);

# query with comparison operators and implicit plus (second arg is true)
$query = $qp->parse("txt~^foo.* date>=01.01.2001 date<<less