Contributed Module Ideas

I eventually want to hunt for someone to do development on this idea, but first I'd like to find out how it can be designed to be of greatest benefit to the community.

I want to be able to manage access to a node, with CCK fields. The node should be viewable by both a role and at least a single (ideally multiple) user(s) not in the role.

Do you know of a module that would/could tie a user profile to a CCK created content-type?
Here's our problem: we are moving away from CiviCRM (don't get me started with the issues). Can we tie a particular content-type (or multiple content-types) through the use something like the Subforms modules to user profiles? Can we then let user creation spawn two records-- a user record; and a new node coupled to the user record? Then the content node could be used in isolation; or the user account could be edited later and those changes would alter the associated node?

I just posted my outline and UI design for a new image gallery module to Drupal on the Raincity Studios blog. It uses CCK, imagefield, and imagecache, and has both galleries and images as nodes.

I'm looking for feedback on the idea, and to see if people are interested in having this built, either through a reverse bounty or some other method.

Purpose of module:

This module will implement Twitter-style following functionality for Drupal community websites. On Twitter you follow people you find interesting and people who find interesting follow you. People you are following show up on your home page in a river-of-news format. My proposed module would do the same thing for a Drupal community site. You follow people who's post you find interesting and are followed by people who find you interesting.

I wrote a bit here about how the twitter model is useful.

Node_media is intended to be successor of node_images. Currently is in his very early stages of development and I want to contribute conducting efforts in right direction.

Based on previous lines, this project should achieve 2 goals:

1. Stabilize current node_media to at least Release candidate for D5 and then start porting it
2. Conduct candidate new features of node_images to node_media 2.0 (i.e.: thickbox, internatinalization, ...)

After 3 months of intense work... I'm proud to announce first stable release of Organic Groups Subscriptions ! now available.

Special thanks to gustav, he is a wonderful mentor and project lead.

Hope you enjoy it...

Blessings!

Every time I migrate a site (which seems to happen about once a month on average...) I find myself in a bit of a debate: I don't want to put the site into maintenance mode because I want people to be able to view the site, but I do want to prevent users from creating new content that would get lost in the migration. Ideally you can cut this period down to a half hour or so through the use of short DNS "time to live" values, but there is also some amount of time where you have this problem.

I'm excited about building a module that, if designed properly, would useful to others. I see how it might be useful for the development of a human resources department for personnel reviews and really any place where reports or static documents pass from one party to another.

I am building a community site based around an organization. We produce custom reports for many of the community members and provide them through a very simple and custom php app on our website. I want to move this to drupal to take advantage of the other powers to build community, as well as flexibility to improve access to these reports for archive purposes.

This has been floating around in my head for several months, but I've not developed a drupal module before so I crave review, comment and even participation.

Over the last year and a half FeedTheBull has become one of the largest, independent social networks for the investment community. We have recently moved to the Drupal platform and are looking for an experienced Drupal developer to join our team. We have a strong direction of where we are going, and we would like to take someone along with us.

Requirements:

• Drupal Core 5.x +
• Module Development
• Custom Theme Development
• CCK
• Taxonomy
• JQuery/Interface
• Extensive Drupal experience
• Extensive experience with OOP PHP
• AJAX/XML
• JavaScript
• Security

The Subscriptions module provides a range of subscription types. Users can subscribe to individual content items, to all items of a particular content type, to all posts in a particular blog, or to all items tagged with a particular taxonomy term. The range of subscription types can be extended by additional add-on modules. This guide describes the hooks a module needs to implement to provide new subscription types.

Reuters released a web service called Open Calais. It is built on clear forest technology that has been around for a while.

You can throw text at it and get tags organized by country, personalities, industry terms, ... in RDF format back. It is of better accuracy than http://tagger.flaptor.com/findtags, http://tagthe.net or yahoo terms extraction API (http://www.programmableweb.com/api/yahoo-term-extraction, http://drupal.org/project/yahoo_terms)

You can try it here:
http://autotagger.opensynapse.net/

This session will introduce Drupal users to the beauty that is creating custom modules. We will start out by doing an overview of what a module is, what it is composed of, and how modules interact with the Drupal core. The lesson quickly turns from lecture to hands-on when the basics are over and students code their modules and learn all about Drupal's hooks and API offerings.

This session will go over how to build and architecture a new custom Drupal module.

Who is this course for?

Introducing ourselves
SONY BMG Music Entertainment is a global recorded music joint venture with a roster of current artists that includes a broad array of both local artists and international superstars, as well as a vast catalog that comprises some of the most important recordings in history. Sony BMG Music Entertainment is 50% owned by Bertelsmann A.G. and 50% owned by Sony Corporation of America.

Job duties
•Working with a team of designers and Drupal developers to create compelling and cutting edge web sites and web applications

I'm building/have built a social networking site, and coming across Twine made me realize that it would be nice to build some kind of "Trust" module, where users could specify what level of trust they attribute to others, and this trust level would affect how content shows up and is organized.

Trust Levels

Specifically, I'm thinking of 5 levels of trust:
* Always Hide - Essentially equivalent to "block user," this would make it so the blocker doesn't see any content from the blocked user

After spending hours with Taxonomy trying to use it to construct a single tiered Library, The problem was that the module of taxonomy was too specific to what it does. I also saw that with in my code, I was running multiple select statements that were unnecessary. In addition my library was small, and I feared using a growing database full of taxonomy data would hinder the performance of my script. Simply put, Taxonomy was to high level for what I needed, and didn't provide the low level functionality and flexibility that I wanted.

I needed to write my own library routine, and modifying taxonomy was not an option. I wasn't using this to classify content, but as a simple place holder for strings. I then went off to write taxonomy 2.0, but found the task was too large on its own to complete in a reasonable time.

Just looking around for components for an issue tracking system. One key feature would be that users can setup their own controlled vocabulary for their issues...

Hi all.. I've found a little tool to be usefull in one of my sites. Let me explain.. Under certain situations, I should be sure the user completes a step of a form or a quiz, or just I do need the user to select one Item or accept the terms and conditions before letting him continue, but I have a lot of documentation in the site about how to help filling these forms, or just with enough knowledge to help the user to comply the requeriments.. Even if the user must complete the operation, it should be able to see other content in the site, but do nothing else..

I'm working on an idea for a new module and was wondering if anyone had any feedback. It may overlap a bit with existing modules (especially Views), but I think it's different and potentially interesting.

Basically, the idea is this: Sometimes, when viewing/editing/creating a particular type of content, you might want to do so through a "lens" that only shows you a subset of fields that you are interested in at that particular time. You only want to deal with those particular fields, without having to deal with the node as a whole (which may be very large and complex).

My name is Matthew Pare and I'm a Co-Chair for the "Community and Core" track for Drupalcon Boston 2008. Over the last couple of weeks we have been planning and brainstorming to make Drupalcon Boston 2008 the best Drupalcon to date! One of our recommended track session topics is "Community: Role of the Contributor" and since your viewing this post on the Contributed Module Ideas group I thought you would be excellent candidates for submitting sessions on the topic.

I saw this great piece from John VanDyk : http://www.sysarchitects.com/node/64

We've been having problems with our staff and their connectivity to the server. That is a separate track of what we are running down. But this got me thinking: could I write a desktop application?

<

ul>

In the last week, I've helped two people deal with {node_access} table issues. http://drupal.org/node/197878 is fairly typical of this sort of problem.

Node Access is spooky stuff for most people, and there is generally no way to fix Node Access issues -- or bulk reset NA rules -- without writing SQL.

Yesterday I downloaded and played with the Drigg module. Among its features is an option to let a privileged role submit content as a different user. The list of spoof users is also an administration option. The motivation for this is clear... it lets a handful of people easily make a site look like a bustling community. This is great for jumpstarting your Drigg site (which is designed to be a Digg clone), but how ethical is it?

OK, so I'm working on integrating Domain Access with OG.

Problem is, the current node_access system uses OR based permissions. What I really need is the option to set AND based permissions. For example:

-- Current node_access rules

-- Desired rules

See http://drupal.org/node/191375 for a full discussion and some possible options.

Over the last weekend I started to develop the Feed Element Mapper - a Feed API compatible module that ultimately should allow you to map any item on a feed to any field on your feed item node. Currently there is an implementation for taxonomies.

Check out the screencast on our blog here:

http://www.developmentseed.org/blog/2007/oct/30/pick-it-feed-stick-it-no...

and you can grab the module here:

http://cvs.drupal.org/viewvc.py/drupal/contributions/sandbox/alex_b/feed...

(I just upgraded it to FeedAPI 1.0 compatibility)

If one wants to have multiple multi-page articles on a site, one seems to be really limited right now. Especially if one wants to have the nodes in an ordered tree and wants to be able to insert new nodes anywhere in that tree and also wants to be able to move nodes from one position to another.

So far I am using node_relativity which allows me to put nodes in a tree, but that tree is only ordered by the nodes id. I also had to heavily modify the output of the module as I need to output a table of contents of the article.

A few technical notes for developers concerning how MySite interacts with non-Drupal data and application sources.

First, a little history. The core goal of the MySite module is to abstract content published to a Drupal site. So the MySie distribution supports content types native to Drupal. The reason for this is scope: I don't have time to solve every problem, so I focus on those.

I've been mucking around on FaceBook for the last week. It's cool, and the apps are nice.

And the dirty little secret is that MySite supports this type of "app" functionality through its plugin API -- it might even be made to read Facebook apps.

So where's the developer love?

/me stops whining

[UPDATE: I have stopped reading this thread.] 23-OCT-2007.

Hi. Allow me to introduce myself. I'm a student at university in the US in a graduate web development course specifically oriented toward drupal development, including module development. In searching for a project to do for this class, I've become rather frustrated. Every time I think of something to do I find that its already been done by some module or another, or can be done using some combination of existing modules. That's a good thing for the drupal user community, but not so good for me.

I just proposed this session for Barcelona. Hope it makes sense.

Looking deeply at the MySite / Panels integration question, I think what we need is a unified abstraction API that lets modules find, collect, render, and display data in multiple contexts.

Working on a unified API might be the best direction. Take a look at the session proposal and this brief overview.

I just updated the RPG project page with a more current description. To add to the discussion, I'm cross-posting the juicy parts here and at Drupal RPG. (Sorry in advance for the spam if you're subscribed to the three posted groups...)

RPG

The engine itself does little more than provide a core to build a game with. Although it is intended to be for online RPG's, there is no reason the base couldn't be expanded to create other types of games, such as Turn-Based Strategy games, RTS games, or even slidescrollers. The engine is able to do this by providing basic functionality for administrators to create, use, and share 'rulesets'.

Rulesets are definitions of the Types, Attributes, and Actions used to create in-game objects. They may be created in forms available to game administrators, and may also be imported/exported from forms or even files. RPG Object Types follow inheritance rules, and may even include multiple parents, allowing types to share and even override attributes and actions.

Hello,

I welcome any initiative that aims to reduce time wasted, redundancy etc.

This group was created to allow people to post their new module ideas, BEFORE they create them, before they start coding.

What about all the modules already created, where redundancy already exist?
Can this group be used to find a proper resolution?

Example:
On the dev list, we found those four very related modules:
http://drupal.org/project/default_filter
http://drupal.org/project/filterbynodetype
http://drupal.org/project/filter_default

I've got a Slideshow pro module complete with views and filter integration lying around in my drawers. didn't come around to roll out a drupal project, will happen ASAP.

For a client that whishes to subscribe to feeds of tags and posts in closed Organic Groups we are planning to build a module, that allows users to generate unique URLs with tokens that can be used e. g. for subscribing with a feed reader.

Anybody interested/up to sth. similar or any references?

To get this group kick started, I thought I would post my own recent idea for a new module. It’s still in the proposal stage and has no code, but early feedback will definitely help its development…