Jim Meyer - 2005-12-10

Logged In: YES
user_id=66093

Hello!

One way we could approach this would be to create a separate
table to relate items to users, then pull the userid column
out of the items table. With that, we'd be able to relate
any number of users to a particular item.

The more complex part would be UI and approvals. If Amanda
adds an item, does she add Brock or does Brock add himself?
If she adds Brock, Brock should be able to refuse to be
added. If Brock adds himself, Amanda should be able to
reject him as a party to her item. I suppose we could
leverage the user approval process for this, but I haven't
looked closely at that.

Alternately, we could add the concept of groups; items could
be owned by groups with people as members. However, this
would complicate the code as we'd want the group's items to
show up on each member's list, so we'd have to resolve each
user's group memberships then track back to items and, since
other people could be logged in changing group membership,
we'd have to do it each time. Ugh.

Cheers!

--j