http://localhost/ticket/653 <p> When people link to a package, a track-back link is auto-created. (Similar system as for blogs). </p> <p> As suggested by Tim Davies: </p> <p> Allowing some form of ‘track back’ against datasets When a non-technical user comes to look at a dataset it would be really useful for them to be able to see if anyone has created an interface interpretation of it already. </p> <p> I found quite a few cases in research of end-users struggling to make sense of a dataset when good interfaces to that data had already been built and blogged about, but without there being any link from the dataset listing to those data uses. Accepting track backs could also make it easier for technical users to find blog posts / shared code etc. relating to a given dataset. </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/653 Trac 0.12.3 dread Tue, 21 Sep 2010 09:41:48 GMT http://localhost/ticket/653#comment:1 http://localhost/ticket/653#comment:1 <ul> <li><strong>description</strong> modified (<a href="/ticket/653?action=diff&amp;version=1">diff</a>) </li> </ul> Ticket seanh Fri, 15 Jun 2012 15:37:16 GMT http://localhost/ticket/653#comment:2 http://localhost/ticket/653#comment:2 <ul> <li><strong>priority</strong> set to <em>awaiting triage</em> </li> <li><strong>repo</strong> set to <em>ckan</em> </li> <li><strong>theme</strong> set to <em>none</em> </li> <li><strong>milestone</strong> set to <em>ckan-backlog</em> </li> </ul> Ticket