<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket #2812: Groups description needs improving</title>
    <link>http://localhost/ticket/2812</link>
    <description>&lt;p&gt;
The 'What are Groups?' text at &amp;lt;&lt;a class="ext-link" href="http://demo.ckan.org/group"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://demo.ckan.org/group&lt;/a&gt;&amp;gt; is a
bit naff. Here is a suggested replacement:
&lt;/p&gt;
&lt;p&gt;
What are groups?
&lt;/p&gt;
&lt;p&gt;
Groups allow you to group users and data together so that they are
easier to manage. For example datasets in a group could be visible
only to group members, or publicly visible but only editable by group
members.
&lt;/p&gt;
&lt;p&gt;
Groups can be used to collect together datasets from a single
publisher, or related to a particular project, for example.
&lt;/p&gt;
</description>
    <language>en-us</language>
    <image>
      <title>CKAN</title>
      <url>http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png</url>
      <link>http://localhost/ticket/2812</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
      
        <dc:creator>toby</dc:creator>

      <pubDate>Wed, 08 Aug 2012 17:00:00 GMT</pubDate>
      <title>owner, status, milestone changed</title>
      <link>http://localhost/ticket/2812#comment:1</link>
      <guid isPermaLink="false">http://localhost/ticket/2812#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;owner&lt;/strong&gt;
              changed from &lt;em&gt;toby&lt;/em&gt; to &lt;em&gt;shevski&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;
                changed from &lt;em&gt;demo phase 4&lt;/em&gt; to &lt;em&gt;demo phase 3&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
@ira,
&lt;/p&gt;
&lt;p&gt;
do you want this change?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>shevski</dc:creator>

      <pubDate>Thu, 09 Aug 2012 10:14:00 GMT</pubDate>
      <title>owner changed</title>
      <link>http://localhost/ticket/2812#comment:2</link>
      <guid isPermaLink="false">http://localhost/ticket/2812#comment:2</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;owner&lt;/strong&gt;
              changed from &lt;em&gt;shevski&lt;/em&gt; to &lt;em&gt;toby&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Current text does need updating, but I think we need an explanation along the lines of:
&lt;/p&gt;
&lt;p&gt;
"Groups allow you to group together datasets under a organisation (for example, the Department of Health) or topic (e.g. Transport, Health) so make it easier for users to browse datasets by theme.
&lt;/p&gt;
&lt;p&gt;
Groups also enable you to assign roles and authorisation to members of the group - i.e. individuals can be given the right to publish datasets from a particular organisation."
&lt;/p&gt;
&lt;p&gt;
But even that could be clearer.
&lt;/p&gt;
&lt;p&gt;
Mark's text could be misleading since we haven't currently implemented private datasets or the right auth settings.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>toby</dc:creator>

      <pubDate>Thu, 09 Aug 2012 10:45:56 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost/ticket/2812#comment:3</link>
      <guid isPermaLink="false">http://localhost/ticket/2812#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;fixed&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
changed
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>markw</dc:creator>

      <pubDate>Thu, 09 Aug 2012 14:05:02 GMT</pubDate>
      <title>status changed; resolution deleted</title>
      <link>http://localhost/ticket/2812#comment:4</link>
      <guid isPermaLink="false">http://localhost/ticket/2812#comment:4</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;closed&lt;/em&gt; to &lt;em&gt;reopened&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                &lt;em&gt;fixed&lt;/em&gt; deleted
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
That's still fairly terrible. Also surely the auth stuff is part of Ross's Organizations stuff? It doesn't matter much if it's implemented yet, that's why this is a demo. But anyway, here is a more generic but readable version based on Ira's text above:
&lt;/p&gt;
&lt;p&gt;
Groups allow you to group users and data together so that they are easier to manage. Group owners can assign roles and authorisations, giving each project or department control of its own data publishing.
&lt;/p&gt;
&lt;p&gt;
Users can browse or search by group, making it easier to find the data they are looking for.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>toby</dc:creator>

      <pubDate>Thu, 09 Aug 2012 14:49:45 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost/ticket/2812#comment:5</link>
      <guid isPermaLink="false">http://localhost/ticket/2812#comment:5</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;reopened&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;
@markw
&lt;/p&gt;
&lt;p&gt;
I think you are talking about a different ticket
closing
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>toby</dc:creator>

      <pubDate>Thu, 09 Aug 2012 14:58:10 GMT</pubDate>
      <title></title>
      <link>http://localhost/ticket/2812#comment:6</link>
      <guid isPermaLink="false">http://localhost/ticket/2812#comment:6</guid>
      <description>
        &lt;p&gt;
@markw,
&lt;/p&gt;
&lt;p&gt;
Actually I see you also want some text changes
&lt;/p&gt;
&lt;p&gt;
please don't add unrelated discussions to tickets as it causes noise is disruptive and I just end up closing tickets as won't fix etc.
&lt;/p&gt;
&lt;p&gt;
I have updated the text as it was assigned to me and so i am still keeping this closed as I did as requested. Can you an ira sort this out between yourselves and create a new ticket when you have agreement
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>