<?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?status=closed&amp;milestone=pdeu-1&amp;group=resolution&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?status=closed&amp;milestone=pdeu-1&amp;group=resolution&amp;order=priority</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
        <link>http://localhost/ticket/1158</link>
        <guid isPermaLink="false">http://localhost/ticket/1158</guid>
        <title>#1158: Put PDEU into read-only mode and remove unneeded functions</title>
        <pubDate>Wed, 25 May 2011 15:36:26 GMT</pubDate>
        
        <dc:creator>pudo</dc:creator>

        <description>&lt;p&gt;
PDEU should be in a mode where:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Users cannot edit or create packages
&lt;/li&gt;&lt;li&gt;Users cannot sign up on their own
&lt;/li&gt;&lt;li&gt;&lt;a class="missing wiki"&gt;AuthorizationGroups?&lt;/a&gt; and &lt;a class="missing wiki"&gt;RevisionHistory?&lt;/a&gt; is completely gone from the UI
&lt;/li&gt;&lt;li&gt;Groups have been repurposed as Subjects
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost/ticket/1158#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/1157</link>
        <guid isPermaLink="false">http://localhost/ticket/1157</guid>
        <title>#1157: A simple theme for publicdata.eu, CKAN</title>
        <pubDate>Wed, 25 May 2011 15:32:53 GMT</pubDate>
        
        <dc:creator>pudo</dc:creator>

        <description>&lt;p&gt;
Change the visual style of CKAN to be more like these sites:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="missing wiki"&gt;GitHub?&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Quora
&lt;/li&gt;&lt;li&gt;Google Projects
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
This does not include major UX work.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/1157#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/1155</link>
        <guid isPermaLink="false">http://localhost/ticket/1155</guid>
        <title>#1155: Harvester for data.london.gov.uk</title>
        <pubDate>Wed, 25 May 2011 15:28:38 GMT</pubDate>
        
        <dc:creator>pudo</dc:creator>

        <description>&lt;p&gt;
Write a harvester for data.london.gov.uk to import catalogue metadata into PDEU. API (or at least documentation) is available at: &lt;a class="ext-link" href="http://sourceforge.net/projects/londondatastore/files/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://sourceforge.net/projects/londondatastore/files/&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/1155#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/1156</link>
        <guid isPermaLink="false">http://localhost/ticket/1156</guid>
        <title>#1156: Scraping harvesters for Paris and Vienna Catalogues</title>
        <pubDate>Wed, 25 May 2011 15:30:28 GMT</pubDate>
        
        <dc:creator>pudo</dc:creator>

        <description>&lt;p&gt;
Import metadata from both sources into PDEU via the Harvesting framework but by scraping their respective catalogue pages.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://data.wien.gv.at/katalog/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://data.wien.gv.at/katalog/&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="http://opendata.paris.fr/opendata/jsp/site/Portal.jsp"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://opendata.paris.fr/opendata/jsp/site/Portal.jsp&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost/ticket/1156#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/1162</link>
        <guid isPermaLink="false">http://localhost/ticket/1162</guid>
        <title>#1162: Define a common extra for storing the geographic extent</title>
        <pubDate>Thu, 26 May 2011 11:18:24 GMT</pubDate>
        
        <dc:creator>amercader</dc:creator>

        <description>&lt;p&gt;
We need a common extra across the different harvested sources that defines the extent of the data. We will have mainly national level catalogues, but also at a lower level (region, city).
&lt;/p&gt;
&lt;p&gt;
Relevant discussion:
&lt;a class="ext-link" href="http://lists.okfn.org/pipermail/ckan-discuss/2011-May/001245.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://lists.okfn.org/pipermail/ckan-discuss/2011-May/001245.html&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/1162#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/1173</link>
        <guid isPermaLink="false">http://localhost/ticket/1173</guid>
        <title>#1173: Offer a DCat representation for packages in the API</title>
        <pubDate>Wed, 01 Jun 2011 14:47:19 GMT</pubDate>
        
        <dc:creator>amercader</dc:creator>

        <description>&lt;p&gt;
/api/rest/package/foo.rdf should return a DCat representation of the package. To create it, we will use the functions in ckanext-rdf.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/1173#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/1159</link>
        <guid isPermaLink="false">http://localhost/ticket/1159</guid>
        <title>#1159: Add RDFa to CKAN package pages</title>
        <pubDate>Wed, 25 May 2011 15:38:27 GMT</pubDate>
        
        <dc:creator>pudo</dc:creator>

        <description>&lt;p&gt;
RDFa can be used as a simple way to expose linked data or at least sameAs the API version of the data but we need to make sure we do not expose anything different from the "official" representation.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/1159#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/1164</link>
        <guid isPermaLink="false">http://localhost/ticket/1164</guid>
        <title>#1164: Cloropleth Map of European Data Availability for PDEU</title>
        <pubDate>Thu, 26 May 2011 11:20:24 GMT</pubDate>
        
        <dc:creator>amercader</dc:creator>

        <description>&lt;p&gt;
A nice map in the homepage showing the availability of data across Europe
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/1164#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/1160</link>
        <guid isPermaLink="false">http://localhost/ticket/1160</guid>
        <title>#1160: Havest CSW servers on PDEU</title>
        <pubDate>Thu, 26 May 2011 10:54:31 GMT</pubDate>
        
        <dc:creator>amercader</dc:creator>

        <description>&lt;p&gt;
It could be interesting for the publicdata.eu project to add some CSW datasources. Thanks to the INSPIRE directive, there are quite a few national catalogs of geodata that could be worth harvesting.
Work on this should include:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Compose Endpoint List (1d)
&lt;/li&gt;&lt;li&gt;Harvest on staging system and evaluate which sources have useful material (2d)
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
First point is being performed in this GDoc:
&lt;a class="ext-link" href="https://spreadsheets.google.com/spreadsheet/ccc?key=0Atp3cZFjuIOAdDBVQWRINnlfN1d0b2lleHVEdjBSb2c&amp;amp;authkey=CNu4hsEB&amp;amp;hl=en_US#gid=0"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://spreadsheets.google.com/spreadsheet/ccc?key=0Atp3cZFjuIOAdDBVQWRINnlfN1d0b2lleHVEdjBSb2c&amp;amp;authkey=CNu4hsEB&amp;amp;hl=en_US#gid=0&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/1160#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/1174</link>
        <guid isPermaLink="false">http://localhost/ticket/1174</guid>
        <title>#1174: API Representation Registry</title>
        <pubDate>Thu, 02 Jun 2011 21:43:12 GMT</pubDate>
        
        <dc:creator>pudo</dc:creator>

        <description>&lt;p&gt;
As CKAN grows, more and more optional representations of packages will become used. Besides RDF (which is the motivation for this ticket), support for DSPL, home-grown XML, or CSV listings is imaginable.
&lt;/p&gt;
&lt;p&gt;
To properly support this CKAN should have an extensible representation registry that can be extended when new output types become available (and without changing the API in the process). This needs to integrate in two places:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;We need to add support for file format extensions to the package handler and REST API.
&lt;/li&gt;&lt;li&gt;We need to add HTTP content type negotiation (Accept headers).
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
To support this we should have a registry with two registers:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;to map format extensions to mime types (e.g. "json" -&amp;gt; "application/json")
&lt;/li&gt;&lt;li&gt;to map mime types and entity types to converter functions (e.g. 8"application/json", ckan.model.Package) -&amp;gt; func(obj, mime_type) )
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
This should be set up on load_environment so that IConfigurer plugins can feed into it.
&lt;/p&gt;
&lt;p&gt;
The registry should then first be added to _finish in the REST API (which needs to be refactored to be passed the {format} part of the URL if one is given. Based on the format part and HTTP headers, an appropriate representation can be generated by the registry and then be returned to the user.
&lt;/p&gt;
&lt;p&gt;
Forwarding of requests to the regular WUI controllers with Accept headers set or a format specified can be implemented in a separate effort.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/1174#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/1161</link>
        <guid isPermaLink="false">http://localhost/ticket/1161</guid>
        <title>#1161: Build a simplified theme for PDEU</title>
        <pubDate>Thu, 26 May 2011 11:03:55 GMT</pubDate>
        
        <dc:creator>amercader</dc:creator>

        <description>&lt;p&gt;
We need to offer a strongly simplified version, read-only of CKAN under publicdata.eu, with a focus on its role as search engine instead of a data catalogue.
&lt;/p&gt;
&lt;p&gt;
This ticket relates to work on the PDEU theme only!
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost/ticket/1161#changelog</comments>
    </item><item>
        <link>http://localhost/ticket/985</link>
        <guid isPermaLink="false">http://localhost/ticket/985</guid>
        <title>#985: Harvest other data catalogues</title>
        <pubDate>Mon, 14 Feb 2011 10:36:39 GMT</pubDate>
        
        <dc:creator>pudo</dc:creator>

        <description>&lt;ul&gt;&lt;li&gt;data.london.gov.uk (1d, ping DERI)
&lt;/li&gt;&lt;li&gt;catalogues from Paris and Vienna (1d)
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Others?
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;digitaliser.dk (1d)
&lt;/li&gt;&lt;li&gt;data-publica.com (2d)
&lt;/li&gt;&lt;li&gt;data.suomi.fi (2d)
&lt;/li&gt;&lt;li&gt;dati.piedmonte.it (1d)
&lt;/li&gt;&lt;li&gt;portalu.de (2d)
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost/ticket/985#changelog</comments>
    </item>
 </channel>
</rss>