Site structure

This integration allows for users to utilize Travelgrove’s search engine for travel, that scrapes the travel vendors, for cheap airfares, cruises, hotels, travel deals, and more. The system is geo-targeted, where users from Europe, Asia, United States, see results specific to their IP. Prices are scraped from over 100 travel sites, including all the major merchants, such as Orbitz, Priceline, Travelocity, Cheaptickets, etc.

Approximately 1/3rd of all online transactions over the internet are travel related, about 50 billion per year. The Travel Meta Search Module allows for Drupal website owners or builders of sites to monetize their existing traffic to their site, as well as provide a practical, useful, value-added tool. Some have even made a business model for their site based around this tool alone.

50% Revenue Sharing: Like Google’s Adsense, site owners are paid PPC (pay per click), which is much different than most other travel systems that pay PPS (pay per sale). So, you will make money every time someone uses the search (up to 20 cents). (this can average to be 1-2 fold more than the old PPS model that most companies use).

And finally, to get paid you must get a PubID, which you can pick up here:
https://www.travelgrove.com/affiliates/login.php (located in the links/banners section)

A Notifications plugin that allows users to subscribe to information updates based on a node's taxonomy. Primarily designed to integrate with nodeprofile to allow people to tag themselves, and receive updates based on the terms they have assigned to their nodes.

Usage examples

This module has been developed for School of Everything to keep users up to date on their interests. We use this module in conjunction with the taxman to allow users to tell us what subjects they are interested in.

This module also interfaces with Taxonomy NCO to provide notifications of similar subjects. Taxonomy NCO performs analysis on large freetagging vocabularies to infer semantic similarities, or 'other things that people might be interested in'.

A high level description of how this module was initially developed and implemented is available at http://drupal.org/node/284675.

Notes

The Node Taxonomy Manager (called the taxman) provides a "pretty" interface for taxonomy editing, and a set of tools to integrate with node profiles, allowing users to "add this tag to my profile".

This module adds a new url, node/[nid]/taxman, to facilitate the adding and removing of taxonomy terms in a themeable manner. This page is also available in a themeable block which could be added to a page.

NodeProfile Integration

This module was designed to allow users to manage their "interests". The "tagger" element of the module provides a block that will be displayed at taxonomy urls, providing links to "add this to my interests" or "remove this from my interests". Multiple types of node profile are supported and the action text can be managed for each one.

Current Limitations

Although the taxman can be used on any node type, there is currently a little too much focus on node profiles. Some work needs to be done to provide extra flexibility for non profile nodes.

If users are allowed to have more than one profile of the same type.... I don't know what would happen.

Usage Examples

Provides a clean set of API calls for working with taxonomy. Most of the core code has been taken from the taxonomy module, and turned into some smaller, more modular functions for use by other modules. Taxonomy REST provides some simple url based tools for adding and removing terms from nodes.

Taxonomy API

Taxonomy module does not really open up much of it's functionality to other modules. This means that, if your module needs to add or remove tags programmatically, then you have to end up duplicating a lot of the core taxonomy code. This module is an attempt to take a step to a clean interface to taxonomy functions. No actual end user functionality is added through this module.

Taxonomy REST

REST interfaces use URLs to interact with data. This module creates a set of URLs that will allow users with update privileges on a node to add and remove taxonomy terms using links rather than forms.

eg:
Add term 987 to node 123 :
http://example.com/services/taxonomy/node/set/123/987

Remove term 987 from node 123 :
http://example.com/services/taxonomy/node/delete/123/987

Security Considerations

Port to Drupal6 is available, check out the README for other instructions

The beta out now integrates with the pathauto API so its now you can manage your aliases in one spot

Like autopath but for taxonomy. Create one Vocabulary by content type, and for each node create a unique Term