From contact method | Todd's Email Contact Method |
---|---|
Item | task_handlers? |
Item version number | 1 |
I am okay with either proposal 1 or 2 below, but I prefer "handler" as a
term instead of "assignee" since the latter is more specific to
hierarchical management in organizations, and Deme is more general
purpose.
How would many agents be assigned to a TaskAssignment item? If you can do
that, why not just allow many agents to be pointed to by a handler field
within the Task?
Todd
On Thu, 7 Jul 2011, Mike Mintz wrote:
> [Mike Mintz][1] commented on [Project Model Proposal][2]
> Comment title: [task_handlers?][3]
>
> * * *
>
> Is the task_handlers supposed to correspond to "assignee" in most issue
> tracking systems? If so, making in a group seems like it will be unwieldy, as
> users will have to create groups containing themselves. I would like to
> propose two alternatives:
>
> 1. Call it "assignee" and have it point to an Agent. This could be a
> GroupAgent for things that belong to an entire group. (Simple)
>
> 2. Remove the field, add a new relationship type called "TaskAssignment" with
> task and agent fields. Zero, one, or many agents can be assigned to a task.
> (Complicated)
>
> [1]: http://deme.stanford.edu/viewing/person/7
> [2]: http://deme.stanford.edu/viewing/htmldocument/207
> [3]: http://deme.stanford.edu/viewing/textcomment/211
>
>