Free request free catalogs software for linux

External Site Catalog allows you to index and search external sites in a Plone site.

ExternalSiteCatalog is a web crawler that can index external sites and make them searchable in Plone.

You can specify the sites to index in a Plone Configlet, and directly index them from Plone, or let a scheduler do the job.

Searching the external sites is done in a special portlet that is installed with ExternalSiteCatalog.

External sites are not searchable in the normal Plone catalog, but are only available in a separate catalog in the portal_externalcatalog tool.

Request Tracker (RT) is an enterprise-grade ticketing system which enables a group of people to intelligently and efficiently manage tasks, issues, and requests submitted by a community of users.
The RT platform has been under development since 1996, and is used by systems administrators, customer support staffs, IT managers, developers and marketing departments at thousands of sites around the world.
Written in object-oriented Perl, RT is a high-level, portable, platform independent system that eases collaboration within organizations and makes it easy for them to take care of their customers.
RT manages key tasks such as the identification, prioritization, assignment, resolution and notification required by enterprise-critical applications including project management, help desk, NOC ticketing, CRM and software development.
RT is used by Fortune 100 companies, government agencies, educational institutions, and development organizations worldwide.
Main features:
- RT is your organizations focal point for tracking tasks, issues, knowledge, and collaboration.
- Its easy to submit, assign, prioritize, search, escalate, and report on issues.
- RT keeps track of each tickets full history and metadata to help your organization better retain knowledge and analyze trends.
- RT can track multiple projects for multiple teams within a single installation.
- RT tracks critical system metadata, including time spent per action, due dates, and estimated time to completion.
- Its easy to record private comments that are not available to end-users.
- RTs web interface comes complete with an intuitive "iterative" search interface that allows end users to construct complex queries by pointing and clicking within their web browsers.
- Users can save and edit queries later, using their browsers "bookmarks" feature.
- Users dont need to do anything special -- they can just send email to RT. RT will take care of thanking them for their message, automatically routing it to the appropriate staff, and making sure all future correspondence gets to the right place.
- RT provides a simple, self-service interface that allows end users to view their own active and resolved tickets online.
- RTs web interface is designed to be easy to use from any browser. Just working in Internet Explorer and Netscape isnt enough. Your staff need to be able to get work done anytime, anywhere.
- Whether you use Windows, MacOS or Unix, your staff already have everything they need to access RT.
- RT works great from a handheld or screen-reader (for the blind.) Best Practical is working with users to ensure that a future release is fully compliant with Section 508 accessibility requirements.
- A powerful new command-line interface that allows power users to quickly and easily work with RT, even if theyre out of the office is currently available for testing by the public.
- Youve got customers around the world. RT lets you interact with them in their own language. Internally, RT converts all data to UnicodeTM, so you can respond to users in their native tongue, but work in yours.
- Youve got staff around the globe. RTs web interface has been fully internationalized. Right now, RT speaks English, German, French, Dutch, Portuguese, Russian, Czech, Japanese, Traditional Chinese, and Simplified Chinese. Adding new languages is a breeze, if you need something RT doesnt support yet. On login, RT automatically detects which language each user prefers, so staff members can collaborate even if they speak different languages.
- Unlike costly proprietary issue tracking systems, an administrator can have a basic RT system up and running in an afternoon.
- RT is built to be useful right out of the box. You dont need expensive consultants
- Theres no client software to manage or keep up to date. Your existing web browser and email clients are all you need.
- RT is written in object-oriented perl. Not only do you get the complete source code to the product with every download, but your staff can begin customizing RT to meet your needs within hours.
- RTs web interface and mail gateway are built on top of the same API we publish for you to write your own tools on top of. The interface is documented and there are numerous third party tools to use as examples and templates.
- Every organization needs to track specialized data. RT lets you define list-based and freeform custom fields to help track your tickets. Once you create custom fields, its easy to search on them, just like RTs predefined fields.
- All of RTs mailing rules are based around a powerful custom business logic system called "Scrips." Scrips make it easy for a local administrator to make RT do ANYTHING whenever a ticket is created or updated, without making it hard to upgrade.
- RTs entire web interface is built on a flexible templating system that lets you build your own web-based tools or alter RTs look and feel to better fit your organization.
- If you dont want to radically change RTs interface, you can add your own components to RTs pages. A web callback system lets you drop miniature templates into RTs web pages.
- If you need even more power, "Code overlays" let you customize RTs internal behaviour without touching RTs core libraries.
Enhancements:
- This release includes numerous small cleanups and improvements.
- It fixes the dreaded "infinite relogin" bug.

Bundle::Catalog is a bundle to install all Catalog related modules.

SYNOPSIS

perl -MCPAN -e install Bundle::Catalog

This bundle includes all the modules used by the Perl Catalog module.

A Bundle is a module that simply defines a collection of other modules. It is used by the CPAN module to automate the fetching, building and installing of modules from the CPAN ftp archive sites.

CGI::Request is a parse client request via a CGI interface.

SYNOPSIS

use CGI::Request;

# Simple interface: (combines SendHeaders, new and import_names)

$req = GetRequest($pkg);

print FmtRequest(); # same as: print $req->as_string


# Full Interface:

$req = new CGI::Request; # fetch and parse request

$field_value = $req->param(FieldName);
@selected = $req->param(SelectMultiField);
@keywords = $req->keywords; # from ISINDEX

print $req->as_string; # format Form and CGI variables

# import form fields into a package as perl variables!
$req->import_names(R);
print "$R::FieldName";
print "@R::SelectMultiField";

@value = $req->param_or($fieldname, $default_return_value);

# Access to CGI interface (see CGI::Base)

$cgi_obj = $req->cgi;
$cgi_var = $req->cgi->var("REMOTE_ADDR");


# Other Functions:

CGI::Request::Interface($cgi); # specify alternative CGI

CGI::Request::Debug($level); # log to STDERR (see CGI::Base)


# Cgi-lib compatibility functions
# use CGI::Request qw(:DEFAULT :cgi-lib); to import them

&ReadParse(*input);
&MethGet;
&PrintHeader;
&PrintVariables(%input);

This module implements the CGI::Request object. This object represents a single query / request / submission from a WWW user. The CGI::Request class understands the concept of HTML forms and fields, specifically how to parse a CGI QUERY_STRING.

Contentment::Catalog is a Perl module to provides categorization and indexing features.

SYNOPSIS

# Get a list of the available indexes
my @indexes = $context->catalog->indexes;

for my $index (@indexes) {

# Get a list of avilable terms
my @terms = $index->terms;

for my $term (@terms) {

# Get a list of generators
my @generators = $index->generators;

}

}

One frequently controversial component of a CMS is the categorization system. Contentment attempts to avoid this problem by providing a framework for building categorization systems so that any controversy just leads to the replacement of whatever system someone doesnt like.
That is, rather than create some all encompassing categorization system or some dead-simple one that your grandma who thinks the boogey-man is going to jump out of the her CD-ROM drive can use, you can have either or both or neither depending upon your need. Thus, instead of providing a category or taxonomy system, Contentment provides the indexing system, which allows you to implement whatever category system you prefer.

Class::IntrospectionMethods::Catalog can manage catalogs from IntrospectionMethods.

Exported functions

set_method_info( target_class, method_name, info_ref )

Store construction info for method method_name of class target_class.

set_global_catalog (target_class, ...)

Store catalog informations. The first parameter is the class featuring the methods declared in the global catalog.

Following paramaters is a set of named paramaters (e.g. key => value):

name

Mandatory name for the global catalog

list

array ref containing the list of slot and catalog. E.g.:

list => [
[qw/foo bar baz/] => foo_catalog,
[qw/a b z/] => alpha_catalog,
my_object => my_catalog
],
isa

Optional hash ref declaring a containment for catalog. E.g:

list => [ foo => USER ,
admin => ROOT ],
isa => { USER => ROOT }

Then the ROOT catalog will return foo, and the USER catalog will return foo and admin.

help

Optional hash ref (slot_name => help). Store some help information for each slot.

set_global_catalog will construct:

A ClassCatalog object containing the global catalog informations.

A sub_ref containing the ClassCatalog object in a closure.

Returns ( slot_name, sub_ref ). The sub_ref is to be installed in the target class.

When called as a class method, the subref will return the ClassCatalog object. When called as a target class method, the subref will return an ObjectCatalog object associated to the ClassCatalog object stored in the closure.

These 2 object have the same API. ObjectCatalog is used to contain catalog changes that may occur at run-time. ClassCatalog informations will not change.

Jifty::Request is a canonical internal representation of an incoming Jifty request.

This document discusses the ins and outs of getting data from the web browser (or any other source) and figuring out what it means. Most of the time, you wont need to worry about the details, but they are provided below if youre curious.

This class parses the submission and makes it available as a protocol-independent Jifty::Request object.

Each request contains several types of information:

actions

A request may contain one or more actions; these are represented as Jifty::Request::Action objects. Each action request has a moniker, a set of submitted arguments, and an implementation class. By default, all actions that are submitted are run; it is possible to only mark a subset of the submitted actions as "active", and only the active actions will be run. These will eventually become full-fledge Jifty::Action objects.

state variables

State variables are used to pass around bits of information which are needed more than once but not often enough to be stored in the session. Additionally, they are per-browser window, unlike session information.

continuations

Continuations can be called or created during the course of a request, though each request has at most one "current" continuation. See Jifty::Continuation.

(optional) fragments

Fragments are standalone bits of reusable code. They are most commonly used in the context of AJAX, where fragments are the building blocks that can be updated independently. A request is either for a full page, or for multiple independent fragments. See Jifty::Web::PageRegion.

SQL::Amazon::Request::Help is an Interface to retrieve Help content.

SYNOPSIS

$dbh = DBI->connect(dbi:Amazon:, $amznid, undef,
{ amzn_mode => books,
amzn_locale => us,
amzn_max_pages => 3
})
or die "Cannot connect: " . $DBI::errstr;
#
# search for some Perl DBI books
#
$sth = $dbh->prepare("
SELECT ASIN,
Title,
Publisher,
PublicationDate,
Author,
SmallImageURL,
URL,
SalesRank,
ListPriceAmt,
AverageRating
FROM Books
WHERE MATCHES ALL(Perl, DBI) AND
PublicationDate >= 2000-01-01
ORDER BY SalesRank DESC,
ListPriceAmt ASC,
AverageRating DESC");

$sth->execute or die Cannot execute: . $sth->errstr;

print join(, , @$row), "n"
while $row = $sth->fetchrow_arrayref;

$dbh->disconnect;

DBD::Amazon provides a DBI and SQL syntax abstraction for the Amazon(R) E-Commerce Services 4.0 API *aka* ECS. < http://www.amazon.com/gp/ >. Using the REST interface, and a limited SQL dialect, it provides a DBI-friendly interface to ECS.

Be advised that this is ALPHA release software and subject to change at the whim of the author(s).