<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket Query</title>
    <link>http://localhost/query?component=ckan&amp;milestone=v0.7&amp;group=status&amp;order=priority</link>
    <description>The open source data portal software</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/query?component=ckan&amp;milestone=v0.7&amp;group=status&amp;order=priority</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
        <link>http://localhost/ticket/51</link>
        <guid isPermaLink="false">http://localhost/ticket/51</guid>
        <title>#51: Upgrade CKAN to use sqlalchemy and vdm v0.2</title>
        <pubDate>Mon, 08 Sep 2008 19:00:38 GMT</pubDate>
        
        <dc:creator>rgrp</dc:creator>

        <description>&lt;p&gt;
Move CKAN codebase to use sqlalchemy (rather than sqlobject) along with vdm v0.2.
&lt;/p&gt;
&lt;p&gt;
NB: the upgrade itself should not be too hard, the work will be in providing a satisfactory migration script to convert existing data on ckan.net service.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/51#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/4</link>
        <guid isPermaLink="false">http://localhost/ticket/4</guid>
        <title>#4: Find a package</title>
        <pubDate>Mon, 10 Jul 2006 16:43:40 GMT</pubDate>
        
        <dc:creator>johnbywater</dc:creator>

        <description>&lt;h2 id="Asa"&gt;As a&lt;/h2&gt;
&lt;p&gt;
Visitor
&lt;/p&gt;
&lt;h2 id="Iwantto"&gt;I want to&lt;/h2&gt;
&lt;p&gt;
Locate packages that I am, or might be, interested in
&lt;/p&gt;
&lt;h2 id="Sothat"&gt;So that&lt;/h2&gt;
&lt;p&gt;
I know what packages exist and can read the information associated with those packages
&lt;/p&gt;
&lt;h2 id="Notes"&gt;Notes&lt;/h2&gt;
&lt;p&gt;
Find a package by searching by (or some combination thereof):
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;tag
&lt;/li&gt;&lt;li&gt;string contained in title or description
&lt;/li&gt;&lt;li&gt;license
&lt;/li&gt;&lt;/ol&gt;</description>
        <category>Results</category>
        <comments>http://localhost/ticket/4#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/44</link>
        <guid isPermaLink="false">http://localhost/ticket/44</guid>
        <title>#44: Provide RSS/Atom Feed of Repository History</title>
        <pubDate>Tue, 08 Jan 2008 10:34:17 GMT</pubDate>
        
        <dc:creator>rgrp</dc:creator>

        <description>&lt;h1 id="AsA"&gt;As A&lt;/h1&gt;
&lt;p&gt;
Visitor
&lt;/p&gt;
&lt;h1 id="IWantTo"&gt;I Want To&lt;/h1&gt;
&lt;p&gt;
Get an RSS/Atom Feed of the Repository History to use in my feed reader (or elsewhere).
&lt;/p&gt;
&lt;h1 id="Details"&gt;Details&lt;/h1&gt;
&lt;ul&gt;&lt;li&gt;Preference for Atom.
&lt;/li&gt;&lt;li&gt;should just add parameter to /revision/list/ (or /revision/) to select atom format e.g. ?format=atom.
&lt;/li&gt;&lt;li&gt;should have a 'days' attribute specifying number of days back to go e.g. &amp;amp;days=30
&lt;/li&gt;&lt;/ul&gt;&lt;h1 id="Cost"&gt;Cost&lt;/h1&gt;
&lt;p&gt;
Low
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/44#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/52</link>
        <guid isPermaLink="false">http://localhost/ticket/52</guid>
        <title>#52: Paginated results sets should be customizable across domain objects</title>
        <pubDate>Thu, 09 Oct 2008 10:54:08 GMT</pubDate>
        
        <dc:creator>rgrp</dc:creator>

        <description>&lt;ol&gt;&lt;li&gt;Tag results could/should show number of associated packages
&lt;/li&gt;&lt;li&gt;Package results should show title (and be in list)
&lt;/li&gt;&lt;li&gt;Pagination should be able to be applied to other result sets than simply register listing (e.g. search results ...)
&lt;/li&gt;&lt;li&gt;Revisions should be listed in a table with full details
&lt;/li&gt;&lt;/ol&gt;</description>
        <category>Results</category>
        <comments>http://localhost/ticket/52#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/54</link>
        <guid isPermaLink="false">http://localhost/ticket/54</guid>
        <title>#54: Support dump and load of CKAN data to JSON</title>
        <pubDate>Mon, 13 Oct 2008 14:24:43 GMT</pubDate>
        
        <dc:creator>rgrp</dc:creator>

        <description>&lt;h1 id="Asa"&gt;As a&lt;/h1&gt;
&lt;p&gt;
Sysadmin
&lt;/p&gt;
&lt;h1 id="Iwantto"&gt;I want to&lt;/h1&gt;
&lt;p&gt;
Dump (serialize) CKAN data to a simple transport format (e.g. JSON) and be able to load it again.
&lt;/p&gt;
&lt;h1 id="Details"&gt;Details&lt;/h1&gt;
&lt;ul&gt;&lt;li&gt;Already have simple db dump. However dumping to JSON has various advantages, particularly where changes to the data need to be made upon reloading (e.g. during a migration).
&lt;/li&gt;&lt;li&gt;Dump should include *all* CKAN data (i.e. all the data in the CKAN db tables)
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost/ticket/54#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/55</link>
        <guid isPermaLink="false">http://localhost/ticket/55</guid>
        <title>#55: Code to migrate data from v0.6 to v0.7 using dump and load</title>
        <pubDate>Mon, 13 Oct 2008 14:30:40 GMT</pubDate>
        
        <dc:creator>rgrp</dc:creator>

        <description>&lt;p&gt;
Associated to &lt;a class="closed ticket" href="http://localhost/ticket/51" title="enhancement: Upgrade CKAN to use sqlalchemy and vdm v0.2 (closed: fixed)"&gt;ticket:51&lt;/a&gt; (upgrade CKAN to new vdm) and &lt;a class="closed ticket" href="http://localhost/ticket/54" title="enhancement: Support dump and load of CKAN data to JSON (closed: fixed)"&gt;ticket:54&lt;/a&gt; (dump/load) need to convert v0.6 data for v0.7.
&lt;/p&gt;
&lt;p&gt;
Obvious way to do this is via alteration to data load method.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/55#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/39</link>
        <guid isPermaLink="false">http://localhost/ticket/39</guid>
        <title>#39: When listing packages show more information than just name.</title>
        <pubDate>Fri, 09 Nov 2007 11:48:40 GMT</pubDate>
        
        <dc:creator>rgrp</dc:creator>

        <description>&lt;p&gt;
When a package listing is shown (as on &lt;a class="ext-link" href="http://ckan.net/package/list"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://ckan.net/package/list&lt;/a&gt;) more information than just name should be shown. For example package titles should be shown as well as names (could also list tags and other stuff but simplest is just title).
&lt;/p&gt;
&lt;p&gt;
Cost: 1
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/39#changelog</comments>
    </item>
 </channel>
</rss>