<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket #2878: Roles and Permissions for Organisations</title>
    <link>http://localhost/ticket/2878</link>
    <description>&lt;p&gt;
As part of merging Organisations into core, it is necessary that we clarify the capacity field with which the users/datasets are added as members to the group 'subclass'.
&lt;/p&gt;
&lt;p&gt;
Rather than the capacity being an opaque string that implies auth but doesn't clearly specify it, we will use role names where roles are defined in the database - with a clearly defined set of standard roles.  The Role table is expected to have simply a string name/representation and acts as a container for permissions.
&lt;/p&gt;
&lt;p&gt;
Each permission is a string of the form object.action (such as package.add, group.delete) of which several are expected to be associated with a role.  This means the permission table will contain a string and a reference to the role.
&lt;/p&gt;
&lt;p&gt;
This work will require UI changes to the screens allowing users to be added to a group/organisation so that the list of available roles is available to add those users.
&lt;/p&gt;
&lt;p&gt;
[ ] Model for Role and Permission
&lt;/p&gt;
&lt;p&gt;
[ ] Logic layer changes for managing roles/permissions etc.
&lt;/p&gt;
&lt;p&gt;
[ ] Determine default roles, perhaps just admin/editor/viewer
&lt;/p&gt;
&lt;p&gt;
[ ] Fix the auth layer to use the permissions/roles - may be better implemented as another ticket.
&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/2878</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
      
        <dc:creator>ross</dc:creator>

      <pubDate>Wed, 22 Aug 2012 10:01:41 GMT</pubDate>
      <title>description changed</title>
      <link>http://localhost/ticket/2878#comment:1</link>
      <guid isPermaLink="false">http://localhost/ticket/2878#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;description&lt;/strong&gt;
              modified (&lt;a href="/ticket/2878?action=diff&amp;amp;version=1"&gt;diff&lt;/a&gt;)
            &lt;/li&gt;
          &lt;/ul&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>ross</dc:creator>

      <pubDate>Wed, 22 Aug 2012 12:41:57 GMT</pubDate>
      <title>description changed</title>
      <link>http://localhost/ticket/2878#comment:2</link>
      <guid isPermaLink="false">http://localhost/ticket/2878#comment:2</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;description&lt;/strong&gt;
              modified (&lt;a href="/ticket/2878?action=diff&amp;amp;version=2"&gt;diff&lt;/a&gt;)
            &lt;/li&gt;
          &lt;/ul&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>seanh</dc:creator>

      <pubDate>Thu, 18 Oct 2012 11:42:01 GMT</pubDate>
      <title>keywords set</title>
      <link>http://localhost/ticket/2878#comment:3</link>
      <guid isPermaLink="false">http://localhost/ticket/2878#comment:3</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;keywords&lt;/strong&gt;
              &lt;em&gt;organizations&lt;/em&gt; added
            &lt;/li&gt;
          &lt;/ul&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>seanh</dc:creator>

      <pubDate>Thu, 18 Oct 2012 12:05:06 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost/ticket/2878#comment:4</link>
      <guid isPermaLink="false">http://localhost/ticket/2878#comment:4</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;new&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;wontfix&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Closing as we've gone forward with a slightly different approach instead
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>