This module provides an Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), interface to the Bibliography Module.

Currently it only exposes metadata from the biblio module; however if there was demand I believe that it could be made configurable to expose other node types as well.

This module was inspired by and I have used some code from http://physnet.uni-oldenburg.de/oai/ writen by Heinrich Stamerjohanns.

The og_actions module is a collection of 5 actions for use with the actions module and workflow module. These actions facilitate the use of organic groups with the actions and workflow modules, allowing administrators to create rules to modify the organic group information for specific nodes.

A module to create individual aggregator for Organic Groups using Aggregator.

Key features
------------------
- Feed content filter (including keyword filter and excluding keyword filter)
- An individual feed page of every feed source is available

Requirements
------------------
- Aggregator module
- OG module

The OG Audience module provides an "audience" tab and/or a block on node pages that allows Organic Groups (OG) users to change the audience of existing content. A user can add a node to one or more of his subscribed groups. A group administrator can remove a node from his group(s).

Users with the proper permission can change the audience of a node even if they do not have the permission to edit the node.

This is a small module to set the authoring group for any group post.

This module has been sponsored by http://www.wiki9999.org/

This module provides each group with a calendar showing only the group's events.

Sponsored by Raven Brooks of BuyBlue.
Developed by CivicSpace Labs.

讓每個群組都擁有一個討論版，並限制為僅有群組成員可以檢視該討論區裡的文章。

Creates a forum per organic group and restricts viewing forum nodes by group membership.

Go ahead and use the dev release from the 30th of August. It contains a bug fix to 2.0.

The OG Join Role module simply adds a "join organic groups" permission to the Organic Groups module. A use case for this would be if you have a site where only members of a certain role are allowed to join an organic group.

The module is written in an all-or-nothing sort of way - either certain roles can join any and all groups or they can join no groups. It will not work on a per-group basis.

In addition to granting/denying permission to join a group, the module also modifies any text and/or links to join a group unless the user has the proper role. For example, the module removes any "og/subscribe" links on the page and replaces them with "nicer" text that you define in the admin settings.

Promote users that join certain groups to a special role.

Choose one role that all users who join the groups you select will be promoted to. Should a user leave that group, he will be demoted again.

The OG Public Access module allows Organic Groups (OG) administrators to control public access to their groups' content. This module does not require group administrators to be granted the site-wide administer nodes permission.

The use case for this module is for a site with teams of writers submitting content privately in their groups, and editors controlling what is allowed to go public in specific groups.

This module allows you to assign group-specific roles to users which are restricted to the groups they are in. In other words, using this module, you can assign the role "contributor" to a user in a group, and the user will only have the permissions of that role while he is in that particular group.

Requires og.module and og_forums.module.

Read the history of this module: http://drupal.org/node/87679

Other features of this module allow you to:

• Assign a default role to all new users who sign up to your site.
• Notify group admin of new group subscribers. Requires mimemail.module.
• Set a default "Founder" group role for users who create groups.
• Set a default group role for new subscribers to a group.
• Create subgroups. Requires og_subgroups.module.
• Comes with it's own access control for optionally integrating the taxonomy access control (TAC) and organic groups (OG) modules. See: http://groups.drupal.org/node/3700.
• Supports Content Access (http://www.drupal.org/project/content_access) and Access Control List (http://www.drupal.org/project/acl) access control modules. See http://groups.drupal.org/node/5392
• Works with OG Vocabulary (http://www.drupal.org/project/og_vocab) module. See this issue: http://drupal.org/node/162649
  

This Module adds Online Status Indicator Support for the most common Instant Messangers into Drupal.
At the Moment "Onlinestatus Indicator" has support for:

• AOL Instant Messanger
• ICQ
• Jabber (with onlinestatus.org or edgar)
• MSN Messanger (with onlinestatus.org)
• Yahoo! Messanger
• Skype (SkypeWeb or Jyve)
• X Fire

Important: Your PHP installation needs CURL Support.

This module helps with integration the openads adserver 2.3 (http://www.openads.org/) into Drupal. Escpecially it helps with seperating
code (where to place ads in templates) and content (which ads to serve). This module will generate all the JavaScript required to
invoke openads adserver.

Features include:

• Define which ads show to which user roles
• Extended information in ad_channel, including full url and user role
• Ads are available as blocks or can be inserted manually into templates.

The module was sponsored by Ambiweb GmbH

The 4.7 version was originally developed by JanRain to implement OpenID consumer support in Drupal using the JanRain PHP OpenID and Yadis libraries.

There is a 4.7-2.x branch developed by James Walker and Rowan Kerr that supports OpenID 2.x, and includes a server and a client component, including attribute exchange.

Find out more about OpenID at openid.net.

Allows you to delegate your URL as an OpenID. This prevents your from having to run your own OpenID server while allowing you to harness your URL as an OpenID. If you switch OpenID Providers, just switch your settings in the module. This is based on this article which covers the topic in more depth.

OpenPackage Video enables video functionality for your site. Submitted videos are transcoded to FLV format so they can be viewed directly in the web browser. Transcoding either occurs locally using FFmpeg, or videos are transferred to OpenPackage.biz, transcoded and then returned to your site.

OpenResort is a new solution for the drupal community that provides full featured online booking functionality for all types of accommodation. OpenResort also offers a suite of other solutions for the tourism industry. For more details visit http://www.openresort.org/

The OpenResort Community Edition is completely open source and free to use by anyone. This version allows for the creation of properties, and any number of bookable units under a property. Units can only be created one at a time, regardless if they are of the same type. Rates and availability also must be added one at a time for every unit. Check out a demo here. PLEASE NOTE the download includes a patch file which needs to be applied to the ecommerce suite. Once this patch is applied ecommerce can no longer be used as a standard shopping cart solution.

Note: this is still under development. Do not deploy on production sites.

This module allows you to search multiple OpenSearch feeds at the same time. The results are aggregated and cached locally, and results are fetched incrementally as you page further down the results.

It works best if the search sources are all run on the same software. The OpenSearch module for Drupal can provide the appropriate feeds, and will also pass along relevance information. OpenSearch Aggregator will sort the results by descending relevance globally.

Note that you need to patch node.module with the provided patch for now.

Turns your Drupal site into an OpenSearch client capable of searching 3rd party sites that offer OpenSearch RSS feeds. See http://opensearch.a9.com/ for more information.

RSS parsing is handled by the Magpie RSS library. This enables search requests to remote sites to be cached in order to politely limit the amount of overhead and traffic caused.

There is now a working group to discuss Lucene and Nutch: http://groups.drupal.org/lucene-and-nutch

From the README:
*Objective*
The goal of this module was to extend the capabilities of the original
og_mandatory_group module to allow as many mandatory groups as the user wants for:
1) All users
2) Group administrators/owners
3) any role
As all of the changes constitute a module with drastically different capabilities,
it didn't make sense to patch the original module with this code. Additionally,
most of the old code was thrown out and a ton of new code put in place.

This isn't simply a patch to og_mandatory_group. Read the rest of the README for a full rundown of features and functionality.

organic groups list manager (OG2List)可以讓群組的成員擁有一個郵件論壇（mailing list），裡面的郵件會被保存在一個討論版裡，群組成員可以用電子郵件來進行回應，或是直接在討論版裡回應。
為甚麼要使用這模組呢？ 因為：

1. 電子郵件也是內容，可以儲存在 Drupal 這種 CMS 裡。
2. 透過你的網站（討論版和 RSS）與郵件論壇一起協同合作的群組成員，是同樣的一群人。群組與郵件論壇的成員都在一份名單上。使用者對於網站和郵件論壇的個人設定，也都在同一個網站上可以完成。
3. 群組應該要可以動態地建立郵件名單，不需要系統管理者的手動介入。你的網站也不需要對電子郵件伺服器下指令，避免不必要的安全性漏洞。

本模組使用 organic groups 和 forum 模組，作為內容和成員的管理。討論版是和 OG_forum 模組箱連結，並使用 comment 和 comment mover 模組來管理對於郵件論壇的回應。

當使用者在註冊時輸入一個群組註冊碼時，會自動地成為該群組的成員。可以協助使用者在一個擁有太多群組的網站裡，加入某個特定群組。功能包括：

• 群組註冊碼只適用於設定為開放性或審核制的群組。邀請制和封閉式的群組是無法使用註冊碼的。
• 群組註冊碼可以被加到邀請朋友的電子郵件訊息裡，也可以在每個使用者的個人資訊頁裡看到。
• 群組註冊碼可以在註冊表單裡設為必須或選填的項目。
• 使用群組註冊碼來註冊並加入群組的使用者，可以選擇性地被賦予一個額外的角色。
• 您也可以重設群組註冊碼，讓舊的註冊碼都無法再使用。

This module is add-on for the Organic Groups module designed to facilitate users in joining a specific group upon registration (or afterwards as a member) on sites that have a number of groups that is too large to easily browse through or show in the registration form.

A new user will be auto-approved as member of a group when they supply a group code at registration. You may combine this feature with the usual use of groups in the registration form. Users may also visit the "Use group code" page to join a group using a code.

1. 可建立階層式的組織架構，並將使用者對應到組織架構中的角色。
2. 可限定node只能被隸屬於某一組織架構單元的使用者所瀏覽。

The OI module allows users to be categorized in a hierarchical manner in OI entities. Entities by default propagate membership up (so that if a user in a member of a child entity, they are usually in the parent entity as well). Entities have roles, which can be filled by members of the entity, and fields (support for this is very limited in the current code) which can support various meta-data about the entity. Entities are categorized into different types of entities ("groups", "committees", "organizations", "sites", etc). The OI entities can be used for node access restrictions. There is also a text filter that allows you to display entity membership. Node access restrictions do not apply to users with "administer content" permissions (but this is true for all node access modules).

Sadly, documentation is very much lacking. I will work on this eventually.

This is a simple filter that adds in a configurable CSS classname to all outgoing links (e.g., links that point to a *different* website).

What's so useful about that? Well you can then easily add a little icon next to each link indicating that it takes you to a different site. Or you can use some unobtrusive JavaScript to hook in some useful effects, warnings, or whatever you want.

Creation of a new outline module based on book.module.

This module is a general use outline module. With it, you can create volumes of posts of any type (whereas the book module uses 'book pages' by default).
You can mix node types within each volume, but each volume has a default node type.

The module is based on beginner's and pwolanin's patch here: http://drupal.org/node/65319 and http://drupal.org/node/81226 .

I welcome your feedback.

A small module that allows users to override the default publishing options for any new nodes they create and any nodes they can edit without giving them the 'administer nodes' permission. Hopefully, the permissions in Drupal 6.x will be a bit more granular to include this type of functionality and this module will die a happy death.

NOTE: This module still needs some use-case testing as I haven't really run it through the grinder.

Effectively allows a plug-n-play style implementation of Google Web
Toolkit AJAX widgets within a Drupal website. Widgets can be used
within CCK, a block, or as an input filter.

The module is in use here: http://oyoaha.com/ and here:
http://oyoaha.com/wearehere

This module provides an easy way to lay-out a view without the need for rewriting a new module for the layout each time. The layout is controlled from the administration page. In some way it's an extension and generalization of the view bonus module. The most powerful aspects of this module are when used with CCK as a way to set the layout for a field. It provides a means for styling the elements in a node without a full template rewrite, and, more importantly, provides a way for including a media gallery within a node (this application is more workflow dependent and implements aggregation via views).

The module is in use here: http://oyoaha.com/portfolio and here: http://oyoaha.com/drupal/view/portfoliogalleries