Ticket #200 (closed enhancement: invalid)
Sort out user & node relationships
| Reported by: | jim | Owned by: | jim |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Views & content types | Keywords: | |
| Cc: | jim | Estimated Number of Hours: | 0.0 |
| Add Hours to Ticket: | 0 | Billable?: | yes |
| Total Hours: | 0 |
Description
There's a lot of data in the site related through node and user references. Most of that is fine, but many of these are a bit contrived and some have lost data integrity as the project has evolved.
For example: https://tech.transitionnetwork.org/trac/ticket/178#comment:3 - Users are allowed to chose initiatives they are related to, but not projects, in their profiles. BUT they can also be related via Point of Contact fields, or Core team, or others... The named connections are strong but overlap with the user->initiative on the user profile.
We need a consistent, strong and well utilised way of relating users (profile nodes) to the things they work on (projects and initiatives nodes for now). See: http://drupal.org/project/noderelationships
OR we just need to be clear about the ways a user can relate to things and ensure they're explicitly built into the system. That's mostly there, but could do with tightening up and extending.
It's possible we'd need user relationships too, for stronger social networking and maintaining teams: http://drupal.org/project/user_relationships
Not urgent, but worth making a plan sooner rather than later.
Given we're going to re-think the user account thing for the US initiative adding ticket, bringing this back in case it's worth it. If it's not relevant to now, de-select phase 4.