Under active development

Auto-generates HILCC (Hierarchical Interface to the Library of Congress Classification) taxonomy terms for nodes that have LCC call numbers (library-assigned numbers like "QA 76.73 .P224 2005"). This can help you build a Drupal site that auto-organizes by a hierarchic subject tree.

For instance, items with different call numbers like QA76.73 and QA75 would be clustered under the Drupal category Engineering & Applied Sciences > Computer Science. The taxonomy terms are generated during node creation and update, and now optionally during cron runs and using node batch operations (from admin/content/node).

Possible uses are:

• Subject-based search, for instance using the Apache Solr module
• Subject-based breadcrumb, using the Taxonomy Breadcrumb module.

(For an example that uses all these modules, see the links to the demo below).

The Aurigma Uploader for Imagefield module integrates the commercial Aurigma Image Uploader with Drupal. Multiple images are uploaded in a single batch into a multiple imagefield.

6.x-1.x supports version 5 of the uploader.
6.x-2.x supports version 6 of the uploader.
6.x-2-dev now adds ajax loading of images. Please try it!

For an open source java uploader see JIFUpload.

Requirements
- Modules: CCK, filefield, imagefield
- Aurigma is a commercial product. A valid license key is required.
- Users must have Java installed, or allow ActiveX for IE browsers.

Configurable features
- Selection of content type used.
- Selection of imagefield field used.
- Size of the uploader on the page.
- Aurigma parameters may also be entered manually in the module's admin page.

Benefits
- Allows batch image uploading to imagefield.
- Set image descriptions in the uploader and/or the imagefiled.
- Deletions are handled by imagefield and filefield.
- Image types are limited to jpg, gif, png.

Suggestions
- FileField Paths enhances the file path options provided by Token. Without Token images are saved in the default files directory.

Media: Brightcove adds Brightcove as a supported media provider.

PURL 1.0-beta6 requires CTools. Please make sure you have added it to your modules before running update.php.

PURL (pronounced 'perl') stands for Persistent URL. PURL is an API module -- it is meant to be a helper (and one that does some heavy lifting at that!) for other modules interested in using elements of the page request to sustain information between pages without using a SESSION or other hackish means.

Translation: PURL does absolutely nothing for the end user out of the box without other modules that take advantage of its API.

It is an API module that provides a way for other modules to take advantage of concepts using custom_url_rewrite_outbound() without having to write the complex logic that URL rewriting often requires. An example implementation of this API can be found in the spaces module.

PURL can work with these page request elements:

• Path prefixes: http://example.com/foo/node/5
• Path prefix pairs: http://example.com/group/1/node/5
• Query string: http://example.com/node/5?group=1
• Domains: http://example.com/node/5