Unsupported

This module was in development but is on hold until further notice.

Adds a permissions model onto relationships that can be used to grant CRUD permissions for nodes for a specific user by role or specifically for them. These permissions are for the child nodes of the node a user has a Relation with Permissions with.

Example

User <-> Event <-> Photo
               <-> ... (any other

                ^ Is media from
      ^ Is attending

Example explained

We might have a 'Event', for example, which people can attend. We have a organizer (User(s)) and and attenders (Users). The relation between them and the event is 'is attending'.

All attending people will be able to add new 'Photo'(s) to the 'Event' when they are attending the 'Event'. We create a relation type 'is media from' to relate photo's (or anything else) to a 'Event'.

We add the Relation Permissions field to the relation type 'is
attending'.

Based on the relation User <-> Event we know that there can be permissions to add Photos to the event. The Relation Permissions gathers this information and allows to define role permissions per relation type. On a per relation basis (User <-> Event) a role can be assigned. Or it is possible to override the role and assign specific permissions for the relation.

Task to complete

About

Gantt Project Importer for Storm.

NOTE: The module is not functional yet.
Task Template Manager ( TTM ) is a plugin for Storm.

This would become the main module for managing task templates for Storm. The module will provide a standard method to save the task templates for automatic task creation.

This project will require a default parser to edit the template once its created. This will be maintained as a co-project of TTM.

Task Template Manager ( TTM ) will expose api for other modules ( parsers ) to store raw templates. These templates will be stored in the database as a serialized object. Further if the parsing logic to standard template is implemented in the parsers then they can be handled by the default parser later on. Thus eliminating the need to implement the complex logic of creating parent child relation while creating nodes. Also simultaneously eliminating the need to create a editor for uploaded templates.

Various API that would be exposed for parsers are.
i> saving their template into database.
ii> querying for templates.
iii>replacing existing templates.

More features will be included into the TTM, which would essentially be focused on user experience. So suggestions would be warmly welcomed.

ISI Link module aims to provide methods of importing data from InstantSoftware rental property management into Drupal.