Under active development

The NPR project is a package of 6 modules.

• The npr_pull module allows a Drupal site builder to pull down NPR API stories and turn them into local drupal nodes, either in an ad-hoc fashion, or regularly via a cron.
• The npr_api module makes NPR API calls much easier, and provides a good starting point for the advanced drupal developer to build custom modules.
• The npr_push module allows admins to take locally-created stories and push them up to the NPR API. Please note: it requires a special API key + registering your IP address with NPR (you can only push with that key from that IP). Please contact NPR Digital Services for more help: http://info.ds.npr.org/contact.html
• The npr_fields module creates custom fields that are useful in mapping drupal data to/from NPR API data.
• The npr_story module leverages the npr_fields module, creating a ready-made drupal content type, geared for NPR API story pulls.
• The dev version of this package also contains npr_stations - which integrates with (but does not depend upon) npr_pull, allowing one to pull (or cron) stories provided only by certain stations.

If you'd like to talk beyond the issue queue about this module, look for CrookedNumber on irc -- #drupal, #drupal-contribute or, better yet, #drupal-pubmedia

Who should care?

This module provides a domain-aware Twitter block. If you have domains and want tweets to be displayed, this block may help you get there. If you don't know what domains are, you'll probably be happier with one of the many other Twitter modules available for Drupal.

About

This module provides a domain-aware block which retrieves and displays a tweet. The tweet displayed can be configured on a per-domain basis and will display one of the following: the latest tweet posted by a specified user or the latest tweet matching a specified search term.

The only data stored on the database are configuration data; this code generates JavaScript to fetch tweets directly from Twitter. This means that Domain Tweets won't increase the running time of cron jobs, but it also means that it's not possible to directly verify which tweets clients are seeing.

Installation

• Uncompress the Domain Tweets tarball into your modules directory (e.g. sites/all/modules).
• Go to admin/build/modules/list and enable Domain Tweets.
• Edit the default query at admin/settings/domain_tweets according to what you want to be displayed.
• "Edit Default Query" ->
• Name: This is only used in the administrative interface. Users will never see this value.

This set of modules aims to be a permanent datastore for important Drupal data. Based upon that data admins can configure tables and charts to provide informations for various people.

The main focus was put on the flexibility of that storage system. It builds upon the Drupal entity/field concept and can be configured to meet the needs of specific use cases. A simple example can be found in the datastore_system module.


MODULE OVERVIEW
---------------

* datastore_entity: Defines two entity types: datastore and datastore_domain.
A datastore is the container for time based data which is described with
default properties and can be enhanced with fields. Datastore domains are a
way to categorize datastores and work as bundle field (so you can attach fields
based upon the main domain).

* datastore_field: Actually the heart of this package. Provides a field type
to store timestamp/value pairs. In contrast to default fields it implements
a own storage procedure for performance issues.

* datastore_system: This contains some samples of how to use the datastore
package. It provides default logging informations like count of users/nodes
and distribution of taxonomy terms. Uses rules and the rules_scheduler module
to retrieve and store data.

* datastore_visualization: Contains simple visualization tools like a style

This module allows sites to have multilingual books.

Users can translate book pages in any language, without adding the translation to a new book outline.

Why

In Drupal, book outlines are not translated by the Internationalization or Locale modules. Before this module was coded, the solution was to create multiple books, one for each language. But this is very cumbersome and not effective at all, especially when having many languages.