Compusure Drupal development

Drupal via the core Statistics module allows you to collect node view counts for the current day (daycount) and for 'all-time' (totalcount). This module was developed to allow you to define additional timeperiods in addition to the ones provided by the Statistics module. By enabling this module you can track node view and comment counts for shorter timeperiods such as 4 hours or for longer timeperiods such as 1 week or 1 month.
In order to make the collection of this data more useful I have also included simple Views integration that allows you to present a node's view count or comment count as a Views field and/or use the node's view count or comment count as a Views sort.
read more

The successor of the gcg project by the original contributor.
Key features:
- CCK based
- Complete views integration, including proximity searches
- Token integration
- Custom location taxonomy (requires the taxonomy module to be enabled)
- DHTML menu integration
- Preconfigurable maps
- Preconfigurable icons: built-in from the gmap project and Google charts based factory icons
- Completely new Geocoder result parser

Nice Map is a WMS client for Drupal. It comes with views module support and should work with latitude/longitude data stored by location module, or basic cck number fields.
It is currently offered as a developers preview.

Helper module to sort view ui select options. This module makes it easy to find the option you are looking for when adding fields and filters by sorting the options list.
Several sort options are provided.

OG Node Approval offers content review between group members allowing them to approve or reject content. When creating or updating content simply choose the audience for the content, save the node, and the module will insert group members from those respective audiences into the a node approval table.
After each member approves the content OG Node Approval will change the status of the node if configured to do so. It will either do nothing, use a separate node_status table, or use the node.status column to publish the node.
Output-wise, OG Node Approval displays the status of each group member for that content, and embeds a form within the content to allow group members easy access to change their status. Once they change their initial 'pending' status, they can no longer change it back. Also, users may publish comments when they reject content.
OG Node Approval integrates with Views 2 to allow fields, filters, and sorting based on either user node approval status or the overall status of the node.
This module was developed for a client of Kosada, Inc.

This module allows module developers to embed (attach) any form in a Views row display as a field.
It creates a simple hook API function to whitelist embeddable forms. Attached a simple form as an example.

This module allows to add fields to views containing custom text (PHP allowed).

Allows output of a theme-free, barebones display of a View, for embedding in other websites.

This module will add Transcriptions (or Closed Captioning) to video and audio files. It will also integrate with Media Player, YouTube API, Asset, and Embedded Media Field.
Ultimately slated for a Drupal 7 release (because of required hook_file and hopefully streaming packaging). However, there will be an initial Drupal 6 release with limited functionality.
Rough road map:
* Create CCK field type for limited CCK integration.
* Create stand-alone tables for File object integration.
* Hook into Media Player (and maybe JW Flash Player) to allow "pause and transcribe" functionality.
* Create XML files for said player(s).
* More!

Provides soft-deletion/trash bin functionality for Drupal. Content is "killfiled" instead of deleted outright, and can be retained for a configurable span of time before being permanently purged. All this is opaque to end-users as all killfiled content is pervasively hidden from them, but administrators can access and restore killfiled content when necessary.
An index of recently killfiled content is also made available as an RSS feed at killfile.rdf (this functionality requires the RDF module), allowing content deletions to be propagated from one Drupal instance to another that subscribes to its content (requires FeedAPI on the subscribing side in order to process the content deletions). This particular functionality is intended for use cases such as multi-instance scenarios based on the publish/subscribe architecture.
read more