Uses a PubSubHubbub implementation to syndicate content between any sites that also have this module, moderate incoming content, and publish. Currently supports two sites with identical content-types to share content between each other automatically.
The PubSubHubbub protocol allows for near-immediate updates from the publisher to the consumer, including updates to content. The consumer registers itself with the publisher automagickally when it initiates the first pull of content. The publisher will then ping all of its subscribers when syndicatable content has been created or modified. The consumer will pull in new content and make updates to existing consumed content, and put the new content into a moderation queue waiting for your editor's approval and placement of the content within the consumer site.
A great use case is creating a content hub for a series of stand-alone websites. They all subscribe to the content hub and publish to the hub, allowing all sites to pick and choose which content to use out of all of the websites combined.
Drupal Computing is a framework that facilitates distributed computing between Drupal and external programs written in non-PHP languages such as Java and Python. It is particularly designed for the cases where you need to use Drupal with non-PHP, computational-intensive code libraries (such as Apache Mahout, NumPy/SciPy, R, etc) for offline big data analytics. In addition to this Drupal module, you also need the companion Java and Python client library at https://github.com/danithaca/drupal-computing. The target audience would be developers who write Java/Python programs for Drupal.
Enables you to use your Drupal site to hold exams. Integrates with the Organic Groups module so that all group members will be put into exam mode when the time for exam arrives. In exam mode the users can only access a predefined set of pages in a predefined order, and all blocks are hidden except those you want to be visible in exam mode. Exam pages are only visible when taking exams.
How this module works for your students
It protects exam nodes(tests for instance) so that the users can't access them outside exams
When a user has exam he will be sent to the exam nodes(tests and webforms for instance) once he logs in.
When in exam mode the user can't visit any other pages except the exam node pages.
The exam module provides a navigation block named "steps" so that the user knows what step he is on and can jump between steps
The user will be "thrown" out of exam mode if he uses too much time
The exam module hides all blocks on the page and provides the function "exam_is_time" so that you can hide any other navigation when the user is in exam mode, you can even use a different theme when in exam mode