Actively maintained

A unique set of tools used for Services 3.x.

Currently services_tools houses two modules.

• Historical
• Definition

You can see them below.

Historical

An API for providing historical versions of a Services API. Any quality services implementation should be versioned to ensure incompatibility issues do not arise. Even a simple API used internally between two machines can benefit from versioning since it will allow the machines to be updated independent of one another. For full fledged public APIs versioning is also essential to ensure the stability of the service.

Instead of always pointing clients to the current API, use a version number even if there is only one. For example, api/foo becomes api/1.0/foo. This ensure that when you make changes and create api/1.1/foo that clients using api/1.0/foo continue to work and can upgrade at their leisure.

The API is quite flexible and provides a number of ways the historical API may be implemented. For details see services_historical.api.php and the original issue which describes the thought process.

Onboarding is the process where site owners help new site members to orient themselves and take some important initial steps toward becoming full-fledged members of the site. This process is critical in various websites created with Drupal, as it smooths the user experience.

Whitney Hess wrote that "[m]ost companies think that getting people to sign up is the ultimate challenge, but what about getting them oriented to your site and actually using it? That process of helping people get started is called onboarding, and it’s crucial that you give it the attention it deserves."

The goal of this project is to build a flexible, configurable system for helping Drupal site owners build onboarding processes custom to their needs.

Examples of possible onboarding actions for a conference website, for example, include:
- Buy your ticket
- Buy some training
- Fill in your profile
- Submit sessions
- Vote on sessions
- Submit bofs
- Vote on bofs
- Find other people who have similar profile fields
- etc.

Minnesota Historical Society Collections Modules currently provide a PHP Stream Wrapper for MHS Images along with a field to download MHS images to a Drupal site.

Apache Solr Node Exclude module. Provides simple system for manually excluding nodes from the Apache Solr modules indexing process.

DrupalGapps is a project that aims at seamlessly integrating Google Apps with Drupal.

Extended DrupalGapps is a project that aims at extending the current feature-set of the existing module.

The project aims at extending the DrupalGapps (Google Apps Framework for Drupal) module by:
* Porting DrupalGapps module to Drupal 7.
* Improving and adding more features to existing DrupalGapps API.
* OAuth integration.
* Registration sub-module development.
* Developing wrapper API and application for Google Documents List API using DrupalGapps API.

(my project for the Google Summer of Code) - Tiago Carmona Palacios

Media:Youtube is a nice module that provides Youtube support for the Media family of modules. It has many features, but lack support for uploading. While direct upload is handled nicely in the Media Mover module in Drupal 7, Browser upload still isn't supported. It was supported via the module Video Upload in Drupal 6, written by bojanz.

The main difference between Direct upload and Browser upload is that in the Direct upload users upload the video to Drupal website, and then Drupal uploads it to the service. Its great when you need to moderate the content of videos, but greatly increases bandwidth usage. Browser upload uploads the file directly to Youtube, and after the upload is completed it saves a file reference (ID) in the Drupal database. This method, while don't support moderation of the content, saves the extra bandwich usage of the Direct upload. Also I'm planning to add support to have Youtube account associated per user or having just one per site, to prevent the upload of videos that might violate the Youtube terms of use.