<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket #190: Package comments</title>
    <link>http://localhost/ticket/190</link>
    <description>&lt;p&gt;
Cost 7 days
&lt;/p&gt;
&lt;p&gt;
When viewing a package, users can read user comments and leave their own. Users need to be logged in to leave a message. Comments appear immediately. A mechanism for deleting unwanted comments is provided to an authorized user. Comments are sorted with the most recent first. Comments are available for read, creation and deletion in both the Web UI and over the REST API.
&lt;/p&gt;
&lt;p&gt;
The admin for the package and a superuser can delete unwanted comments, both on the package page and a collation of all comments on their user page. Users can delete their own comments(?) Need to consider whether over the REST API we encourage the use of a 'frontend user' APIKEY which can be used to leave comments for another, actual user.
&lt;/p&gt;
&lt;p&gt;
Example at bottom of package page:
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Leave a comment:&lt;/strong&gt;
&lt;/p&gt;
&lt;table class="wiki"&gt;
&lt;tr&gt;&lt;td&gt;Subject&lt;/td&gt;&lt;td style="text-align: center"&gt;  &lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;_
&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Comment&lt;/td&gt;&lt;td style="text-align: center"&gt;  &lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;_
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;p&gt;
&lt;br /&gt;
&lt;/p&gt;
&lt;table class="wiki"&gt;
&lt;tr&gt;&lt;td&gt;Submit button
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;p&gt;
&lt;strong&gt;Comments:&lt;/strong&gt;
&lt;/p&gt;
&lt;table class="wiki"&gt;
&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Explanation doc&lt;/strong&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;em&gt;Posted on 25h May 2009 by http://bertdavies.myopenid.com&lt;/em&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;It says on the pollution data web page that not all the stations have a CO2 sensor, so you have to extrapolate from the ones that do. See my visualisation of CO2 across London for an idea of what you can do: bertdavies.com/pollution-2008.jpg
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;table class="wiki"&gt;
&lt;tr&gt;&lt;td&gt;&lt;strong&gt;More info&lt;/strong&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;em&gt;Posted on 24th May 2009 by http://ronsmith.myopenid.com&lt;/em&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Excellent data, but why is there no value in the CO2 column for some of the testing stations?
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;
&lt;h1 id="Implementationdetails:"&gt;Implementation details:&lt;/h1&gt;
&lt;p&gt;
Comments table is with columns:
&lt;/p&gt;
&lt;table class="wiki"&gt;
&lt;tr&gt;&lt;td style="text-align: left"&gt;id &lt;/td&gt;&lt;td&gt; package_id &lt;/td&gt;&lt;td&gt; date (date) &lt;/td&gt;&lt;td style="text-align: right"&gt; comment (multi-line text)
&lt;/td&gt;&lt;/tr&gt;&lt;/table&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/190</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
      
        <dc:creator>pudo</dc:creator>

      <pubDate>Sun, 01 Aug 2010 18:07:54 GMT</pubDate>
      <title>owner, status, type changed</title>
      <link>http://localhost/ticket/190#comment:1</link>
      <guid isPermaLink="false">http://localhost/ticket/190#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;owner&lt;/strong&gt;
              changed from &lt;em&gt;rgrp&lt;/em&gt; to &lt;em&gt;pudo&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;type&lt;/strong&gt;
                changed from &lt;em&gt;enhancement&lt;/em&gt; to &lt;em&gt;defect&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
This will be solved using an external plugin and the disqus service.
&lt;/p&gt;
&lt;p&gt;
A current test version of the external code is at: &lt;a class="ext-link" href="http://bitbucket.org/pudo/ckandisqus"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://bitbucket.org/pudo/ckandisqus&lt;/a&gt;
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>pudo</dc:creator>

      <pubDate>Tue, 03 Aug 2010 07:34:12 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost/ticket/190#comment:2</link>
      <guid isPermaLink="false">http://localhost/ticket/190#comment:2</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;
fixed as of cset:1389
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>