<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Transition Technology: Ticket #200: Sort out user &amp; node relationships</title>
    <link>http://localhost:8080/trac/ticket/200</link>
    <description>&lt;p&gt;
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.
&lt;/p&gt;
&lt;p&gt;
For example: &lt;a class="ext-link" href="https://tech.transitionnetwork.org/trac/ticket/178#comment:3"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://tech.transitionnetwork.org/trac/ticket/178#comment:3&lt;/a&gt; - 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-&amp;gt;initiative on the user profile.
&lt;/p&gt;
&lt;p&gt;
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: &lt;a class="ext-link" href="http://drupal.org/project/noderelationships"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/project/noderelationships&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
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.
&lt;/p&gt;
&lt;p&gt;
It's possible we'd need user relationships too, for stronger social networking and maintaining teams: &lt;a class="ext-link" href="http://drupal.org/project/user_relationships"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/project/user_relationships&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Not urgent, but worth making a plan sooner rather than later.
&lt;/p&gt;
</description>
    <language>en-us</language>
    <image>
      <title>Transition Technology</title>
      <url>/trac/chrome/site/TransitionNetwork-Logo-Web-Small.jpg</url>
      <link>http://localhost:8080/trac/ticket/200</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <item>
      
        <dc:creator>ed</dc:creator>

      <pubDate>Fri, 17 Jun 2011 11:52:23 GMT</pubDate>
      <title>owner, status changed; milestone set</title>
      <link>http://localhost:8080/trac/ticket/200#comment:1</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/200#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;owner&lt;/strong&gt;
              changed from &lt;em&gt;ed&lt;/em&gt; to &lt;em&gt;jim&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;new&lt;/em&gt; to &lt;em&gt;assigned&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;milestone&lt;/strong&gt;
                set to &lt;em&gt;Phase 4&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
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.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>jim</dc:creator>

      <pubDate>Wed, 22 Jun 2011 21:29:57 GMT</pubDate>
      <title>milestone deleted</title>
      <link>http://localhost:8080/trac/ticket/200#comment:2</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/200#comment:2</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;milestone&lt;/strong&gt;
                &lt;em&gt;Phase 4&lt;/em&gt; deleted
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Only tangentially relevant to &lt;a class="assigned ticket" href="http://localhost:8080/trac/ticket/262" title="innovation: US users adding Ini profiles through the US site (assigned)"&gt;#262&lt;/a&gt;, deselecting phase IV.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>jim</dc:creator>

      <pubDate>Wed, 14 Dec 2011 13:25:16 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost:8080/trac/ticket/200#comment:3</link>
      <guid isPermaLink="false">http://localhost:8080/trac/ticket/200#comment:3</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;assigned&lt;/em&gt; to &lt;em&gt;closed&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                set to &lt;em&gt;invalid&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
This is a whole project in itself, one with little defined benefit.
&lt;/p&gt;
&lt;p&gt;
Closing -- reopen of it's important and we know what's needed.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>