CKAN: Ticket #325: Event push notification http://localhost/ticket/325 <h3 id="Asa">As a</h3> <p> CKAN client program </p> <h3 id="Iwantto">I want to</h3> <p> be notified when changes to the CKAN metadata occur. </p> <h3 id="Examplesofuse">Examples of use</h3> <ol><li>An external search engine needing to (re)index a package. </li><li>A front-end system that caches package info and wants to know when it changes, to keep in step. </li><li>A system for automatically checking package URLs and resource URLs as they are put on the system. This could alert to bad URLs and automatically email feedback to (meta)data owners. </li></ol><h3 id="Context">Context</h3> <p> The current state of CKAN can be queried through the REST API, you can keep track of changes by reviewing the feeds, but there is no way to find out the instant something is changed, without costly polling. </p> <h3 id="Design">Design</h3> <p> Split-off into two tickets: </p> <ul><li>Notification message - <a class="closed ticket" href="http://localhost/ticket/323" title="enhancement: Notification message (closed: fixed)">ticket:323</a> <ul><li>Which events to notify on </li><li>Message format </li></ul></li><li>Interface for Notifier Service - <a class="closed ticket" href="http://localhost/ticket/322" title="enhancement: Client interface for Notification Service (closed: fixed)">ticket:322</a> </li></ul><h3 id="Testing">Testing</h3> <p> To test notifications, Carrot / AMQP will be configured to use a native-Python Queue, instead of requiring RabbitMQ to be running on the machine. </p> <h3 id="Related">Related</h3> <ul><li>Run CKAN search indexing using this system - <a class="closed ticket" href="http://localhost/ticket/324" title="enhancement: Search indexing using notifications (closed: fixed)">ticket:324</a> </li></ul> en-us CKAN http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/325 Trac 0.12.3 pudo Tue, 25 May 2010 17:10:07 GMT description changed http://localhost/ticket/325#comment:1 http://localhost/ticket/325#comment:1 <ul> <li><strong>description</strong> modified (<a href="/ticket/325?action=diff&amp;version=1">diff</a>) </li> </ul> Ticket dread Thu, 27 May 2010 14:35:21 GMT description changed http://localhost/ticket/325#comment:2 http://localhost/ticket/325#comment:2 <ul> <li><strong>description</strong> modified (<a href="/ticket/325?action=diff&amp;version=2">diff</a>) </li> </ul> Ticket dread Thu, 27 May 2010 14:43:09 GMT description changed http://localhost/ticket/325#comment:3 http://localhost/ticket/325#comment:3 <ul> <li><strong>description</strong> modified (<a href="/ticket/325?action=diff&amp;version=3">diff</a>) </li> </ul> Ticket dread Mon, 31 May 2010 16:42:53 GMT description changed http://localhost/ticket/325#comment:4 http://localhost/ticket/325#comment:4 <ul> <li><strong>description</strong> modified (<a href="/ticket/325?action=diff&amp;version=4">diff</a>) </li> </ul> Ticket dread Tue, 15 Jun 2010 10:33:49 GMT description changed http://localhost/ticket/325#comment:5 http://localhost/ticket/325#comment:5 <ul> <li><strong>description</strong> modified (<a href="/ticket/325?action=diff&amp;version=5">diff</a>) </li> </ul> Ticket dread Mon, 21 Jun 2010 12:31:50 GMT description changed http://localhost/ticket/325#comment:6 http://localhost/ticket/325#comment:6 <ul> <li><strong>description</strong> modified (<a href="/ticket/325?action=diff&amp;version=6">diff</a>) </li> </ul> Ticket dread Thu, 08 Jul 2010 14:39:39 GMT status changed; resolution set http://localhost/ticket/325#comment:7 http://localhost/ticket/325#comment:7 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> <p> Both sending and received tickets closed. </p> Ticket