Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
Visitors can report an Issue (e.g. pothole) to a Jurisdiction (i.e. a Council). Once confirmed by the submitter, notification of an Issue is emailed to the relevant jurisdicton for resolution. Issues can include a latitude and longitude, category, description and a photo. Visitors can add Updates (comments) to an Issue, and indicate that the Issue is fixed. To minimise usage hurdles, user accounts are not required. To minimise spam, confirmation by email is required for new Issues and Updates.
The site uses multiple web services:
Google Maps: for map display, with markers representing Issues. http://maps.google.com/maps/geo: address geocoding to latitude and longitude. http://geonames.org: postcode geocoding to latitude and longitude. http://koordinates.com: reverse geocode API to find Jurisdiction from from latitude and longitude.
It's a working site, but the code needs plenty of work to make it applicable to other jurisdictions.
Do not expect this code to work "out-of-the-box". Only use this code if you can work on it directly to customise for your jurisdiction.
The module is a wrapper around the jQuery pause plugin and also provides an interface for adding the necessary selectors that the plugin would need for performing the pause events. It should also be noted that this module does integrate with jQ, however it does not require it in order to work.
Ideation is a Kit specification-compliant Feature Module. The Ideation feature is essentially a crowd-sourced suggestion box, which allows users to: suggest ideas, vote on and discuss already submitted ideas, surface most important/best ideas, as well as start discussions around ideas.
Module is intended to be compatible with all Kit-supporting distributions.
Drupal 7 version of the Ideation module is compatible with the OpenPublic distribution.
You can read more in blog posts from Development Seed, initial developer of the module, and Phase2 Technology developer of Drupal7 version of the module and current maintainer.
Instead of creating duplicate biblio records during imports, existing ones can be updated or the import can be skipped depending on a configurable duplicate detection strategy.
You can use an out of the box strategy or configure your own.
How to detect duplicates?
Use one or combine multiple of these strategies:
Hashing over configurable biblio fields.
ISBN
ISSN
DOI
PubMed ID
...
How to deal with duplicates?
Create duplicate record.
Skip import of a record.
Update the latest existing duplicate record.
Update the oldest existing duplicate record.
Update all existing duplicate records.
Create a new revision of the latest existing duplicate record.
Create a new revision of the oldest existing duplicate record.
Create a new revisions of all existing duplicate records.
How to merge duplicates?
Override the existing record.
Override the existing record but keep non empty values that do not exist in the record to be imported.
Only add new values that are empty in the existing record.
The Rules Autotag module takes a light-weight approach for autotagging full-text content by matching taxonomy terms (and optional Synonyms). Rules Autotag depends on the Rules module. Functionality is provided on different layers:
The API function rules_autotag_extract($text, $vocabulary) extracts terms from a given text which match a given vocabulary.
The basic rules action Extract terms (rules_autotag_extract_action) takes a text and a vocabulary as input and returns all matched terms.
The wrapper rules action set Autotag to terms list (rules_autotag_tag) directly stores the extracted terms into a terms list/field.
Comparison to related modules:
Taxonomy Autotagger takes a more user-oriented approach with by providing a AHAH-driven Autotag button.
Auto Tagging sends node content through any number of third party services to determine what the content is about.