Ticket #227 (closed task: wontfix)

Opened 6 years ago

Last modified 4 years ago

Set up mirroring capability for core data types

Reported by: ed Owned by: chris
Priority: major Milestone:
Component: Live server Keywords:
Cc: Estimated Number of Hours: 0.0
Add Hours to Ticket: 0 Billable?: yes
Total Hours: 0

Description (last modified by chris) (diff)

Action point from the web strategy meeting, while discussing security:

  1. Technical discussion track needed on ongoing security with these priorities: 1. how to keep safe copies, 2. how to avoid vandalism
  1. Need to explore 'Mirrors' for TN.org: core data: all Directories, secondary data: forums, blogs, news etc.

This ticket for setting up 'mirroring' capability for core data as part of the under the waterline element of phase 4

Change History

comment:1 Changed 6 years ago by ed

From email from Chris:


8e. Need to explore 'Mirrors' for TN.org: core data: all Directories,

secondary data: forums, blogs, news etc.

8f. National sites as mirrors for each other?

On Thu 17-Feb-2011 at 10:08:47AM +0000, Ed Mitchell wrote:

  1. Jim meeting with Carl (US) to discuss enabling initiatives to

register on a local site which is integrated with the main TN
initiatives directory. This will be a key to this I'm sure, and the
bigger 'how to get projects to sign up from their own sites too'
question (Jim I'll explain in our skype later today).
I've been thinking about this in terms of the initiatives directory and
I have thought of a couple of options, one simple and still centralised
and one more complicated and distributed (of course there are many more
options in-between):

  1. Give national hubs admin access to add initiatives to the network site. Make a selective Mysql dump of the tables needed to import the initiatives into another Drupal site available for mirroring purposes.
  1. Sort out a XML format for the initiatives data and a way to dump and import this from Drupal and other CMS's as required. Put the XML data in a git repo and have each site update their version of the repo. We then sort out a way to merge the changes between repos and keep them all upto date.

comment:2 Changed 5 years ago by ed

  • Priority changed from major to critical

comment:3 Changed 5 years ago by ed

  • Priority changed from critical to major

comment:4 Changed 5 years ago by chris

priority changed from critical to major

OK, what the way forwards with this?

comment:5 Changed 5 years ago by ed

worth bringing up in skype tomorrow. Related to #262. Also, here's a question: which national hubs could we have this sort of relationship with? The US definitely, so they're a first point of call, but are any other national hubs in a technically advanced enough situation to accept a dump of data from us?

comment:6 Changed 5 years ago by ed

  • Milestone Phase 4 deleted

downgrading in lieu of potential changes to #262 (ie we may not share data after all)...

comment:7 Changed 4 years ago by chris

  • Description modified (diff)

Is this ticket still valid or should it be closed?

comment:8 Changed 4 years ago by ed

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


Note: See TracTickets for help on using tickets.