cck, groups, categories hybrid
Categories represent areas of influence. They don’t correspond directly to location, rather locations are constructed by intersecting vocabularies and providing a means of display for the resulting nodes.
Groups can be associated with categories, as a single node. This node is also a cck node.
Some categories are also groups.
- Workflow / Actions
- na_arbitrator
This last is a work by Earl providing an API for node access modules to interoperate.
Currently, access modules directly insert records into the node_access table. If any module has inserted a “yes” record, access is granted.
na_arbitrator provides. Currently, there exists in the package a module workflow_access which ties node access to workflow state by role.
Relationships
- Node {has a} Workflow State
- Node {aggregates to} multiple categories
- Groups {have many}
- Managers
- Members
For each category/group, there are 3 local “roles”:
- Not a member
- Member
- Manager
A content item lives in the intersection of the union of each set of categories which share a container
For example:
?? (FAQs) AND (History OR Math) AND (“History: Early 20th” OR “Math: Trigonomery”) ??
Here, the first category is the content type. Each content type has fields, workflow, and behavior. Type determines workflow. This makes workflow and behavior global in the sense that it is the same in all departments. This is true at least in our first prototype.
It would be possible to add more “roles” to a group type using CCK user ref fields. Behaviors could then be associated with these local roles using a na_arbitrator node access module.