skip to main content

kiesler.at
TommydeJesus
Back to Page | Back to History

Difference between revisions

Version 5, 2005-04-06 17:38 Version 6, 2005-04-06 17:38
Lines 4 - 13 Lines 4 - 13
   
One of the better ideas and yet not exploited nearly enough by the core. Why no association between groups and categories? Why no restrictions on Users as to which groups they can access to edit/create/view? I read where phpWS is concerned more with management than it is with content, but it seems the opposite is true. getting the content in the database is the priority, how it is accessed, and by who, not as much. So much power in one module used almost not at all. One of the better ideas and yet not exploited nearly enough by the core. Why no association between groups and categories? Why no restrictions on Users as to which groups they can access to edit/create/view? I read where phpWS is concerned more with management than it is with content, but it seems the opposite is true. getting the content in the database is the priority, how it is accessed, and by who, not as much. So much power in one module used almost not at all.
   
Currently categorizing data seems more important to the whats related feature than anything else. And while I think that feature is useful, it's more window dressing than anything else. Categorizing both the content as well as groups should be a priority. Currently categorizing data seems more important to the whats related feature than anything else. And while I think that feature is useful, it is more window dressing than anything else. Categorizing both the content as well as groups should be a priority.
   
Groups as they stand right now serve little purpose. Without tying Approval to specific modules and specific groups, the group feature has little to no power. Here is an example of what it should do. Groups as they stand right now serve little purpose. Without tying Approval to specific modules and specific groups, the group feature has little to no power. Here is an example of what it should do.
   
A group is created with 3 members. Lets call the group Financial Aid. This group gets categorized as well. We will call the category financialaid. The group can then only edit content in the financialaid category, and all new content is assigned to that category, unless another category is added to the group. The you could choose from 2,3,4 categories, depending on how many are assigned to a particular group. A group is created with 3 members. Lets call the group Financial Aid. This group gets categorized as well. We will call the category financialaid. The group can then only edit content in the financialaid category, and all new content is assigned to that category, unless another category is added to the group. The you could choose from 2,3,4 categories, depending on how many are assigned to a particular group.
   
One user in the group has approval. The other two can create/edit content. The user with approval is sent an e-mail that that content needs to be approved. This content goes into a holding area. The old content stays available to the general public until the new content is approved. This would apply to all content modules, including 3rd party modules. One user in the group has approval. The other two can create/edit content. The user with approval is sent an e-mail that that content needs to be approved. This content goes into a holding area. The old content stays available to the general public until the new content is approved. This would apply to all content modules, including 3rd party modules.