<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket #896: Distributed Data and Syncing Between CKAN Instances</title>
    <link>http://localhost/ticket/896</link>
    <description>&lt;p&gt;
Based on the ideas in:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost/wiki/DistributingChanges"&gt;DistributingChanges&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost/wiki/SyncingInstances"&gt;SyncingInstances&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Merging the tickets &lt;a class="closed ticket" href="http://localhost/ticket/296" title="enhancement: Commit CKAN revisions to changeset system (closed: duplicate)"&gt;#296&lt;/a&gt;, &lt;a class="closed ticket" href="http://localhost/ticket/297" title="enhancement: Update CKAN repository from changeset system (closed: duplicate)"&gt;#297&lt;/a&gt;, &lt;a class="closed ticket" href="http://localhost/ticket/298" title="enhancement: Pull changesets from remote CKAN instance (closed: duplicate)"&gt;#298&lt;/a&gt;, &lt;a class="closed ticket" href="http://localhost/ticket/299" title="enhancement: Merge diverging lines of changesets (closed: duplicate)"&gt;#299&lt;/a&gt; into this one.
&lt;/p&gt;
&lt;p&gt;
Related ideas include:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Using dcat to exchange data
&lt;/li&gt;&lt;li&gt;Using couchDB to have a stub package record synchronised between multiple CKAN instances, each linking to the main record in the correct instance
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
This should be considered a wishlist item for the timebeing.
&lt;/p&gt;
</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/ticket/896</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
      
        <dc:creator>thejimmyg</dc:creator>

      <pubDate>Tue, 15 Mar 2011 19:29:35 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost/ticket/896#comment:1</link>
      <guid isPermaLink="false">http://localhost/ticket/896#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;new&lt;/em&gt; to &lt;em&gt;closed&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                set to &lt;em&gt;duplicate&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Actually, I think this should be implemented instead by considering a different CKAN instance as a potential harvest source and then harvesting from it. By thinking of it this way in the first instance, we effectively get a read-only copy of other data in CKAN but one which will be kept up to date.
&lt;/p&gt;
&lt;p&gt;
Marking as duplicate. Discussion can now carry on via &lt;a class="closed ticket" href="http://localhost/ticket/987" title="defect: Common harvesting framework (closed: duplicate)"&gt;#987&lt;/a&gt; Common harvesting framework.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>