http://localhost/ticket/253 <h1 id="Overview">Overview</h1> <p> Functionality to formally associate packages. We see a need for specific parent-child, inheriting or dependency relations. Not only should this help navigation between packages in the web interface, but it also provides a mechanism to automatically pull dependencies when downloading a data package, in a similar manner as we see in software package management. </p> <h1 id="Examples">Examples</h1> <ol><li>There are 27 packages in data.gov.uk to do with the Data4NR's Health Poverty Index. There is currently no common link between these, unless you search for 'HPI' (which also brings up House Price Index), or look under tag 'health' (which also has 600 other results). There should be a link on each HPI package page to navigate to the other 'sibling' HPI packages, and to a 'root' package that has info about the set. This could be partially achieved using the existing tag or group concepts, but a more explicit/official/obvious marking of their relationship could be beneficial. </li></ol><ol start="2"><li>In ckan.net is freedict, a collection of translation dictionaries. You could make each dictionary a child package and use this system. But it would probably be better to make each dictionary a different resource in the same package. (There are other ideas to denote a resource as the data making up a 'portion' of package, or a 'whole' of the package, to help people downloading datasets in the software package style.) </li></ol><ol start="3"><li>OSM has had some Naptan data imported (bus stops), with special permission - i.e. a more liberal license. It would be useful to show this link on both OSM and Naptan packages in CKAN: OSM 'derives from' Naptan with a comment about the license change. I'm not sure this is useful to an automatic download or use of these datasets, but may aid exploration on the CKAN website and understanding the provenance of the bus stop data on it. </li></ol><ol start="4"><li>IPCC collection of data linked / mirrored. Not sure if there are useful relationships here? </li></ol><ol start="5"><li>Dracos gets postbox locations from crowd sourcing and OSM. We could say Dracos 'derives from' OSM. </li></ol><p> See more examples discussed here: <a class="ext-link" href="http://trac.ckan.org/ticket/253"><span class="icon">​</span>http://trac.ckan.org/ticket/253</a> </p> <h1 id="Implementation">Implementation</h1> <p> This is split into four tickets: </p> <ul><li>Model: <a class="closed ticket" href="http://localhost/ticket/254" title="enhancement: Package relationships - 1. model (closed: fixed)">ticket:254</a> </li><li>Read in WUI: <a class="closed ticket" href="http://localhost/ticket/255" title="enhancement: Package relationships - 2. Read in WUI (closed: fixed)">ticket:255</a> </li><li>Edit in WUI: <a class="assigned ticket" href="http://localhost/ticket/256" title="requirement: Package relationships - 3. Edit in WUI (assigned)">ticket:256</a> </li><li>API: <a class="closed ticket" href="http://localhost/ticket/257" title="enhancement: Package relationships - 4. Read in API (closed: fixed)">ticket:257</a> </li></ul><p> No need for write access to be provided API for the moment. </p> <p> This ticket also encompasses <a class="closed ticket" href="http://localhost/ticket/169" title="enhancement: Package derivations (closed: duplicate)">ticket:169</a> (Package derivations) and <a class="closed ticket" href="http://localhost/ticket/176" title="enhancement: Package dependencies (closed: duplicate)">ticket:176</a> (Package dependencies). </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/253 Trac 0.12.3 dread Mon, 22 Feb 2010 17:23:28 GMT http://localhost/ticket/253#comment:1 http://localhost/ticket/253#comment:1 <ul> <li><strong>description</strong> modified (<a href="/ticket/253?action=diff&amp;version=1">diff</a>) </li> </ul> Ticket dread Tue, 23 Feb 2010 12:37:39 GMT http://localhost/ticket/253#comment:2 http://localhost/ticket/253#comment:2 <ul> <li><strong>owner</strong> changed from <em>rgrp</em> to <em>dread</em> </li> <li><strong>priority</strong> changed from <em>awaiting triage</em> to <em>blocker</em> </li> <li><strong>description</strong> modified (<a href="/ticket/253?action=diff&amp;version=2">diff</a>) </li> </ul> Ticket dread Tue, 23 Feb 2010 12:38:48 GMT http://localhost/ticket/253#comment:3 http://localhost/ticket/253#comment:3 <ul> <li><strong>description</strong> modified (<a href="/ticket/253?action=diff&amp;version=3">diff</a>) </li> </ul> Ticket dread Wed, 07 Apr 2010 09:27:38 GMT http://localhost/ticket/253#comment:4 http://localhost/ticket/253#comment:4 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>duplicate</em> </li> </ul> <p> Closing in favour of the 4 tickets it is split into. </p> Ticket dread Tue, 11 May 2010 16:43:07 GMT http://localhost/ticket/253#comment:5 http://localhost/ticket/253#comment:5 <ul> <li><strong>milestone</strong> set to <em>v1.0</em> </li> </ul> Ticket rgrp Fri, 21 Jan 2011 11:43:08 GMT http://localhost/ticket/253#comment:6 http://localhost/ticket/253#comment:6 <ul> <li><strong>status</strong> changed from <em>closed</em> to <em>reopened</em> </li> <li><strong>resolution</strong> <em>duplicate</em> deleted </li> </ul> <p> Re-opening as this is a useful meta-ticket and should only be closed when all subtickets done. </p> Ticket dread Mon, 31 Jan 2011 10:54:46 GMT http://localhost/ticket/253#comment:7 http://localhost/ticket/253#comment:7 <ul> <li><strong>milestone</strong> changed from <em>v1.0</em> to <em>longterm</em> </li> </ul> Ticket dread Mon, 31 Jan 2011 18:53:44 GMT http://localhost/ticket/253#comment:8 http://localhost/ticket/253#comment:8 <ul> <li><strong>priority</strong> changed from <em>blocker</em> to <em>major</em> </li> </ul> Ticket thejimmyg Fri, 08 Jul 2011 11:35:01 GMT http://localhost/ticket/253#comment:9 http://localhost/ticket/253#comment:9 <ul> <li><strong>repo</strong> set to <em>ckan</em> </li> <li><strong>theme</strong> set to <em>none</em> </li> <li><strong>milestone</strong> <em>ckan-backlog</em> deleted </li> </ul> Ticket dread Fri, 02 Sep 2011 10:54:43 GMT http://localhost/ticket/253#comment:10 http://localhost/ticket/253#comment:10 <ul> <li><strong>description</strong> modified (<a href="/ticket/253?action=diff&amp;version=10">diff</a>) </li> </ul> Ticket dread Thu, 27 Oct 2011 10:01:24 GMT http://localhost/ticket/253#comment:11 http://localhost/ticket/253#comment:11 <ul> <li><strong>priority</strong> changed from <em>major</em> to <em>awaiting triage</em> </li> <li><strong>status</strong> changed from <em>reopened</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> Ticket dread Thu, 27 Oct 2011 10:01:54 GMT http://localhost/ticket/253#comment:12 http://localhost/ticket/253#comment:12 <ul> <li><strong>status</strong> changed from <em>closed</em> to <em>reopened</em> </li> <li><strong>resolution</strong> <em>fixed</em> deleted </li> </ul> <p> Closed by mistake </p> Ticket dread Thu, 27 Oct 2011 10:02:08 GMT http://localhost/ticket/253#comment:13 http://localhost/ticket/253#comment:13 <ul> <li><strong>owner</strong> <em>dread</em> deleted </li> <li><strong>status</strong> changed from <em>reopened</em> to <em>assigned</em> </li> </ul> Ticket seanh Fri, 15 Jun 2012 15:38:46 GMT http://localhost/ticket/253#comment:14 http://localhost/ticket/253#comment:14 <ul> <li><strong>milestone</strong> set to <em>ckan-backlog</em> </li> </ul> Ticket