Ticket #896 (closed story: duplicate)

Opened 3 years ago

Last modified 3 years ago

Distributed Data and Syncing Between CKAN Instances

Reported by: thejimmyg Owned by:
Priority: minor Milestone:
Component: ckan Keywords:
Cc: Repository:
Theme:

Description

Based on the ideas in:

Merging the tickets #296, #297, #298, #299 into this one.

Related ideas include:

  • Using dcat to exchange data
  • Using couchDB to have a stub package record synchronised between multiple CKAN instances, each linking to the main record in the correct instance

This should be considered a wishlist item for the timebeing.

Change History

comment:1 Changed 3 years ago by thejimmyg

  • Status changed from new to closed
  • Resolution set to duplicate

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.

Marking as duplicate. Discussion can now carry on via #987 Common harvesting framework.

Note: See TracTickets for help on using tickets.