Hi everyone,

I would like to implement 2 use cases, read a lot about the possibilities with Drupal and have some ideas on how to implement it. Maybe you can give me some feedback on the feasibility?

1) Company user group

Use case: User can register, create associated company profile, invite colleagues to join company profile

Implementation idea: Use Organic groups, create company as additional content type, only allow 1 company content type per group, invite-functionality handled by OG?

2) Proposal management

Use case: User can create proposals, only visible to him, submit for review, admin does voting on submitted proposals (result not visible to user)

Implementation idea: Proposal as new content type, "submit" status as content field, views to restrict visibility to creator only, view for user without voting element, separate view for admin for submitted proposals with voting possibility (fivestar)

Any feedback on those implementation ideas? Is it do-able?

Regards
bluepuma

Comments

shyamala’s picture

1) Company user group

Use case: User can register, create associated company profile, invite colleagues to join company profile

Implementation idea: Use Organic groups, create company as additional content type, only allow 1 company content type per group, invite-functionality handled by OG?

MAKE COMPANY the GROUP NODE, this way you fill in the company information only once for every Group/Company you create. GROUP NODE == COMPANY

2) Proposal management

Use case: User can create proposals, only visible to him, submit for review, admin does voting on submitted proposals (result not visible to user)

Implementation idea: Proposal as new content type, "submit" status as content field, views to restrict visibility to creator only, view for user without voting element, separate view for admin for submitted proposals with voting possibility (fivestar)

You can used the published and unpublished status associated with every node to achieve this by configuring the permission based on the content type. You can define author based node type based permissions for each CCK in the admin, user Permissions section.

Views is a query building module and can not be used for permissions.